G
Guest
On exactly one Windows XP workstation on our network, users are unable to
access files by UNC, although they can access them through mapped drives.
For instance, P: is a mapped drive for \\Server\Public\. So the paths
P:\temp.txt and \\Server\Public\temp.txt point to the same file, by way of
the same network share. But "type P:\temp.txt" types out the file, while
"type \\Server\Public\temp.txt" displays "Access denied." Folders can be
opened by UNC in Explorer or a DIR command, but "List folder contents" seems
to be the only functioning privilege.
\\Server\Public shares the F:\Public folder on the server itself, so
\\Server\F$\Public\temp.txt also points to the file. On other computers, a
regular user can access P:\temp.txt and \\Server\Public\temp.txt and gets
"Access denied" for \\Server\F$\Public\temp.txt; and an administrative user
can access all three.
But on the problem machine, even domain administrators can only access
P:\temp.txt. Aren't the resulting privileges supposed to be the same whether
the share is accessed directly or through a mapped drive letter? What's
going on?
This machine can't access any share on any network machine by UNC, as far as
I've tested. It can't even read files from its own C$ share. This behavior
started in the last day, and has survived multiple reboots. I can't find
anything weird in the event logs for the machine, or in the security logs of
machines it's trying to access.
Any ideas? Thanks!
access files by UNC, although they can access them through mapped drives.
For instance, P: is a mapped drive for \\Server\Public\. So the paths
P:\temp.txt and \\Server\Public\temp.txt point to the same file, by way of
the same network share. But "type P:\temp.txt" types out the file, while
"type \\Server\Public\temp.txt" displays "Access denied." Folders can be
opened by UNC in Explorer or a DIR command, but "List folder contents" seems
to be the only functioning privilege.
\\Server\Public shares the F:\Public folder on the server itself, so
\\Server\F$\Public\temp.txt also points to the file. On other computers, a
regular user can access P:\temp.txt and \\Server\Public\temp.txt and gets
"Access denied" for \\Server\F$\Public\temp.txt; and an administrative user
can access all three.
But on the problem machine, even domain administrators can only access
P:\temp.txt. Aren't the resulting privileges supposed to be the same whether
the share is accessed directly or through a mapped drive letter? What's
going on?
This machine can't access any share on any network machine by UNC, as far as
I've tested. It can't even read files from its own C$ share. This behavior
started in the last day, and has survived multiple reboots. I can't find
anything weird in the event logs for the machine, or in the security logs of
machines it's trying to access.
Any ideas? Thanks!