Issues with DFS/DFS Management console

I have two servers, both member servers of a domain I'll call
mydomain.org. One server is W2K3 R2 SP2, and the other is W2K3 SP2.
These servers are in separate AD sites. I am attempting to create a
Domain based DFS Namespace and setup both of these servers as
Namespace servers for the DFS Namespace.
Information Details:
Domain: mydomain.org, W2K3 with AD Schema updated to R2, Two DCs, part
of a forest.
Server1: W2K3 R2 SP2, AD Site1, member server of mydomain.org
Server2: W2K3 SP2, AD Site 2, member server of mydomain.org

I can log onto either of the servers and using the DFS Management
console create a DFS namespace and setup either of the servers to be a
namespace server for it. For example I can do the following:
1) I can log into Server1, setup a Domain based DFS namespace with a
DFS Root of Test1 and make Server1 the namespace server for it.
2) I can log into Server1, setup a Domain based DFS namespace with a
DFS Root of Test2 and make Server2 the namespace server for it
3) I can log into Server2, setup a Domain based DFS namespace with a
DFS Root of Test3 and make Server1 the namespace server for it.
4) I can log into Server2, setup a Domain based DFS namespace with a
DFS Root of Test4 and make Server2 the namespace server for it

My problem is that I cannot setup a second DFS Namespace Server for
any of the above created DFS Namespaces. When I try to add the other
server as a Namespace server I get:
Contacting the server. Success
Verify server name. Error

If I look at the Errors tab, I get "Computer Server1 does not belong
to domain mydomain.org" Obviously both servers are members of
mydomain.org, I can even browse for the server at the Add Namespace
Server dialog when attempting to setup an additional server to be a
Namespace server. I have tried every combination of adding a second
namespace server to all of the above DFS namespaces, all fail with a
similar error.

Anyone have any ideas why this is occurring? I have several other DFS
namespaces setup in this same way in other domains in our forest.

.

Relevant Pages

  • Re: .local and .com
    ... I would NOT recommend using the .local namespace, ... sub-namespace of your publicly registered namespace. ... Split DNS ~ For running internal network in same namespace as internet ... > We will be implementing a Windows Small Business 2003 Server using> Exchange ...
    (microsoft.public.windows.server.dns)
  • Re: DNS dfs issue
    ... that the namespace server, decommissioned the problematic DC/DNS. ... It seems to depend on the dns, but they should be the same. ... every client at Site B is affected. ...
    (microsoft.public.windows.server.dns)
  • Re: DNS dfs issue
    ... Put up a new DC/DNS box in the site and made that the namespace server, ... because the results depend on the dns not the logon server. ... This suggests it must be a client setting that affects the ability to resolve the namespace. ...
    (microsoft.public.windows.server.dns)
  • Re: "Insufficient state to deserialize the object" error
    ... code snippet I sent is called "Inexus.dll" (namespace INexusStuff). ... on the Client side. ... Back on the Server side there is another module with the ... The code containing the Server side delegate, ...
    (microsoft.public.dotnet.framework.remoting)
  • Re: DFS Restructure
    ... To keep the namespace intact, make sure the current w2k8 have a mirror of the dfs namespace, so that if w2k3 is offline, users can still access namespace via w2k8.I am assuming that you have domain base namespace. ... We need to decomission the 2003 server without ...
    (microsoft.public.windows.server.general)