none
Netlogon Error 5719 every boot - Windows 2008 R2 SP1 RRS feed

  • Question

  • HP DL360 G7 with clean install of Server 2008 R2 SP1 and latest patches.  Single NIC connected to 1GB Access switch port (which has also been connected via a hub for troubleshooting, to no avail.)  HP software / Firmware all up to date and system board replaced by HP for good measure.

    Every boot, 'Netlogon error 5719 cannot contact domain' is reported in system log, and then a few seconds later, the NIC initializes.  No matter what service we make 'Netlogon' dependant upon, Netlogon always seems to error beforehand.  I have replicated the operating system and patch levels on a virtual machine and we do not see the issue, only on this physical piece of tin (hence HP changing the system board and integrated NICs).

    Other steps taken:

    - NIC speed / duplex fixed or Auto, makes no difference.

    - LMHosts lookup disabled & NetBIOS over TCP enabled / disabled

    - moved NIC to top in binding order

     

    Has anybody else experienced this recently or is anyone aware of an easy fix?

    Advice welcomed!  Thank you.

    Thursday, July 28, 2011 10:18 PM

Answers

  • Hi,

     

    Please try the following troublehsooting suggestions:

     

    1.    Force Kerberos to use TCP instead of UDP.

     

    HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Lsa\ Kerberos\Parameters

    MaxPacketSize = 1

     

    How to force Kerberos to use TCP instead of UDP in Windows

     http://support.microsoft.com/default.aspx?scid=kb;EN-US;244474 

     

    2.    Make netlogon service to depend on network connections.

     

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Netlogon

    DependOnService = Netman

     

    3.    Disable the Spanning Tree Algorithm feature of your Ethernet switch.

     

    HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Netlogon\Parameters

    ExpectedDialupDelay = 180

     

    A client connected to an Ethernet switch may receive several logon-related error messages during startup

     http://support.microsoft.com/default.aspx?scid=kb;EN-US;202840 

     

    4.    Reboot the server and check the event log again.  

     

    Regards,


    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.
    Friday, July 29, 2011 2:15 AM
    Moderator

All replies

  • Hi,

     

    Please try the following troublehsooting suggestions:

     

    1.    Force Kerberos to use TCP instead of UDP.

     

    HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Lsa\ Kerberos\Parameters

    MaxPacketSize = 1

     

    How to force Kerberos to use TCP instead of UDP in Windows

     http://support.microsoft.com/default.aspx?scid=kb;EN-US;244474 

     

    2.    Make netlogon service to depend on network connections.

     

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Netlogon

    DependOnService = Netman

     

    3.    Disable the Spanning Tree Algorithm feature of your Ethernet switch.

     

    HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Netlogon\Parameters

    ExpectedDialupDelay = 180

     

    A client connected to an Ethernet switch may receive several logon-related error messages during startup

     http://support.microsoft.com/default.aspx?scid=kb;EN-US;202840 

     

    4.    Reboot the server and check the event log again.  

     

    Regards,


    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.
    Friday, July 29, 2011 2:15 AM
    Moderator
  • Why did you mark your response as an answer without confirmation from the user? This seems to be a recent trend with Microsoft staff monitoring the boards and it leads us to false conclusions that the suggestions did indeed resolve the issue.

    I too am exeperiencing this exact same issue on my HP DL380 G6 and DL360 G6 servers, and it impacting Exchange service startup. Specficially the Netlogon errors out as listed in the first post, and Exchange services which are set to Automatic don't start.

    I skipped your suggestion #1 as the servers are on the same network switch, not passing through a firewall, as the DCs so it shouldn't matter. I tried suggestion 2 and 3 with no relief.

    The issue seems to be directly tied to the fact that the Netlogon service is trying to start before the NICs have even initialtized. For example the last reboot of of the Exchange 2010 server shows the Netlogon service tring to start and failing at 6:16:21PM with the first NIC initalizaing (event source "L2nd") at 6:16:22PM. I can completely understand why the Netlogon service can't find any DCs if it is firing off before the NICs are all connected. Neither registry setting seems to change this behavior.

    Is there somethign else we can try?

    Tuesday, September 13, 2011 10:40 PM
  • Our Exchange DSE found this link which was recently updated which helped us provide a work around until we can find and eliminate the root cause of the Netlogon issues:

    http://support.microsoft.com/kb/2025528

    Our Exchange server AD Topolgy service and subsequent services are now starting properly even though we still get the Netlogon error. Perhaps this will work for other folks as well and their services since this is a Netlogon registry modification.

    Thursday, September 15, 2011 6:40 PM
  • I tried everything, after several days I found this http://support.microsoft.com/kb/239924/. And thats it. The answer is on the Broadcom FAQ page:

    A system containing an 802.3ad team causes a Netlogon service failure in the system event log and prevents it from communicating with the domain controller during boot up. How do I resolve this issue?

    Microsoft Knowledge Base Article 326152 (http://support.microsoft.com/kb/326152/) indicates that Gigabit Ethernet adapters may experience problems with connectivity to a domain controller due to link fluctuation while the driver initializes and negotiates link with the network infrastructure. The link negotiation is further affected when the Gigabit adapters are participating in an 802.3ad team due to the additional negotiation with a switch required for this team type. As suggested in the Knowledge Base Article above, disabling media sense as described in a separate Knowledge Base Article 239924 (http://support.microsoft.com/kb/239924/) has shown to be a valid workaround when this problem occurs.

    Monday, October 24, 2011 1:11 PM
  • Did you try this on your servers and verify it works? Also are you using 802.3ad teams?

    The teams on my HP servers are using "Network Fault Tolerance wiht Preference Order", not the "802.3ad Dynamic with Fault Tolerance", and we do hard set the ports to 1000/full both on the server and the switch ports.

    Thanks!

    Friday, October 28, 2011 8:52 PM
  • Hello, I had the same type of servers. 

    I had both servers with the clean instalation of system and on the second i had this problem. After every startup i got this error. I tried reinstall server but nothing chnage.

    Problem was in drivers. If i updated drivers on network card to the latest (version: 7.0.11.0, driver date: 29.9.2011), problem disappeared.

    Monday, June 18, 2012 10:16 AM
  • Hello guys,

    I had this issue on a Blade System C3000 with BL460 G1. With the new Driver (27.3.2012) the issue is gone.

    NOW I have 2 DL385 G6 Servers and have again this issue. HP sent me 2 new NIC´s (NC380T - Intel Based). Nothin g better still the issue.

    How did u fix this? I am workin on this since 1 WEEK, I tried everything incl. DisableDHCPmediasense. Nothing helps. With my DL380 G4 Servers is everything fine, also with my HP Z800 is everything ok.

    I have an unmanaged LevelOne switch. Everything connected to this. Everything works, only the DL385 G6 NOT.

    PLEASE HELP!

    Thanks

    Thursday, September 13, 2012 11:41 AM
  • I tried all the suggested ideas in this but none worked. To fix I installed the latest version of the HP Network Configuration Utility. Set up a team and this resolved it. The additional symptom I had was if I tried to create a team it created the new network connection but did not bind to it correctly.

    Wednesday, February 6, 2013 7:50 PM