Link to home
Start Free TrialLog in
Avatar of atlbearcat
atlbearcat

asked on

Domain Controller Replication

We have several remote sites and 1 site in particular only has 1 2003 domain controller. This domain controller went down and users were not able to authenticate. In active directory sites and services this Site only has this 1 DC listed there. Replication is setup and is working as it is connected to one of our other domain controllers. My question is what is best practice to setup up redundancy for authentication. Is this failing because we only have 1 DC in this remote site listing? Is there an alternative to actually adding a second DC in this site?
Avatar of motnahp00
motnahp00
Flag of United States of America image

Best practice is to have two DCs per site to provide redundancy in the event 1 DC crashes.

All you have to do to add a 2nd DC to a site is promote a member server using DCPROMO.
How many domains do you have?  If more than one, do you have redundant Global Catalogs?

When the 2003 Domain Controller is back up, can you open a command prompt window on it and run:
dcdiag /v /c

Open in new window

If the domain is setup properly, the DCLOCATOR process should allow clients in one site to failover to using a domain controller in another site, in situations where their nearest site DC is down. But many things can hinder this process.

Which operating systems were the users using that failed to authenticate?

This thread discusses your issue, and at the bottom offers some fixes.
http://social.technet.microsoft.com/Forums/en/winserverDS/thread/746d5492-e08b-40a7-8d46-8b3b53b2f3e5

But as motnahp00 pointed out above, it's ALWAYS best to have two or more DC's per site.
ASKER CERTIFIED SOLUTION
Avatar of atlbearcat
atlbearcat

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of atlbearcat
atlbearcat

ASKER

Thread helped