G
Guest
Hey all,
I have DFS setup in our domain, mostly used to provide a single access point
to shares which reside on different workstations. There is no replication
involved. The DFS Root is a share setup to contain the DFS links and nothing
else. The DFS Root is on a Windows 2000 Server that's up to date.
For consistency/ease of use for my users, the name of the link in the DFS
Root is the same as the actual share name it's pointing to.
The DFS Root is mapped as a network drive during a user's logon.
Since SP2, DFS continues to work, except when it comes to accessing a share
that is on the local machine. A network path not found error is returned.
For example
\\DFS Root\<local share name>\ - will return the network not found path
error.
Browsing to the location through the network to the DFS Root or the mapped
drive gives the same result.
But
\\<local computer name>\<local share name> - still works okay to access the
same share.
Additionally, if one checks the properties on the link to the local share in
the DFS root and checks the DFS tab everything appears okay, and "check
status" will even return that the link is "Okay". Even after having Windows
confirm the link is "Okay" the local client is not able to access it.
This issue only appears to occur on XP SP2, SP1 still works properly, as do
Windows 2000 SP4 workstations. I have experienced this on numerous different
XP Pro workstations.
I had originally thought it may just have been an issue with the new Windows
firewall, but I was unable to find any dropped packets related to this in the
logs, and even completely disabling the firewall did not correct the problem.
Thanks for any input you can offer.
I have DFS setup in our domain, mostly used to provide a single access point
to shares which reside on different workstations. There is no replication
involved. The DFS Root is a share setup to contain the DFS links and nothing
else. The DFS Root is on a Windows 2000 Server that's up to date.
For consistency/ease of use for my users, the name of the link in the DFS
Root is the same as the actual share name it's pointing to.
The DFS Root is mapped as a network drive during a user's logon.
Since SP2, DFS continues to work, except when it comes to accessing a share
that is on the local machine. A network path not found error is returned.
For example
\\DFS Root\<local share name>\ - will return the network not found path
error.
Browsing to the location through the network to the DFS Root or the mapped
drive gives the same result.
But
\\<local computer name>\<local share name> - still works okay to access the
same share.
Additionally, if one checks the properties on the link to the local share in
the DFS root and checks the DFS tab everything appears okay, and "check
status" will even return that the link is "Okay". Even after having Windows
confirm the link is "Okay" the local client is not able to access it.
This issue only appears to occur on XP SP2, SP1 still works properly, as do
Windows 2000 SP4 workstations. I have experienced this on numerous different
XP Pro workstations.
I had originally thought it may just have been an issue with the new Windows
firewall, but I was unable to find any dropped packets related to this in the
logs, and even completely disabling the firewall did not correct the problem.
Thanks for any input you can offer.