Select the product you need help with

Event ID 5719 is logged when you start a computer

Article ID: 938449 - View products that this article applies to.

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 Gigabit network adapter installed.
Or you are using approaches to secure the network access using Network Access Protection (NAP) or similar approaches.
Or you are using network authentication for the computer.

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.

Back to the top | Give Feedback

CAUSE

Cause 1

This issue may occur if you are using a Gigabit network adapter and if the Netlogon service starts before the network is ready.

Cause 2

Solutions that verify the health of the new network member may cause an extended delay in getting clearance on the network to access Domain Controllers.

Cause 3

This issue may occur if the 802.1X authentication process delays connections to the domain controllers.

Cause 4

The client has a delay retrieving an IP address from the DHCP server and is delayed bringing up the network interface because of that.

Back to the top | Give Feedback

RESOLUTION

Resolution 1

To resolve this issue, install the most current driver for the Gigabit network adapter. Another approach may be to enable the "PortFast" option on the network switches.

Resolution 2

Set this registry entry to a value that is safely beyond the time it takes to retrieve a working IP address:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Netlogon\Parameters
Value Name: ExpectedDialupDelay
Data Type: Reg_Dword
Data Value is in seconds (default = 0)
Data Range is between 0 and 600 seconds (10 minutes)

Also configure this setting (details in KB 244474):

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Lsa\ Kerberos\Parameters
MaxPacketSize to 1

Resolution 3

Acconrding to KB 239924, disable media sense for TCP/IP:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Tcpip\Parameters
Add the following registry value:
Value Name: DisableDHCPMediaSense
Data Type: REG_DWORD -Boolean
Value Data: 1 (False, True)
Default: 0 (False)

Resolution 4

There is a known problem with DHCP client code in Windows 7. A hotfix is going to be released using this KB article: http://support.microsoft.com/?kbid=2459530

(http://support.microsoft.com/?kbid=2459530)

Resolution 5

To resolve this issue, reduce the Netlogon negative cache period (the NegativeCachePeriod registry entry). When you do this, the Netlogon service does not behave as if the domain controllers are offline for 45 seconds. The event 5719 is still logged, but there is little negativ eside-effect from that. The setting enables domain controllers to connect earlier.

For more information, click the following article number to view the article in the Microsoft Knowledge Base:

819108

(http://support.microsoft.com/kb/819108/ )

Settings for minimizing periodic WAN traffic

Back to the top | Give Feedback

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.

In a netlogon.log, you may see entries similar to this:
08/24 07:47:03 [CRITICAL] <domain>: NlDiscoverDc: Cannot find DC.
08/24 07:47:03 [CRITICAL] <domain>: NlSessionSetup: Session setup: cannot pick trusted DC
08/24 07:47:03 [MISC] Eventlog: 5719 (1) "<domain>" 0xc000005e ...
08/24 07:47:03 [SESSION] WPNG: NlSetStatusClientSession: Set connection status to c000005e
...
08/24 07:47:19 [SESSION] \Device\NetBT_Tcpip_{4A47AF53-40D3-4F92-ACDF-9B5E82A50E32}: Transport Added (10.0.64.232)
-> Getting a proper IP address takes >15 seconds.

Similar errors can be reported by the Group Policy Engine and as an effect the Group Policy is not applied at system boot, and startup scripts do not run for example. The Group Policy failures may be related to the problems of Netlogon locating a Domain Controller. There are settings to make Group Policy more resilient to late network connectivity arrival. Please see:

2421599 Windows 7 Clients intermittently fail to apply group policy at startup
http://support.microsoft.com/default.aspx?scid=kb;EN-US;2421599

(http://support.microsoft.com/default.aspx?scid=kb;EN-US;2421599)

Back to the top | Give Feedback