Question Locked

2nd 2003 domain controller looses communications with Active Directories wh

0 helpful
3 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I have setup a second domain controller in a 2003 environment for redundancy. I installed AD and DNS on the second DC. When I bring the first DC down for maintenance the second Dc looses communication with AD. Is there a configuration step that I may have missed to keep the Domain alive on the second DC. The error that I receive is

Naming information cannot be located because.
The specified domain either does not exist or could not be contacted.
Contact your system administrator to verify that your domain is properly configured and is currently online

3 replies

by dumphrey

and make sure there is a service record for the second DC as well as the primary DC.

by cg it

Domain controllers in an Active Directory network are peers.

If your trying for redundancy where users are able to continue accessing resources on the network and continue logging in, then you need to assign the DC the Global catalog role and make sure you have the sysvol and netlogon shares available.

Without the global catalog role and the sysvol and netlogon shares available to users, uses can not login to the network.

Further, you secondary DNS server needs to be listed as a DNS server that uses can query for name resolution.

There are 5 roles a DC can have.
Schema master
Domain naming master
RID master
PDC emulator
Infrastructure daemon

Suggest you read this MS KB on FSMO roles

http://support.microsoft.com/kb/223346/

and this article on sysvol and netlogon shares

http://support.microsoft.com/kb/257338/en-us

This discussion is closed to new replies.