explorerjimmy1979
asked on
Windows Server 2003 R2 DFS Management show me Error of the Namespaces
Hi all,
I have two W2K3 R2 server , and before make the DFS on the product environment, I make the Lab for test...
The first server is GC AD, it work ok, and the DFS, DNS also work on the Namespaces
The second server, join to the first AD domain, installed the DFS and DNS, the DFS Copy (Replication) also work on both server.
So I test the fail .., then I shut down the first server, reboot the second server and waiting for30 minutes to reboot the second server again (First server still down)
Now I open the DFS Management ---> Namespaces --> \\domain.local\Public
It show me that
"Error
\\domain.local\Public: The namespace cannot be queried. The specified domain either does not exist or could not be contacted.
I am following Microsoft's Official Document and example to do the Lab, so the namespaces have setting on both first and second server for failed using .. Why now it show up the error and no the Menu for me to setting?
Thank you.
I have two W2K3 R2 server , and before make the DFS on the product environment, I make the Lab for test...
The first server is GC AD, it work ok, and the DFS, DNS also work on the Namespaces
The second server, join to the first AD domain, installed the DFS and DNS, the DFS Copy (Replication) also work on both server.
So I test the fail .., then I shut down the first server, reboot the second server and waiting for30 minutes to reboot the second server again (First server still down)
Now I open the DFS Management ---> Namespaces --> \\domain.local\Public
It show me that
"Error
\\domain.local\Public: The namespace cannot be queried. The specified domain either does not exist or could not be contacted.
I am following Microsoft's Official Document and example to do the Lab, so the namespaces have setting on both first and second server for failed using .. Why now it show up the error and no the Menu for me to setting?
Thank you.
ASKER
Hi ChiefIT,
The DNS setting I am setting on the NIC is point to the First Server (Shut Down One)
192.168.218.161 (First Server)
192.168.218.162 (Second Server)
Do it is the reason?
The DNS work, just the DFS Management Interface not work ...
Since I can using other workstation enter \\domain.local\Public to access the DFS Share and read write here.
The DNS setting I am setting on the NIC is point to the First Server (Shut Down One)
192.168.218.161 (First Server)
192.168.218.162 (Second Server)
Do it is the reason?
The DNS work, just the DFS Management Interface not work ...
Since I can using other workstation enter \\domain.local\Public to access the DFS Share and read write here.
ASKER
But if I power on the first server, the second server can show the Management Interface to let me change setting.
Microsoft said DFS can work well when one server failed, why the function work, but the DFS Management not work so I can not add other Namespace Target after the first server shut down for the Lab Sample...
Microsoft said DFS can work well when one server failed, why the function work, but the DFS Management not work so I can not add other Namespace Target after the first server shut down for the Lab Sample...
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Can't contact server usually means there is no DNS record for the server. Go to the command prompt of the server and type:
IPconfig /register DNS
Then, net stop netlogon
Then, net start netlogon
Force replicate your DNS record form that server to the other domain controller.