DFS Snap-In Cannot Find DFS Root In Simulated Machine Failure Scenario

I have a question regarding DFS.

Here is my setup:
2 DCs running Server 2003, named DC1 and DC2 respectively.
DC1 is the first domain controller.
Both DCs have the global catalog.
I have created a DFS root on DC1 and a root target replicated on DC2.
There are also numerous DFS links, which were also replicated on DC2.

To simulate a failure scenario, I shut off DC1.
All the DFS links can still be accessed.
However, if I try to fire up the DFS MMC Snap-In on DC2, it complained not being able to find the DFS root.
My understanding was, since the DFS root was replicated on DC2, even if DC1 fails, I can still manage the DFS with the DFS Snap-In running on DC2. This is not the case now.

Does anyone know the answer to this one.

David

cmykdpAsked:
Who is Participating?
 
Netman66Connect With a Mentor Commented:
This is by design.  There is only one root server and when it goes offline, the replicas will function but management is tied to the root server and therefore inaccessible.

Not sure if or when this is going to be addressed but what you are seeing now is the same thing I can replicate here on a base configuration.

Think of the root server as similar to a FSMO role holder.

0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.