Solved DFS namespace fails

Microsoft Windows 7 professional 64-bit
November 28, 2011 at 05:30:21
Specs: Windows 2008 R2, 4ghz/12gb
I have a Windows 2008 R2 DFSR environment. The namespace for our local site failed although the underlying shares were still accessible. We lost some ESX hosts this weekend due to storage issues and had some time issues as well. I deleted and recreated the shares and know everything is working but I am trying to figure out why the namespace failed to begin with. I don't see any smoking guns in the event viewer.

Thank you,

Leto the just


See More: DFS namespace fails

Report •


✔ Best Answer
November 30, 2011 at 14:06:31
It's essential for the correct operation of Active Directory that servers clocks are synchronized, and that certainly tallies with the error message that you got. So the first thing that you need to do is to ensure that the clocks on your servers are regularly synchronized from the same time source.


#1
November 28, 2011 at 07:53:47
I notice that servers are recording time events from the DFS server on the servers that can't access the target. If this is a time issue. What do I need to change in DFS if anything to keep it from reoccurring? Is this just a dependency of DFS that I can do nothing to mitigate?

The kerberos client received a KRB_AP_ERR_TKT_NYV error from the server acmedfs01$. This indicates that the ticket used against that server is not yet valid (in relationship to that server time). Contact your system administrator to make sure the client and server times are in sync, and that the KDC in realm ACME.LOCAL is in sync with the KDC in the client realm.

Thank you,

Leto the just


Report •

#2
November 30, 2011 at 11:49:38
I guess the obvious question is whether you have checked the synchronization of the clocks on the servers? It's so obvious that I hesitate to ask, but you don't mention it.

Report •

#3
November 30, 2011 at 12:38:11
Yes, I did check that and there was a difference. I wanted to know if that is simply a dependency of the file share access or DFS.

Thank you,

Leto the just


Report •

Related Solutions

#4
November 30, 2011 at 14:06:31
✔ Best Answer
It's essential for the correct operation of Active Directory that servers clocks are synchronized, and that certainly tallies with the error message that you got. So the first thing that you need to do is to ensure that the clocks on your servers are regularly synchronized from the same time source.

Report •


Ask Question