W2K Domain Controller very slow to reboot

[AndyMac]

We have a lot of W2K domain controllers on ISDN2 and 2Mb/s connected sites.
All DC's run local DNS for AD resolution which is set to then forward on to a remote central DNS for resolution of all other queries. DNS is configured 'manually' when installing as it is not always convenient to have the server connected to the network when installing and thus it would not find the root servers, create itself as root etc etc
The server's IP config is to point to itself as the first DNS server and then on to the 2 remote DNS servers as 2nd and 3rd in the list.
The problem we have is that on around 50% of the servers that are installed a reboot can take 10 minutes. The server either displays the 'preparing network connections' message or a blank screen and has random bursts of disk activity. When the server finally does display a login box and you log in the performance is fine, and not consistant with a DNS / AD problem.
My initial thought was that the server was trying to find the root domain servers and having no joy becuase the ISDN line was down. But removing references to all other DNS servers does nothing. What is confusing is that not all servers do this.
Any suggestions greatfully received!

AndyMac

 

[CoolClark]

Check your event log and make sure your not getting any errors. I was having the same problem until I researched and fixed all the minor errors I was getting.

 

[Evilbart]

W2k uses kerberos, which it finds in Global Catalog servers, I think you should look how many GC servers there are in your organization, where they are located and so on
Also use a time server (kerberos checks time stamps!!)
Hope this pushes you some further in the right direction...

sincerely, Bart