?
Solved

Log on to first DC (FSMO holder) had naming information could not be located, needs second DC to boot up

Posted on 2013-01-14
3
Medium Priority
?
301 Views
Last Modified: 2013-08-17
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 …..
“HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NTDS\Parameters
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.
0
Comment
Question by:vanderfield
  • 2
3 Comments
 
LVL 84

Expert Comment

by:David Johnson, CD, MVP
ID: 38776857
Which domain controller holds the fmso roles? Guessing #2, ensure that you don't keep the #2 DC offline too long or it will tombstone.
0
 

Accepted Solution

by:
vanderfield earned 0 total points
ID: 38776864
ve3ofa,

it's the first DC (FSMO holder), additionally saw this article that explains this Initial Synchronization of FSMO Owners
 
When a DC that owns a FSMO role boots up, it must complete inbound replication with its known replication partners before it will operate as the FSMO master. Specifically, it must replicate the partition that contains the FSMO role the DC owns. For example, if a DC holds either or both of the forest wide operations masters (the Domain Naming or Schema master), then that DC must successfully replicate the Configuration partition of Active Directory. Similarly, if the DC holds one or more of the domain specific FSMO roles (RID, PDC, Infrastructure) then that DC must successfully replicate the domain partition at startup before it will function as that operations master. See: http://support.microsoft.com/kb/305476
0
 

Author Closing Comment

by:vanderfield
ID: 39416452
the concerned DC would boot up properly along side it's replication partner locally
0

Featured Post

[Webinar] Cloud and Mobile-First Strategy

Maybe you’ve fully adopted the cloud since the beginning. Or maybe you started with on-prem resources but are pursuing a “cloud and mobile first” strategy. Getting to that end state has its challenges. Discover how to build out a 100% cloud and mobile IT strategy in this webinar.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This is a little timesaver I have been using for setting up Microsoft Small Business Server (SBS) in the simplest possible way. It may not be appropriate for every customer. However, when you get a situation where the person who owns the server is i…
Setting up a Microsoft WSUS update system is free relatively speaking if you have hard disk space and processor capacity.   However, WSUS can be a blessing and a curse. For example, there is nothing worse than approving updates and they just have…
Windows 8 came with a dramatically different user interface known as Metro. Notably missing from that interface was a Start button and Start Menu. Microsoft responded to negative user feedback of the Metro interface, bringing back the Start button a…
With the advent of Windows 10, Microsoft is pushing a Get Windows 10 icon into the notification area (system tray) of qualifying computers. There are many reasons for wanting to remove this icon. This two-part Experts Exchange video Micro Tutorial s…
Suggested Courses

850 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question