Hello, I am getting Event Id 5719, source is NETLOGON. I have tried many different things such as removing and re-adding the computer account. I have also looked online with no success. Any assistance would be much appreciated. I am on Windows 7 PRo. See below for more info: This computer was not able to set up a secure session with a domain controller in domain Domain due to the following: There are currently no logon servers available to service the logon request. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. - System - Provider [ Name] NETLOGON - EventID 5719 [ Qualifiers] 0 Level 2 Task 0 Keywords 0x80000000000000 - TimeCreated [ SystemTime] 2010-10-13T22:43:37.000000000Z EventRecordID 42503 Channel System Security - EventData T %%1311 5E0000C0 Binary data: In Words 0000: C000005E In Bytes 0000: 5E 00 00 C0 ^..À

This event can be found on a lot of Windows 7 clients, but are you really experiencing a problem and what is the actual problem?Blogging about Windows for IT pros at www.theexperienceblog.com

Hi, Thanks for posting in Microsoft TechNet forums. 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. Best Regards Magon Liu TechNet Subscriber Support in forum. If you have any feedback on our support, please contact tngfb@microsoft.com Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Hi, Thanks for posting in Microsoft TechNet forums. As this thread has been quiet for a while, we assume that the issue has been resolved. At this time, we will mark it as ‘Answered’ as the previous steps should be helpful for many similar scenarios. If the issue still persists, please feel free to reply this post directly so we will be notified to follow it up. You can also choose to unmark the answer as you wish. BTW, we’d love to hear your feedback about the solution. By sharing your experience you can help other community members facing similar problems. Thanks for your understanding and efforts. Best Regards Magon Liu TechNet Subscriber Support in forum. If you have any feedback on our support, please contact tngfb@microsoft.com Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Have you changed the password recently? Also check if your Win7 time is sync with it's logon DC. Leon Liu - Technical Lead

I'm also having the exact problem. Only happens with my Win7 PCs. We have Win2003 DC environment. In my case, the NIC device driver reported started with link status 100Mbs full duplex. About seven seconds later, get the Netlogon error. Though we are able to logon to the domain, the error is accross the board on all PCs. We are also getting User Profile Service delays of up to two minutes at log on. Any suggestions?

Bennun I have the same issue. A network connection is established 12 seconds before I see the netlogon event. I am running W7 SP1 with a W2k3 domain. Does anyone have an answer to this? we didnt see it on XP

Bennun I have the same issue. A network connection is established 12 seconds before I see the netlogon event. I am running W7 SP1 with a W2k3 domain. Does anyone have an answer to this? we didnt see it on XP I too have this issue and have not been able to resolve it.

On Experts Exchange, I found a related thread. Here's the relevant part: I found that the Gigabite Broadcom adaptors did not like the "Media sensing" feuture from microsoft. Added a registry key to \hklm\system\currentcontrolset\services\tcpip\parameters - added a "DWORD" DisableDHCPMediaSense = 1. This made all my issues go away. I had the same error, and this registry entry seemed to solve it.