Laptops running windows 7 are receiving a NetLogon 5719 error when connecting wirelessly and do not apply group policies. I've added a dialupdelay, tried group policy for waiting on network. I had this problem initially on all windows 7 machines in subnets where iphelper was used and windows firewall was blocking to the DHCP request response from the DHCP server, but have resolved this, now just have the issue of netlogon failing before DHCP Client completes. Any help would be awesome! Paul Beadles

Hi, Does this issue occur while connected by LAN? Based on my experience, server factors can cause Windows 7 machines experiencing Netlogon 5719 error. Before going further, here I would like to share some KBs related to Netlogon 5719: A “Netlogon event ID 5719” event message is logged when you start a Windows based computer A client connected to an Ethernet switch may receive several logon-related error messages during startup Best Regards Dale 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.

Issue is not occurring when connected to LAN via network cable, just when connecting wirelessly. Digging around system logs on a boot It looks like this Error 9:56:52AM NETLOGON 5719 Error 9:56:53AM GroupPolicy 1055 Information 9:56:57AM Dhcp-Client 50058 (Network is now ready for communication)

Error 1055 indicates Group Policy failure because of computer name resolution fail. I am assuming that the wireless touter in your cooperate isn't compatible with Windows 7. Please update the firmware of the wireless router and see if the problem goes away. Reference: Event ID 1055 — Group Policy Preprocessing (Security) Best Regards Dale 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.

Hello all, I was wondering whether this problem was ever resolved? I am experienceing the same issue with NETLOGON errors specific to my wireless clients. I had been though much the same problems with my wired clients as described above with the now well-documented problems surrounding IP Helpers and Win 7, but after fixing that and finding the fixes don't work for my wireless clients, I've discovered I have a different issue with wireless Win 7 machines. These machines can be on the same subnet as the DC's and can even have static IP's and I still see NETLOGON 5719 errors every time the machine boots. I've tried different brand AP's and even machines in a different, and completely independent AD forest, but they still produce NETLOGON 5719 errors at boot. I've tried just about everything for this problem, and it looks a lot like a Win 7 bug/incompatibility from what I can see (Win XP clients don't have this problem). Can anyone suggest a solution, or course of action? Thanks.

I've recently come across a new laptop doing exactly the same, it was first reported to me as the logon phase more often than not takes over 5 minutes to get to the desktop. The only events of concern ar those as mentioned above with Netlogon 5719 unable to find the DC. as well as GPO errors. I have also tried a multitude of possible causes and fixes. This seems to be occuring on 1 client machine and over 200 other machines of similar spec are unaffected. Also looking for some help on this. Regards Matt