2

On Tuesday we had a Server 2008 R2 DFS-R node go offline unexpectedly. DFS did the right thing and started routing requests to a different node, which was in a remote site. This is by design, because even though it's slow, at least it's still working.

We had the local DFS-R node back online within an hour, and it had synced all its changes 10 minutes after that.

3 of the 5 terminal servers reset themselves to the local DFS node, but the other two stayed pointing at the remote DFS node for three days, until someone finally piped up about how slow requests were.

DFS Namespace Properties

  1. What reasons could there be why some, but not all, of the server reverted?
  2. Is the currently active DFS node for a namespace exposed anywhere in the OS (WMI, or even scripts) so that we can monitor the active nodes?
Mark Henderson
  • 68,823
  • 31
  • 180
  • 259

2 Answers2

4

So, if I had read what was right under my nose, I would have seen that DFS Clients fail back to preferred target was un-checked:

DFS Failback Checkbox

joeqwerty's answer is great for question #1.

Mark Henderson
  • 68,823
  • 31
  • 180
  • 259
3

As for question 2: The DFS tools can be installed on W2K8 and W2K8R2 and used to run DFSUTIL on the client machine. Running "dfsutil /oldcli /PKTINFO" from a command line (after you've installed the DFS tools) should give you the info you're looking for. Here's a hopefully helpful link:

http://blogs.technet.com/b/josebda/archive/2010/05/02/where-to-find-dfsutil-exe-for-windows-server-2008-and-windows-server-2008-r2.aspx

joeqwerty
  • 109,901
  • 6
  • 81
  • 172