Log on to first DC (FSMO holder) had naming information could not be located, needs second DC to boot up
We have two domain controllers (windows 2003 standard) on one site. Recently we had a significant power outage and both server had a forced shut down. On rebooting the first domain controller it hung on “Preparing Network Connections” for a long time but eventually got me to the point where I could log on. However, when trying to access AD Users and Computers I got the following error.
“Naming information could not be located because: The specified domain either does not exist or could not be contacted. Contact your system administrator to verify that the domain is properly configured and is currently online.”
It is not until the other DC has fully booted into Windows that AD instantly becomes available on the first DC. Interestingly, once the first DC has found the domain, the second DC can be shut down without any effect. Each DC looks to itself as the preferred DNS server and the other as its alternate.
We have found a Microsoft article that refers to changing a registry setting …..
Value name: Repl Perform Initial Synchronizations
Value type: REG_DWORD
Value data: 0”
But warns that …..
“This configuration change is not recommended for use in production environments or in any environment on an ongoing basis.”
Does anyone have any suggestions as to why this is happening and how we can set up so that either DC can function fully regardless of the condition of the other? I am particularly concerned about how we would handle one of the DCs dying and leaving us with no working AD.