DFS Namespace / Windows Server 2008 R2 / Win 8 – missing entries

dfswindows-server-2008-r2

We have a DFS namespace at \\company.example.org\dfs\ and inside that are entries for half a dozen folders. There is one namespace server, and no replication. The shares are all now on one server. Very basic.

I use Windows 8 Pro as a desktop, with a drive mapped to \\company.example.org\dfs\companyshare\

Suddenly, and arbitrarily, it stops working, with the error "Windows cannot access \\company.example.org\dfs\companyshare\"

I browse to the \dfs\ namespace folder, only one of the endpoint entries is there, the rest are missing. I can ping the namespace server and browse to the share as \server\share.

After a few minutes … they reappear. Or I reboot, and it works again. This seems to happen on more than one Windows 8 client, but not on Windows 7.

I have run the DFSDiag tests linked, and they all come back fine.

In the properties of the \company.example.org\dfs folder, on the DFS tab, I see one entry in the referral list, which is active and status "Okay".

There are three domain controllers, 2008 R2 twice and 2008. All service packed and updated.

No event log errors that I can find on server or client.

Summary: Win 8 drops most of the DFS endpoints, and then a few minutes later, refreshes them. Nothing else seems to be wrong.

Where can I look for more information?

[Update: So far I have used the dfsutil diagnostics from TheFiddlerWins' answer, and found absolutely nothing. The only progress I've made is realising that the virtual machine in question still had 1 core and 3GB of RAM assigned, and now I've moved lots of roles onto it (printers, several heavy file shares), that was rather underpowered. Since increasing the available CPU and RAM for the machine last week, I haven't noticed this issue occuring again. Too early to say for sure that it's gone, but it might be that simple].

Best Answer

DFS (for some ungodly reason) uses NetBIOS style names (DOMAIN instead of domain.com) by default. This document from Microsoft tells you how to fix it. I suspect your issue is that at times it's able to resolve these names (via WINS, broadcasts etc) and other times not.

If that is not it try following this doc on DFS troubleshooting.