DFS points to wrong site -- no servers moved

[Jim Davis]

Many clients are getting pointed to the wrong site when accessing DFS,
and I'm terribly confused by it. All the help I can find indicate
either that I've moved a server and it needs refreshing (nope) or that I
should enable /insite (which kind of bones failover).

There only two sites set up, with a 2k DC at each. There are other
servers that some of the DFS shares point to; for instance,

site A: DC-A SERVER-A
site B: DC-B SERVER-B

\\domain\DFSROOT$\gravy ->
\\DC-A\gravy$
\\SERVER-B\gravy$

\\domain\DFSROOT$\butter ->
\\DC-A\butter$
\\DC-B\butter$

(and so forth like that)

Regularly, users at site A seem to be accessing \\DC-B\butter$ or
\\SERVER-B\gravy$, and vice-versa. DCDIAG on the domain controllers
only reports one error:

Starting test: frssysvol
There are errors after the SYSVOL has been shared.
The SYSVOL can prevent the AD from starting.

However, SYSVOL appears to be shared properly on both DCs.

- I believe the sites are set up correctly--all the subnets are in their
proper sites in ADS&S.

- DFSUTIL /PKTFLUSH clears the problem temporarily, but the workstation
might get it right on the next boot, and it might not.

- The servers don't have "restrictanonymous" set to 2.

- nltest /dsgetsite reports the correct site for the servers and clients
involved.

What can I do?

 

[Jill Zoeller [MSFT]]

You may have seen this already, but we have a blog post that covers common
misdirection causes at
https://blogs.technet.com/filecab/archive/2006/04/13/425169.aspx.

If this doesn't help, you might want to open a support case with product
support. They can help you troubleshoot this particularly tricky problem.



--
This posting is provided "AS IS" with no warranties, and confers no rights.

Want to learn more about Windows Server file and storage technologies? Visit
our team blog at http://blogs.technet.com/filecab/default.aspx.