Connection MAC's to DFS. I am trying to replace the file servers one at a time so I don't want the Mac's to reference a single server but the distributed file system.
We've had a namespace in place for over a year and it's worked fine.Until last Thursday when a couple of client PCs could still see the namespace but with almost NO contents.
Curse Client For Mac
Looking at the local paths on the member servers shows them to be full of the data we'd expect to see...but you can't see them when browsing to the namespace.The only things you can see are two linked folders, one of which matches the name of the replicated source folder. If you browse in to that link you can then see the expected contents. Look at the properties of one of the folders and choose the DFS tab all you see listed is the source server, not the member servers.
This behaviour is only true in our London office. The namespace behaviour in our New York and Hong Kong offices is as it should be. Specifically, the namespace is fully populated, the DFS referral list shows all the member servers I'd expect to see and as the New York member server is currently down the NY client PC is connecting to the Hong Kong member server for its DFS data.
Finally, we've found one London PC which CAN see the contents of the namespace.
To try to resolve we have- restarted the DFS Namespace service on the Windows Server 2008 DCs, and the Distributed File System service on the Server 2003 DCs,
Vmware Horizon Client For Mac
- set the DFS Namespace service to Delayed Start and rebooted the FSMO role holder DC,
- Ran 'dfsutil /PktFlush', 'dfsutil /SpcFlush' and 'dfsutil /PurgeMupCache' on a 'broken' client PC
Badlion Client For Mac
None of these have made a difference.Almost all clients are Windows 7. All four sites have separate subnets. DCs are mostly Server 2003, except for 2 x 2008 in London.
So far, similar threads to this one on other tech forums have produced no responses at all...hopefully that's not an indication of this being a big, or new, problem!