• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1729
  • Last Modified:

DFS Namespace failover

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.

EXAMPLE:
\\domain.local\dfs
\\domain.local\dfs\Share1 (primary source on 2008r2)
\\domain.local\dfs\Share2 (primary source on 2003r2)

\\2008r2\Share1
\\2008r2\Share2 (replicated from 2003r2)

\\2003r2\Share2
\\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?  

Thanks!
0
MorefieldIT
Asked:
MorefieldIT
  • 2
1 Solution
 
arnoldCommented:
The DFS versions are one issue to address. I.e. win2k3r2 is the version
Check DFS version.
http://blogs.technet.com/b/josebda/archive/2009/07/15/five-ways-to-check-your-dfs-namespaces-dfs-n-configuration-with-the-dfsdiag-exe-tool.aspx

When possible use similar OS versions.

Are the two servers just name space servers or are they DCs as well?
0
 
MorefieldITAuthor Commented:
Following the examples in the link provided i got the following warnings:
-dfsdiag /testdcs
Warning: the registry values under HKLM\CCS\Services\Dfs\Parameters ae not consistent on all compared servers.
Warning the server has IP addresses with conflicting site associations. (IPV6)
-dfsdiag /testsites on 2008
Warning the server has IP addresses with conflicting site associations. (IPV6)
-dfsdiag /testdfsconfig
Warning: the registry values under HKLM\CCS\Services\Dfs\Parameters ae not consistent on all compared servers.
-dfsdaig /testreferral
same warnings as above commands.


Both computers are domain controllers.  It seems that only when the PDC goes "down" is when the other namespace server cannot manage and control the dfs root namespace.
0
 
arnoldCommented:
You could ipv6 protocol support to the windows 2003 networkmnterface to make it cosistent.
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.

Join & Write a Comment

Featured Post

Cloud Class® Course: MCSA MCSE Windows Server 2012

This course teaches how to install and configure Windows Server 2012 R2.  It is the first step on your path to becoming a Microsoft Certified Solutions Expert (MCSE).

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now