If a Windows Server 2003 domain controller, during startup or reboot, hangs for a long time at the "preparing network connections" stage, while responding to ping but not letting you in via RDP.
1) Check which DNS server is listed first. If you are using "127.0.0.1" as the DNS server (since a domain controller carries the Active Directory DNS service by default), this machine may take up to 20 minutes to boot. As soon as you set another controller as the first DNS server (for example, in an X setup - controller A has server B as its DNS server, and controller B has server A as its DNS server) - it will immediately start rebooting quickly and smoothly.
2) If a neighboring controller is listed as the first DNS server - check whether it is actually on the network. If the controllers are located in different geographic locations and the connection between them drops out and is unavailable while the controller is booting - it will stall and search for its "kindred spirit"... it may search for up to 20 minutes, after which it gives up and boots anyway.
What to do if it is currently hanging for a long time at "preparing network connections"?
Wait. Up to 20-25 minutes. And do not touch it. And if after 25 minutes it still has not started - only then start taking action. It is possible that it has lost connection with the other "kindred spirits", for example, due to a network failure. In that case this piece of Microsoft software will stall for a long time and will really only come to its senses after 20-25 minutes.
Comments