To resolve this issue, use the registry to change the related settings that affect DC connectivity. Or, enable the PortFast option on the network switches.
To resolve this issue, install the most current driver for the Gigabit network adapter. Microsoft cannot guarantee that these problems can be solved. These problems might require that you reinstall the operating system. Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. This situation is especially true when the delay in finding a network alternates between startups. However, Group Policy may start prematurely because of a policy application. And it waits for a network that has DC connectivity. Group Policy in Windows Vista and later versions is written to negotiate the network status that has NLA enabled. It delays the display of the network interface.
Some network adapters and switches have link arbitration and MAC address uniqueness checks that take longer to complete than the wait time that is set for Netlogon to detect network connectivity. The network stack and adapter initialization often start at about the same time. The Netlogon service starts before the network is ready.This issue may occur for any of these reasons: The third section shows that the Group Policy engine starts a background procedure, and then waits for one minute after a network becomes available. The second section shows that Network Location Awareness (NLA) fails to report a working network within the wait interval that's allowed, and group policy startup processing fails. It can be based on previous fast startups. The first section shows the calculation for the time-out to use to bring up the network. GPSVC(530.8e0) ApplyGroupPolicy: Getting ready to create background thread GPOThread. NlaGetIntranetCapability returned Not Ready error. ProcessGPOs(Machine): MyGetUserName failed with 1355. NlaGetIntranetCapability failed with 0x15 NlaQueryNetSignatures returned 1 networks The following entries are recorded in the group policy debug log: CGPApplicationService::MachinePolicyStartedWaitingOnNetwork.ĬGPMachineStartupConnectivity::CalculateWaitTimeoutFromHistory: Average is 388.ĬGPMachineStartupConnectivity::CalculateWaitTimeoutFromHistory: Current is -1.ĬGPMachineStartupConnectivity::CalculateWaitTimeoutFromHistory: Taking min of 70.
On Windows 10 and later versions, you'll see only events by components, depending on the Domain Controller connectivity (such as Group Policy). Winsock Addrs: 10.1.1.80 (1) List used to be empty. No IP addresses present, skipping No DC event logĪfter this issue occurs, the computer is assigned an IP address: V6 Winsock Addrs: fe80::5faf:632a:f22c:644a%2 (1) V6WinsockPnpAddresses List used to be empty. The following lines are recorded in Netlogon.log instead: CONTOSO: NlSessionSetup: Session setup: cannot pick trusted DC In Windows 10 and later versions, event 5719 is no longer logged in this situation.
In this scenario, the following event is logged in the System log when you start the computer in Windows 8.1 and earlier versions. You secure the network access by using Network Access Protection (NAP), network authentication (by using 802.1 x), or another method.The computer has a Gigabit network adapter installed.You have a computer that's running Windows 10 or Windows Server 2012 R2.Before you modify it, back up the registry for restoration in case problems occur. Serious problems might occur if you modify the registry incorrectly.
Follow the steps in this section carefully.