K
kenw
I'm having an "interesting" issue with a laptop that has difficulty seeing
the contents of a specific server-shared folder via UNC only. And I need
this specific share to work, for application compatibility reasons.
If I use Explorer to browse the network to the share, when I open the
share, it appear empty. Usually. Sometimes, after a reboot, I can see the
contents. But if I reboot again, it's empty. Always with the same user
ID/password, BTW.
Now, here's where things start to get interesting. I can map a drive
letter to the share, and that works fine. If I add another share name to
the same folder, the new share works fine. I can share and access the
parent folder, right down through the problem folder. The old share is
unaffected -- it still sees nothing in the shared folder.
I've tried recreating the share. No change. I've double-checked all
permissions (share and file); they're fine. There's no problem accessing
the share with the same user ID from another PC. Logging in as a workgroup
peer or a domain member makes no difference. I've tried clearing all
caches and disabling offline files. I've checked environment variables.
I've reset the protocol stack, both via GUI and netsh. I've removed all
network components and re-added everything. Nada. Same for rebooting the
server.
So, what's different about browsing or accessing a network share via UNC
versus via a drive letter? And what would make it see a specific folder
name differently from the same folder as a different name?
Oh, BTW, this behavior seemed to start yesterday after upgrading the laptop
from XP Home to XP Pro. The server is a recently (several days ago)
installed Win2k Server. The AD is... iffy; I don't administer it, and I
think it has "issues", but since when does AD affect folder contents?
/kenw
Ken Wallewein
Calgary, Alberta
(e-mail address removed)
www.kmsi.net
Ken Wallewein
Calgary, Alberta
(e-mail address removed)
www.kmsi.net
the contents of a specific server-shared folder via UNC only. And I need
this specific share to work, for application compatibility reasons.
If I use Explorer to browse the network to the share, when I open the
share, it appear empty. Usually. Sometimes, after a reboot, I can see the
contents. But if I reboot again, it's empty. Always with the same user
ID/password, BTW.
Now, here's where things start to get interesting. I can map a drive
letter to the share, and that works fine. If I add another share name to
the same folder, the new share works fine. I can share and access the
parent folder, right down through the problem folder. The old share is
unaffected -- it still sees nothing in the shared folder.
I've tried recreating the share. No change. I've double-checked all
permissions (share and file); they're fine. There's no problem accessing
the share with the same user ID from another PC. Logging in as a workgroup
peer or a domain member makes no difference. I've tried clearing all
caches and disabling offline files. I've checked environment variables.
I've reset the protocol stack, both via GUI and netsh. I've removed all
network components and re-added everything. Nada. Same for rebooting the
server.
So, what's different about browsing or accessing a network share via UNC
versus via a drive letter? And what would make it see a specific folder
name differently from the same folder as a different name?
Oh, BTW, this behavior seemed to start yesterday after upgrading the laptop
from XP Home to XP Pro. The server is a recently (several days ago)
installed Win2k Server. The AD is... iffy; I don't administer it, and I
think it has "issues", but since when does AD affect folder contents?
/kenw
Ken Wallewein
Calgary, Alberta
(e-mail address removed)
www.kmsi.net
Ken Wallewein
Calgary, Alberta
(e-mail address removed)
www.kmsi.net