Guest John Posted February 19, 2008 Posted February 19, 2008 Here's what I have in a single Win2003 domain: Server1 (192.168.1.8): Windows Server 2003 R2 SP2 AD Controller (FSMO role holder) DNS server installed IP settings: preferred DNS points to itself (192.168.1.8), alternate points to Server2 (192.168.1.6) Server2 (192.168.1.6): Windows Server 2003 R2 SP2 AD Controller DNS server installed IP settings: preferred DNS points to Server1 (192.168.1.8), alternate points to itself (192.168.1.6) Why does Server1 take 5 to 7 minutes to show "preparing network connections..." (when Server2 is off)?? Event viewer shows that there is a problem contacting a logon server but Server1 IS a domain controller (both of them are DCs). When Server2 is already on, Server1 boots up faster (less than 1 minute to show "preparing network connections..." window). There are no warnings in the event viewer. Similarly, Server2 shows the same slowness when booting up while Server1 is offline. Problem disappears if Server1 is already turned on. Let me know if I leave out important info. ------------------------------- Here are 3 warnings when Server1 boots up while Server2 is offline (turned off): Event Type: Warning Event Source: LSASRV Event Category: SPNEGO (Negotiator) Event ID: 40960 Date: 2/19/2008 Time: 8:21:53 AM User: N/A Computer: SERVER1 Description: The Security System detected an authentication error for the server LDAP/SERVER1. The failure code from authentication protocol Kerberos was "There are currently no logon servers available to service the logon request. (0xc000005e)". For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. Data: 0000: 5e 00 00 c0 ^..À Event Type: Warning Event Source: LSASRV Event Category: SPNEGO (Negotiator) Event ID: 40960 Date: 2/19/2008 Time: 8:22:00 AM User: N/A Computer: SERVER1 Description: The Security System detected an authentication error for the server LDAP/Localhost. The failure code from authentication protocol Kerberos was "There are currently no logon servers available to service the logon request. (0xc000005e)". For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. Data: 0000: 5e 00 00 c0 ^..À Event Type: Warning Event Source: LSASRV Event Category: SPNEGO (Negotiator) Event ID: 40960 Date: 2/19/2008 Time: 8:22:02 AM User: N/A Computer: SERVER1 Description: The Security System detected an authentication error for the server ldap/SERVER1.our-domain.com. The failure code from authentication protocol Kerberos was "There are currently no logon servers available to service the logon request. (0xc000005e)". For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. Data: 0000: 5e 00 00 c0 ^..À
Guest Meinolf Weber Posted February 20, 2008 Posted February 20, 2008 Re: Slow Start Hello John" a, This depends on the startup of the DNS server service of the DC itself. Before the service is started the dc searches for another DNS server which is not available and if the DNS server service is running it will use itself. Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties, and confers no rights. ** Please do NOT email, only reply to Newsgroups ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm > Here's what I have in a single Win2003 domain: > > Server1 (192.168.1.8): > Windows Server 2003 R2 SP2 > AD Controller (FSMO role holder) > DNS server installed > IP settings: preferred DNS points to itself (192.168.1.8), alternate > points > to Server2 (192.168.1.6) > Server2 (192.168.1.6): > Windows Server 2003 R2 SP2 > AD Controller > DNS server installed > IP settings: preferred DNS points to Server1 (192.168.1.8), alternate > points > to itself (192.168.1.6) > Why does Server1 take 5 to 7 minutes to show "preparing network > connections..." (when Server2 is off)?? Event viewer shows that there > is a problem contacting a logon server but Server1 IS a domain > controller (both of them are DCs). When Server2 is already on, Server1 > boots up faster (less than 1 minute to show "preparing network > connections..." window). There are no warnings in the event viewer. > > Similarly, Server2 shows the same slowness when booting up while > Server1 is offline. Problem disappears if Server1 is already turned > on. > > Let me know if I leave out important info. > ------------------------------- > Here are 3 warnings when Server1 boots up while Server2 is offline > (turned off): > > Event Type: Warning > Event Source: LSASRV > Event Category: SPNEGO (Negotiator) > Event ID: 40960 > Date: 2/19/2008 > Time: 8:21:53 AM > User: N/A > Computer: SERVER1 > Description: > The Security System detected an authentication error for the server > LDAP/SERVER1. The failure code from authentication protocol Kerberos > was > "There are currently no logon servers available to service the logon > request. > (0xc000005e)". > For more information, see Help and Support Center at > http://go.microsoft.com/fwlink/events.asp. > Data: > 0000: 5e 00 00 c0 ^..À > Event Type: Warning > Event Source: LSASRV > Event Category: SPNEGO (Negotiator) > Event ID: 40960 > Date: 2/19/2008 > Time: 8:22:00 AM > User: N/A > Computer: SERVER1 > Description: > The Security System detected an authentication error for the server > LDAP/Localhost. The failure code from authentication protocol > Kerberos was > "There are currently no logon servers available to service the logon > request. > (0xc000005e)". > For more information, see Help and Support Center at > http://go.microsoft.com/fwlink/events.asp. > Data: > 0000: 5e 00 00 c0 ^..À > Event Type: Warning > Event Source: LSASRV > Event Category: SPNEGO (Negotiator) > Event ID: 40960 > Date: 2/19/2008 > Time: 8:22:02 AM > User: N/A > Computer: SERVER1 > Description: > The Security System detected an authentication error for the server > ldap/SERVER1.our-domain.com. The failure code from authentication > protocol > Kerberos was "There are currently no logon servers available to > service the > logon request. > (0xc000005e)". > For more information, see Help and Support Center at > http://go.microsoft.com/fwlink/events.asp. > Data: > 0000: 5e 00 00 c0 ^..À
Guest John Posted February 20, 2008 Posted February 20, 2008 Re: Slow Start That's what I thought too. I can clearly see DNS service starts a few minutes after I those warnings popped up. If that is the case, is there a way to prioritize DNS server service so that it kicks in as fast as possible? Seems like every Windows Server 2003 that I build (from scratch) shows the same symptoms when there are 2 domain controllers working together. If there's only 1 server, Win2003 starts very fast. As soon as I put another one there, Win2003 slows down considerably when 1 of them boots up while the other is down. "Meinolf Weber" <meiweb(nospam)@gmx.de> wrote in message news:ff16fb66894fd8ca41ca5b2e4d94@msnews.microsoft.com... > Hello John" a, > > This depends on the startup of the DNS server service of the DC itself. > Before the service is started the dc searches for another DNS server which > is not available and if the DNS server service is running it will use > itself. > > Best regards > > Meinolf Weber > Disclaimer: This posting is provided "AS IS" with no warranties, and > confers no rights. > ** Please do NOT email, only reply to Newsgroups > ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm > >> Here's what I have in a single Win2003 domain: >> >> Server1 (192.168.1.8): >> Windows Server 2003 R2 SP2 >> AD Controller (FSMO role holder) >> DNS server installed >> IP settings: preferred DNS points to itself (192.168.1.8), alternate >> points >> to Server2 (192.168.1.6) >> Server2 (192.168.1.6): >> Windows Server 2003 R2 SP2 >> AD Controller >> DNS server installed >> IP settings: preferred DNS points to Server1 (192.168.1.8), alternate >> points >> to itself (192.168.1.6) >> Why does Server1 take 5 to 7 minutes to show "preparing network >> connections..." (when Server2 is off)?? Event viewer shows that there >> is a problem contacting a logon server but Server1 IS a domain >> controller (both of them are DCs). When Server2 is already on, Server1 >> boots up faster (less than 1 minute to show "preparing network >> connections..." window). There are no warnings in the event viewer. >> >> Similarly, Server2 shows the same slowness when booting up while >> Server1 is offline. Problem disappears if Server1 is already turned >> on. >> >> Let me know if I leave out important info. >> ------------------------------- >> Here are 3 warnings when Server1 boots up while Server2 is offline >> (turned off): >> >> Event Type: Warning >> Event Source: LSASRV >> Event Category: SPNEGO (Negotiator) >> Event ID: 40960 >> Date: 2/19/2008 >> Time: 8:21:53 AM >> User: N/A >> Computer: SERVER1 >> Description: >> The Security System detected an authentication error for the server >> LDAP/SERVER1. The failure code from authentication protocol Kerberos >> was >> "There are currently no logon servers available to service the logon >> request. >> (0xc000005e)". >> For more information, see Help and Support Center at >> http://go.microsoft.com/fwlink/events.asp. >> Data: >> 0000: 5e 00 00 c0 ^..À >> Event Type: Warning >> Event Source: LSASRV >> Event Category: SPNEGO (Negotiator) >> Event ID: 40960 >> Date: 2/19/2008 >> Time: 8:22:00 AM >> User: N/A >> Computer: SERVER1 >> Description: >> The Security System detected an authentication error for the server >> LDAP/Localhost. The failure code from authentication protocol >> Kerberos was >> "There are currently no logon servers available to service the logon >> request. >> (0xc000005e)". >> For more information, see Help and Support Center at >> http://go.microsoft.com/fwlink/events.asp. >> Data: >> 0000: 5e 00 00 c0 ^..À >> Event Type: Warning >> Event Source: LSASRV >> Event Category: SPNEGO (Negotiator) >> Event ID: 40960 >> Date: 2/19/2008 >> Time: 8:22:02 AM >> User: N/A >> Computer: SERVER1 >> Description: >> The Security System detected an authentication error for the server >> ldap/SERVER1.our-domain.com. The failure code from authentication >> protocol >> Kerberos was "There are currently no logon servers available to >> service the >> logon request. >> (0xc000005e)". >> For more information, see Help and Support Center at >> http://go.microsoft.com/fwlink/events.asp. >> Data: >> 0000: 5e 00 00 c0 ^..À > >
Recommended Posts