1 2 Previous Next 24 Replies Latest reply on Jun 2, 2014 1:25 AM by TodorIotov Go to original post
      • 15. Re: Windows NETLOGON 5719 at Startup
        goppi Enthusiast

        Same problem here with Win2008R2 SP1 on VSpe 5.1 and no solution so far.

        • 16. Re: Windows NETLOGON 5719 at Startup
          PPH01 Lurker

          Same issue here with Windows 2008 R2 SP1 on ESXi 5.1.  Underlying storage didn't seem to matter any as I tested using the local disks (SAS) and the SAN (Nimble array).  Both presented the issue.  Tried with VM tools installed and without with same issue.

           

          Works fine with DHCP and breaks with Static IP address.

          Tried a number of different MS fixes, none made any difference.

          http://support.microsoft.com/kb/938449 - none of the options fixed issue.

          STP is off on our HP Procurve switches.

           

          We're also running XenServer 5.6SP2 (migrating off XenServer to VMWare), no issue in our XenServer environment or on our physical machines which points to VMWare.  Both XenServer and VMWare are running on the same Procurve switches.  All VM traffic is on dedicated ports (not shared with management traffic).

           

           

          Found that using DHCP Reservations was a workaround, doesn't help for DC's though.

           

           

          How are others getting around this issue on DC's?

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

            Try this

             

            1. Click Start, type regedit in the Start Search box, and then press ENTER.

            2. Locate the following registry key:

            HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters

            3. On the Edit menu, point to New, and then click DWORD Value.

            4. Type ArpRetryCount 

            5. Right-click the ArpRetryCount registry entry, and then click Modify 

            6. In the Value data box, type 0 and then click OK.

            7. Exit Registry Editor.

            8. Restart the machine.

            • 18. Re: Windows NETLOGON 5719 at Startup
              PPH01 Lurker

              Worked great on two servers now (to include a new Exchange 2010 box)!  Thank you!

               

              I'm not sure I fully understand what this does.

              http://technet.microsoft.com/en-us/library/cc957526.aspx

              http://social.technet.microsoft.com/Forums/en-US/windowsserver2008r2networking/thread/d7bda315-6366-4e0a-bdcf-dc875ff6963e/

              As discussed over phone earlier , for conflict detection, the client computer uses the Address Resolution Protocol (ARP) request to determine whether the IP address is being used. However, a ProxyArp device might incorrectly answer the ARP request, and an IP address conflict is reported.

              When this problem occurs, the ProxyArp device responds to all ARP requests.
              To work around this problem, we can turn off gratuitous ARP by setting the value of the ARPRetryCount registry entry to 0. To do this, follow these steps.

               

               

               

              Is this indicating a deeper issue in our network possibly?

              The DC's all appear fine (DCDiag, etc), none of the systems outside of VMWare seem to be having issues.

               

              Thanks again!

              • 19. Re: Windows NETLOGON 5719 at Startup
                goppi Enthusiast

                 

                Is this indicating a deeper issue in our network possibly?

                The DC's all appear fine (DCDiag, etc), none of the systems outside of VMWare seem to be having issues.

                 

                Thanks again!

                 

                From the description what the setting does indeed it is an indication of a general network issue.

                It seems that a network device in your netwok is sending incorrect ARP packets.

                The feature you turned of is to prevent having duplicate IP addresses in your network.

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

                  It has to do with the Duplicate Address Detection done by windows. In the data, it appeared that Netlogon was trying to initiate communication before the Duplicate Address Detection process, which sends three ARP Requests and waits for responses for the IP address the server has been assigned, had finished. By changing the Arp retry count it allowed the detection to occur faster before the netlogon would try to start.

                   

                  Trust me it took a while to figure it out and I worked on this with Microsoft and their OS developers to find it.

                  • 21. Re: Windows NETLOGON 5719 at Startup
                    PPH01 Lurker

                    This makes perfect sense now. Thanks you!

                     

                    I believe this indicates a flaw in Microsoft products boot order in my case (although, it could indicate an issue with ARP from a network device depending on the scenario).

                     

                    • netlogon service is not forced to wait for the network to fully initialize.
                    • The network will wait for the Duplicate Address Detection to complete before it initializes.

                     

                    Therefore it is possible for systems that boot too quickly to start the netlogon service prior to the Duplicate Address Detection to complete (thus network hasn't initialized).

                     

                    So, this entry tells the server not to check for duplicate addresses therefore the network initializes faster and is able to complete before the netlogon service starts.

                     

                    I believe this doesn't show on our XenServer or physical environment because of the speed difference.  Our VMWare environment is MUCH faster (18 seconds to fully boot Server 2012, SAN is under very little load currently), compared to our XenServer enrivonment which takes ~95 seconds.

                     

                     

                    A huge help ANorton! Thanks,

                    • 22. Re: Windows NETLOGON 5719 at Startup
                      de2rfg Enthusiast

                      ANorton wrote:

                       

                      Try this

                       

                      1. Click Start, type regedit in the Start Search box, and then press ENTER.

                      2. Locate the following registry key:

                      HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters

                      3. On the Edit menu, point to New, and then click DWORD Value.

                      4. Type ArpRetryCount

                      5. Right-click the ArpRetryCount registry entry, and then click Modify

                      6. In the Value data box, type 0 and then click OK.

                      7. Exit Registry Editor.

                      8. Restart the machine.

                       

                      Thank you! You saved me a lot of time.

                       

                      I had the same symptoms in our new VMware 5.1 U1 Cluster with fresh hardware. New VMs, P2V'ed and old VMs that were moved into the Cluster showed Netlogon/Group Policy/NTP... errors. With VMware limits on CPU/MEM/Disk the errors went away, it clearly looked like a timing issue.

                       

                      The netlogon debug log showed that the system was missing the IP address (we use static ip settings)

                       

                      07/25 14:43:59 [SESSION] Winsock Addrs: (0) List is now empty.

                       

                      With DHCP everything was working without problems.

                       

                      The ArpRetryCount=0 setting works perfect for me. But I still think it's a workaround, is there any official MS article that describes the problem (timing) and a official solution?

                      • 23. Re: Windows NETLOGON 5719 at Startup
                        de2rfg Enthusiast

                        We received an answer from MS about the problem and the ArpRetryCount regkey. They know the problem and there is no offical solution. They also advised us to not change  the ARP parameter because of the negative effects this could have. So we are back to 0...

                        • 24. Re: Windows NETLOGON 5719 at Startup
                          TodorIotov Lurker

                          Here is the closest thing to official fix for this issue - KB938449. I've tested the ExpectedDialupDelay method, but did not worked out, which is unfortunate, since it looks like the best solution so far.

                          1 2 Previous Next