This is an excellent case to do a network trace. People may be getting sick of me saying this but it cuts out all of the guesswork of the other 15 or so posts. Slap the server on a shared hub or plug into your mirror port and do a trace of the logon while the other DC is down or rebooting or whatever case you find causes the slowness. You will most likely see requests directed to this server and you have to then just figure out what kind of requests they are and why they would be going to that server. Much better than trying to guess around what kind of configuration you have. You could possibly find it with this guessing but generally that involves changing things until it works which is always bad news.
Get a trace, tell us what kind of traffic is going to that rebooting box and not being responded to. joe -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Salandra, Justin A. Sent: Wednesday, February 11, 2004 1:14 PM To: ActiveDir (E-mail) Subject: [ActiveDir] Domain Naming Server FSOM I have noticed that logons take an enourmous amount of time on non DC Windows 2000 Servers if the Server running the Domain Naming Master is rebooting. Why is this? Justin A. Salandra, MCSE Senior Network Engineer Catholic Healthcare System 212.752.7300 - office 917.455.0110 - cell [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> List info : http://www.activedir.org/mail_list.htm List FAQ : http://www.activedir.org/list_faq.htm List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/ List info : http://www.activedir.org/mail_list.htm List FAQ : http://www.activedir.org/list_faq.htm List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/
