This one's a bit complicated, so I'm going to do my best to break down the issue into small, bite-sized chunks. If anything isn't clear, I'll be happy to try and clarify.
Our company has 2 domain controllers, Apollo and Artemis. For the last few months, when Apollo is reboot, the domain goes offline, as if Artemis weren't even there. Users can't log in, Exchange stops responding to user requests, and so on.
When the server, Apollo, comes back up, the Netlogon service is in a paused state, and the network won't start operating properly again until someone logs onto Apollo at the console, and then restarts the network service. This leaves the following event in my event logs:
Event Type: Error
Event Source: NTDS General
Event Category: Service Control
Event ID: 2103
Time: 9:24:34 AM
User: NT AUTHORITY\ANONYMOUS LOGON
The Active Directory database has been restored using an unsupported restoration procedure.
Active Directory will be unable to log on users while this condition persists. As a result, the Net Logon service has paused.
After a little digging on this and other websites, I found that this can be caused by MS DTC not properly recognizing a DC promotion/demotion, and I found event logs to support that theory, and following the suggestions in this post (http://www.experts-exchange.com/Operating_Systems/Windows_Server_2003/Q_21589620.html?query=MS+DTC+could+not+correctly+process+a+DC+Promotion%2FDemotion+event.+MS+DTC+will+continue+to+function+and+will+use+the+existing+security+settings.&clearTAFilter=true
) I managed to clear that error.
There *had* been an issue where Artemis had to undergo a forced demotion (both servers thought they were PDCEmulators), and I'm assuming the MSDTC errors were a leftover fragment of that.
Aftre making the registry changes listed in the link above, I reboot Apollo, only to find that the domain still "dies" when Apollo is reboot (apparently when the netlogon service stops, sinc e restarting that service seems to repair everything).
So now I turn to the experts. I've not been able to come up with any answers on how to repair this issue, so I'm hoping someone else has seen this or something like it.
Thanks in advance, everyone.