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

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: Date
Time: Time
User: N/A
Computer: Server
Description:
No Domain Controller is available for domain <domain name> 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.

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

Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base: To resolve this issue, follow these steps:

1. Click Start, click Run, type regedit in the Open box, and then click OK.
2. In Registry Editor, locate the following subkey, and then click it:
   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Netlogon
3. In the details pane, double-click DependOnService.
4. In the Value data box, type TermService on a new line, and then click OK.
5. Close Registry Editor.
6. Restart the computer.

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.