Microsoft KB Archive/938449

= Event ID 5719 is logged when you start a computer on a domain, and the computer is running Windows Server 2003, Windows XP, or Windows 2000 =

Article ID: 938449

Article Last Modified on 6/21/2007

-

APPLIES TO


 * Microsoft Windows Server 2003, Enterprise Edition (32-bit x86)
 * Microsoft Windows Server 2003, Standard Edition (32-bit x86)
 * Microsoft Windows XP Professional
 * Microsoft Windows XP Home Edition
 * Microsoft Windows 2000 Advanced Server
 * Microsoft Windows 2000 Server
 * Microsoft Windows 2000 Professional Edition

-



Important This article contains information about how to modify the registry. Make sure that you back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base:

256986 Description of the Microsoft Windows registry



SYMPTOMS
Consider the following scenario:
 * You have a computer that is running one of the operating systems that is mentioned in the “Applies to” section.
 * The computer is joined to a domain.
 * The computer has a 1-gigabyte (GB) network adapter installed.

In this scenario, the following event is logged in the System log when you start the computer:

Event Type: Error

Event Source: NETLOGON

Event Category: None

Event ID: 5719

Date:

Time:

User: N/A

Computer: Server

Description:

No Domain Controller is available for domain  due to the following: There are currently no logon servers available to service the logon request. Make sure that the computer is connected to the network and try again. If the problem persists, please contact your domain administrator.



CAUSE
When you use a 1-GB network adapter in this scenario, the Netlogon service starts before the network is ready.



RESOLUTION
Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall the operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.To resolve this issue, follow these steps:  Click Start, click Run, type regedit in the Open box, and then click OK. In Registry Editor, locate the following subkey, and then click it:

 

 In the details pane, double-click DependOnService. In the Value data box, type TermService on a new line, and then click OK. Close Registry Editor. Restart the computer.</li></ol>

<div class="moreinformation_section">

MORE INFORMATION
If you can correctly log on to the domain, you can safely ignore event ID 5719.

Because the Netlogon service may start before the network is ready, the computer may be unable to locate the logon domain controller. Therefore, event ID 5719 is logged. However, after the network is ready, the computer will try again to locate the logon domain controller. In this situation, the operation should be successful.

Keywords: kbexpertiseinter kbtshoot kbprb KB938449

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.