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

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.
0
explorerjimmy1979
Asked:
explorerjimmy1979
  • 2
  • 2
1 Solution
 
ChiefITCommented:
Sounds like you don't have your DNS records correct:

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.
0
 
explorerjimmy1979Author Commented:
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.
0
 
explorerjimmy1979Author Commented:
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...
0
 
ChiefITCommented:
Having one server off will not allow you to add another namespace or manage it through DFS console. You might want to read this article, that says:

"The behavior is unchanged - if the PDCE is offline, DFS will continue to
work as a system, but you will no longer be able to manage it through the
snap-in. In the new DFS management console you get an error on this
(specified domain does not exist or could not be contacted) when you browse
the namespace. In the legacy DFS console, you see no namespaces with no
errors - as you probably already know!

To explain why the PDCE is used:

Domain-based DFS stores its namespace information in a binary blob attribute
in AD called 'pKT'. Since this is a single attribute, it's necessary to
force all the standard management tools to go to a single DC for editing
purposes. Otherwise if we had two admins editing DFS at the same time, on
two different DC's, the admin that saved last would overwrite all the
changes made by the other admin when replication converged."

http://www.petri.co.il/forums/showthread.php?t=7335
0

Featured Post

2018 Annual Membership Survey

Here at Experts Exchange, we strive to give members the best experience. Help us improve the site by taking this survey today! (Bonus: Be entered to win a great tech prize for participating!)

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