1 2 Previous Next 24 Replies Latest reply on Jun 2, 2014 1:25 AM by TodorIotov

    Windows NETLOGON 5719 at Startup

    lilwashu Lurker

      I am having what appears to be either a networking or guest startup issue with Windows 2008 R2 SP1 guest machines on my VSphere Essentials setup. Configuration is:


      HP BL460C G7 servers, 72GB RAM, with built in Emulex dual port 10Gb NICs and mezzanine NC632M dual port NICs (total 4 per host).

      NICs connected to HP C3000 blade enclosure and GBe2C HP (Nortel) interconnect switches which are then uplinked to HP 5304 modular switch

      ESXi 4.1 Update 1 with Emulex driver update


      The issue I am seeing is that when Windows 2008 R2 boots (this can be on a new install or a P2Ved install) it throws a NETLOGON 5719 (unable to establish a secure connection) error in the event log followed closely by a windows time lookup failure warning. I can log in OK and the errors do not reoccur, Group Policy applies OK and the time service syncs a couple of seconds after the initial warning.


      This only happens if the NIC is set to a static IP address. If I set it to DHCP (same address details as the static one), I do not get any errors at all.


      What appears to be happening is that NETLOGON is starting before the network has completely initialised. I have tried making it depend on another service etc, disabled portfast/STP on the switches and have seen no change. I have also read an MS article which says it can be ignored, however I don't like random errors and I have not seen this before in similar deployments with similar hardware. We don't have any issues on physical servers running the same OS, even if they are in the same blade enclosure, or on Windows 2003 VMs.


      Has anyone else noticed this behaviour?

        • 1. Re: Windows NETLOGON 5719 at Startup
          vmroyale Guru
          User Moderators

          Hello and welcome to the forums.


          Note: This discussion was moved from the VMware ESXi 4 community to the Virtual Machine & Guest OS community.


          Do you have the VMware Tools installed in these guests, and what NIC are you using in them?


          Good Luck!

          • 2. Re: Windows NETLOGON 5719 at Startup
            lilwashu Lurker

            I do have VMWare tools installed and have tried the E1000 and VMXNET3 adapters without any change in behaviour.

            • 3. Re: Windows NETLOGON 5719 at Startup
              vMikee386 Novice

              Has there been any movement on this?  I am seeing a similar issue with W2K8-R2.



              • 4. Re: Windows NETLOGON 5719 at Startup
                jrkennemer Lurker

                Any movement?  We're seeing the same thing on our new environment (Cisco UCS and EMC VNX) and after a couple of weeks working with VMware, Cisco, Microsoft and our integrator, we're being told our system is "too fast".  Essentially since we're in test mode and only have a few VMs running on the environment, there's not enough load and Windows boots too quickly.  This causes our Exchange services to fail, which is impeding progress on our pilot.


                Has anyone else run in to this situation?

                • 5. Re: Windows NETLOGON 5719 at Startup
                  lilwashu Lurker

                  No progress yet and VMWare support have been worse than useless so far. I will be calling them tomorrow to register a complaint about this particular aspect.


                  In the meantime we have set Exchange services to delayed start which has worked around it so far.


                  If anyone wants my case reference to give to VMWare support PM me and hopefully we will get somewhere.

                  • 6. Re: Windows NETLOGON 5719 at Startup
                    mila30 Enthusiast

                    Hi, hope everything works fine with you now.  I would like to know your developments.  Because your case once solve will benefit us in a way that we will know what to do if it will happen to us too.  I am looking forward to read updates on your status http://imagicon.info/cat/5-59/1.gif

                    • 7. Re: Windows NETLOGON 5719 at Startup
                      cdsmm Lurker

                      We are having the exact same symptoms: NETLOGON 5719 and some time-service errors on boot.

                      The one different thing is we are running this on physicals. But only on new dual 6 core servers, our older servers don't have these issues. We are running 2008 R2 Enterprise SP1. Becuase we have physicals this problem only manifests itself when we have LACP enabled. We have dozens and dozens of other servers with the same setup (2008 R2, cisco switches) but a couple years old in terms of hardware and they don't have the problems.


                      We've followed all other suggestions found on the internet but nothing has worked. We've also been trying to have the netlogon service depend on other services, and delay start, etc. But nothing has helped.


                      The impact for us and these NETLOGON errors is that some of our computer GPO's are not being consistently applied. So we cannot ignore these errors.


                      I have found some forum posts on an HP and a separate IBM site (we have Dell servers) and everyone seems to be having the exact same issue:




                      We've opened a call with Dell, and I will be opening a call with MS here shortly, but based on what I am seeing, the NETLOGON service seems to be starting so fast that the network connections aren't fully available yet.

                      • 8. Re: Windows NETLOGON 5719 at Startup
                        vMikee386 Novice

                        I truly believe that this is something MS needs to address.  They “own” the services in question and I cannot understand why they would attempt to use one before it has started.

                        • 9. Re: Windows NETLOGON 5719 at Startup
                          lilwashu Lurker

                          The problem does not seem to be trying to use a service before it has started, rather that the service starts before the network hardware has initialised fully, which would put the problem in the hardware vendor's court as far as I can see.

                          • 10. Re: Windows NETLOGON 5719 at Startup
                            vMikee386 Novice

                            Unless it is a MS (or MS certified) driver.  The driver should tell the system when the HW is ready for use.  The service should wait until the driver gives the OK.  If the driver does not start within an allotted time, then there should be a hard error.

                            • 11. Re: Windows NETLOGON 5719 at Startup
                              ANorton Enthusiast

                              Has there been any update on this anywhere? We are having the same issue.

                              • 12. Re: Windows NETLOGON 5719 at Startup
                                vMikee386 Novice

                                No change that I am aware of. I installed the UCS and VNX data center named above and the issue went away once we placed a workload on the system.  Sounds a bit silly, but place a workload (even if it is synthetic via something like IOmeter) and see if your issue persists.

                                • 13. Re: Windows NETLOGON 5719 at Startup
                                  lilwashu Lurker

                                  We never got around the problem, and also don't see the problem on "slower" storage such as NFS/ISCSI. VMware blamed Microsoft and Microsoft blamed VMware.


                                  Interestingly we don't see the problem with HyperV/Xenserver hypervisors on the same platform.

                                  • 14. Re: Windows NETLOGON 5719 at Startup
                                    DuncanClay Lurker

                                    Same problem, Windows Server 2008 R2 SP1 Standard, vCenter 4.1.0, VMware tools 8.3.2, VMXNET 3 adapter, DHCP.  Spent the best part of a day trying various Microsoft KB solutions.


                                    Our problem is that SQL Server 2008 R2 was following the NETLOGON Event ID 5719 with an Event ID 7000 (The SQL Server (MSSQLSERVER) service failed to start due to the following error: The service did not start due to a logon failure.) and 7038 (The MSSQLSERVER service was unable to log on as domain\user with the currently configured password due to the following error: There are currently no logon servers available to service the logon request.).

                                    Whilst I have not been able to stop the 5719 error, setting the startup type of MSSQLSERVER to Automatic (Delayed Start) at least means SQL Server is starting automatically after a reboot.  I consider this a workaround at best, but if you have automatic services that are failing, it might be worth a try.

                                    1 2 Previous Next