We are running a Win2k3 terminal server cluster for sue by staff (especially those on Mac/*nix clients) for accessing Windows only resources. In the past, when we were using Win2k terminal servcies, the Mac admins would use this to browse to windows shares using DFS paths, and right click the shared folder properties to determin what server location the DFS paths were pointing to. This allowed them to run scripts to map the shares to the right server for the Mac users.
However, since moving to the 2k3 cluster we have run into an issue where right clicking a sub-fodler with it's own DFS path in a DFS namespace and going to properties brings up... nothing. No properties will appear at all for the shared folder. Local folders, Folders in the root DFS namespace and non-DFS shares appear to work ok.
DFS Namespace: \\blah.com\universal
Right click \\blah.com\universal\DFSshare brings up the properties.
Right click \\blah.com\universal\DFSshare\DFSresource will not display properties.
This ONLY happens during a terminal session. From an windows admin box, all is fine. I haven't been able to find anything useful online yet, probably because I haven't manaegd to tweak my search terms properly. Can anyone shed any light on this?
Hmm, reading that barely even makes sense to me. Hope you understand what i am getting at...