DFS Namespace failover
Posted on 2013-05-22
I am testing out DFS for an environment that has a Server 2003R2 PDC, with a Server 2008R2 secondary domain controller.
I created the dfs namespace on the 2008r2 server, added my shared folders and setup the replication between the identically names shared folders on each server. I also added the 2003r2 server as another namespace server to the dfs namespace.
\\domain.local\dfs\Share1 (primary source on 2008r2)
\\domain.local\dfs\Share2 (primary source on 2003r2)
\\2008r2\Share2 (replicated from 2003r2)
\\2003r2\Share1 (replicated from 2008r2)
Everything seems to be working well when both machines are up and running. I can manage the namespace from each server, and each server is sharing and replicating the shares on dfs without issue.
Then I started testing failover and redundancy. When I turned off the 2008r2 server, the 2003r2 picked up the slack, I could mange the namespace still, and I saw that all dfs shares where now active on the 2003r2 box, NEAT! Now, I turned the 2008r2 back on, and again tested everything with both servers up and running, no issues.
Here is where it gets weird. I turned off the 2003r2 server this time. I could still access the \\domain.local\dfs shares, and I noticed that the shares are now active on the 2008r2 machine, great! However, I cannot control the namespace now from the 2008r2 server, I am getting a "namespace cannot be queried" error.
Has anyone come across an issue like this with DFS between 2008 and 2003 ADDS servers?