Our primary Windows 2003 R2 Server takes an extremely long time to .
The server will first hang quite a while at the "preparing network
connections" prompt, and then again at the "applying computer settings"
prompt. It will eventually bring up the login prompt and allow me to
log in, but once in, I can see a number of alerts in both the
Application and System Event Logs, and additionally I have to manually
start the Server for NIS service.

One of the first errors I see in the Event Log is this:

Event Type: Warning
Event Source: LSASRV
Event Category: SPNEGO (Negotiator)
Event ID: 40960
Date: 5/3/2008
Time: 4:22:11 PM
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)".

And also this error:

Event Type: Warning
Event Source: NtFrs
Event Category: None
Event ID: 13512
Date: 5/3/2008
Time: 4:31:39 PM
User: N/A
Computer: SERVER1
Description:
The File Replication Service has detected an enabled disk write cache on
the drive containing the directory c:\windows\ntfrs\jet on the computer
SERVER1. The File Replication Service might not recover when power to
the drive is interrupted and critical updates are lost.

This server also holds all the FSMO roles for my AD 2003 domain.

We have a second redundant DC in our domain which provides nearly all
the same services as the primary DC, but it doesn't take nearly as long
to boot from a cold start as the primary does.

Both servers have exactly the same hardware profile, so I'm trying to
determine what is causing such a delay in keeping our main DC from
completely booting from a cold start.

Any ideas? Both servers configured with mirrored boot drives. Should I
be disable the disk write cache function on the RAID controller?

Hello Rob,

Please post an unedited ipconfig /all from both servers.

If 40960 or also 40961 is only after a reboot you can safely ignore it.
http://support.microsoft.com/kb/824217

13512 is also an informational Warning
http://support.microsoft.com/kb/316504

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

> Our primary Windows 2003 R2 Server takes an extremely long time to .
> The server will first hang quite a while at the "preparing network
> connections" prompt, and then again at the "applying computer
> settings"
> prompt. It will eventually bring up the login prompt and allow me to
> log in, but once in, I can see a number of alerts in both the
> Application and System Event Logs, and additionally I have to manually
> start the Server for NIS service.
> One of the first errors I see in the Event Log is this:
>
> Event Type: Warning
> Event Source: LSASRV
> Event Category: SPNEGO (Negotiator)
> Event ID: 40960
> Date: 5/3/2008
> Time: 4:22:11 PM
> 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)".
> And also this error:
>
> Event Type: Warning
> Event Source: NtFrs
> Event Category: None
> Event ID: 13512
> Date: 5/3/2008
> Time: 4:31:39 PM
> User: N/A
> Computer: SERVER1
> Description:
> The File Replication Service has detected an enabled disk write cache
> on
> the drive containing the directory c:\windows\ntfrs\jet on the
> computer
> SERVER1. The File Replication Service might not recover when power to
> the drive is interrupted and critical updates are lost.
> This server also holds all the FSMO roles for my AD 2003 domain.
>
> We have a second redundant DC in our domain which provides nearly all
> the same services as the primary DC, but it doesn't take nearly as
> long to boot from a cold start as the primary does.
>
> Both servers have exactly the same hardware profile, so I'm trying to
> determine what is causing such a delay in keeping our main DC from
> completely booting from a cold start.
>
> Any ideas? Both servers configured with mirrored boot drives. Should
> I be disable the disk write cache function on the RAID controller?
>