Windows 2008 event id 5719 netlogon

You can follow these steps:. If the ntte value is not converted in the UI to a readable date and timestamp, run the following command or proceed to step 9 for an alternate method:. Click Start , point to Programs , point to Accessories , and then click Calculator. To change the value from decimal to hexadecimal decimal numbering system, click Hex. If the hexadecimal string on the left side contains only seven characters, add a zero to the beginning of the string.

Check whether the date and time that you noted in step 1 and the decoded date and time that you noted in step 20 match. If the date and time that event was logged and the decoded date and time match, check whether the computer that is causing the problem has a secure channel established with a domain controller by typing the following command at a command prompt:.

If the problem computer has a valid secure channel established with a domain controller, you receive output that is similar to:. If the problem computer does not have a valid secure channel established with a domain controller, you receive output that is similar to:. If the date and time of event and the decoded date and time do not match, the problem computer's account password may not match the password that is on the domain controller.

This issue can occur under either of the following circumstances:. If Netlogon service logging is turned on for the domain controller, you confirm this scenario by checking for a Netlogon. This applies to scenarios where a NAP solution puts the machine into a quarantine network. Use the following settings as guidelines.

For more information, see Settings for minimizing periodic WAN traffic. It delays the time that the IP takes to come online. You can set the ArpRetryCount registry entry to one 1 , so the wait for uniqueness is shortened.

To do it, follow these steps:. Right-click the ArpRetryCount registry entry, and then select Modify. After you make this change, the Netlogon service doesn't behave as if the domain controllers are offline for 45 seconds. The event is still logged. However, the event doesn't cause any other significant problems. This setting allows member to try domain controllers earlier if the process failed previously. Suggestion: Try to set a low value, such as three seconds.

In LAN environments, you can use a value of 0 to turn off the negative cache. For more information about this setting, see Settings for minimizing periodic WAN traffic.

Configure the Kerberos registry setting to a value that is safely beyond the time that is required allow DC connectivity. This setting applies only to Windows XP and Windows Server or earlier versions of these systems. Windows Vista and Windows Server and later versions use a default value of 0.

The time it takes Netlogon to acquire a working IP can be the basis for the setting. For Direct Access scenarios, you can measure the typical delay your user base has until the connection is established.

You can receive help directly from the article author. Sign up for a free trial to get started. Start Free Trial. Log In. Web Dev.

Netlogon Event ID Venkat Suresh Architect. Published: Note To enable Netlogon Debug Logging simply run the nltest. Or in this case, reboot the computer to generate the event.

This behavior can occur when your server is connected to a switch that has the spanning tree "portfast" setting disabled. To work around this behavior, enable the spanning tree "portfast" setting on the switch. For information about the proper use of the spanning tree "portfast" setting, consult the documentation provided with the switch.

For more information, click the following article number to view the article in the Microsoft Knowledge Base:. Need more help? Expand your skills.