none
Windows 7 x64 and x32 Netlogon 5719 errors

    Question

  • Ok, let me first start off by saying that this only happens on Windows 7 (x64 or x86).  I do not have this problem with XP (x64 or x86).

    I have several subnets for which I use the HP Procurve IP HELPER-ADDRESS.  This also happens if the DHCP server is a physical or virtual machine.  I was reading about the port fast option for RSTP (HP), though I can see if I need to use that if it happens with XP and Windows 7.  I tried the following:

    • Disabled IPv6
    • Tried a physical and virtual machine
    • Ran hotfix 2459530 for both x64 and x32
    • Tried the Broadcast registry fix instead of using unicast 
    • Tried updating NIC drivers for both Intel and Broadcom
    • Changed the gateway for the DHCP options
    • Have GPO for "always wait for network before logon"
    • Have GPO for "Startup policy wait time (120 seconds)"

    I still run into the issue that some Windows 7 machines will get the Netlogon 5719 errors on startup.  I don't know where to go to next about this issue??  I'm hoping SP2 will help with this issue.

    Friday, February 24, 2012 7:26 PM

Answers

  • smKKe wrote:

    Ok, let me first start off by saying that this only happens on
    Windows 7 (x64 or x86).  I do not have this problem with XP (x64 or
    x86).

    I have several subnets for which I use the HP Procurve IP
    HELPER-ADDRESS.  This also happens if the DHCP server is a physical
    or virtual machine.  I was reading about the port fast option for
    RSTP (HP), though I can see if I need to use that if it happens with
    XP and Windows 7.  I tried the following:

    * Disabled IPv6
    * Tried a physical and virtual machine
    * Ran hotfix 2459530 for both x64 and x32
    * Tried the Broadcast registry fix instead of using unicast 
    * Tried updating NIC drivers for both Intel and Broadcom
    * Changed the gateway for the DHCP options
    * Have GPO for "always wait for network before logon"
    * Have GPO for "Startup policy wait time (120 seconds)"

    I still run into the issue that some Windows 7 machines will get the
    Netlogon 5719 errors on startup.  I don't know where to go to next
    about this issue??  I'm hoping SP2 will help with this issue.

    Is this the only error message or do you have other connectivity
    errors, too - like no valid IP-address from dhcp-server, or no dns-name
    resolution working?

    If this is the only error you get and you are able to logon correctly
    and access the domain controller it is only cosmetic and means, that
    netlogon was already trying to access the resource before it was
    available - but it did sucessfully connect later, when the resouce was
    available. If you have other errors as well - please tell us those, too
    - to make troubleshooting easier.


    Wolfgang
    • Marked as answer by smKKe Wednesday, February 29, 2012 8:54 PM
    Friday, February 24, 2012 9:01 PM

All replies

  • smKKe wrote:

    Ok, let me first start off by saying that this only happens on
    Windows 7 (x64 or x86).  I do not have this problem with XP (x64 or
    x86).

    I have several subnets for which I use the HP Procurve IP
    HELPER-ADDRESS.  This also happens if the DHCP server is a physical
    or virtual machine.  I was reading about the port fast option for
    RSTP (HP), though I can see if I need to use that if it happens with
    XP and Windows 7.  I tried the following:

    * Disabled IPv6
    * Tried a physical and virtual machine
    * Ran hotfix 2459530 for both x64 and x32
    * Tried the Broadcast registry fix instead of using unicast 
    * Tried updating NIC drivers for both Intel and Broadcom
    * Changed the gateway for the DHCP options
    * Have GPO for "always wait for network before logon"
    * Have GPO for "Startup policy wait time (120 seconds)"

    I still run into the issue that some Windows 7 machines will get the
    Netlogon 5719 errors on startup.  I don't know where to go to next
    about this issue??  I'm hoping SP2 will help with this issue.

    Is this the only error message or do you have other connectivity
    errors, too - like no valid IP-address from dhcp-server, or no dns-name
    resolution working?

    If this is the only error you get and you are able to logon correctly
    and access the domain controller it is only cosmetic and means, that
    netlogon was already trying to access the resource before it was
    available - but it did sucessfully connect later, when the resouce was
    available. If you have other errors as well - please tell us those, too
    - to make troubleshooting easier.


    Wolfgang
    • Marked as answer by smKKe Wednesday, February 29, 2012 8:54 PM
    Friday, February 24, 2012 9:01 PM
  • From what I can see with all the machines I tested, that is the only error.  I have a mapped printer GPO via the print server and my question is if a computer does get the printer on startup, but later goes to sleep, the computer will lose the mapped printer.  Anyway I can make the GPO refresh on the computer after it comes back from sleep?  Or should I just setup a GPO to make sure noone can make the computer go to sleep?  I have the power options for Windows 7 as high performance since they are all desktops.

    Saturday, February 25, 2012 1:26 AM
  • smKKe wrote:

    From what I can see with all the machines I tested, that is the only
    error.  I have a mapped printer GPO via the print server and my
    question is if a computer does get the printer on startup, but later
    goes to sleep, the computer will lose the mapped printer.  Anyway I
    can make the GPO refresh on the computer after it comes back from
    sleep?  Or should I just setup a GPO to make sure noone can make the
    computer go to sleep?  I have the power options for Windows 7 as high
    performance since they are all desktops.

    Personally I prefer the disabling of sleeping in a LAN Desktop PCs
    environment. There are several things, which may break, if the
    connection goes into sleep mode. But if you want or need to be "green"
    (because of Company policy or personal belief) you have to go the other
    way and apply all necessary workarounds to get things going. Normally
    Windows 7 will recover without any special workarounds - its only a
    matter of time (unfortuntely we do not speak of seconds here but of
    several minutes in worst cases up to one hour) so these things have to
    be valued individually and thoroughly. As in business situations the
    time the employee needs to perform a task is the most expensive cost
    factor, this time is often much more expensive, than saved energy -
    even if its only 1 minute after resuming from sleep.


    Wolfgang
    Monday, February 27, 2012 11:34 AM
  • Hi,

    I would like to share the following articles for you.

    A "Netlogon event ID 5719" event message is logged when you start a Windows based computer
    http://support.microsoft.com/kb/247922

    Netlogon 5719 and the Disappearing Domain [Controller]
    http://blogs.technet.com/b/instan/archive/2008/09/18/netlogon-5719-and-the-disappearing-domain.aspx


    Niki Han

    TechNet Community Support

    Tuesday, February 28, 2012 7:47 AM
    Moderator
  • Thanks -- I tried before:

    A "Netlogon event ID 5719" event message is logged when you start a Windows based computer
    http://support.microsoft.com/kb/247922

    I enabled RSTP on my HP Procurve and that didn't seem to help as well.  This is happening only on seperate VLANs and only on the end user PC.

    Wednesday, February 29, 2012 8:54 PM
  • Ok, let me first start off by saying that this only happens on Windows 7 (x64 or x86).  I do not have this problem with XP (x64 or x86).

    I have several subnets for which I use the HP Procurve IP HELPER-ADDRESS.  This also happens if the DHCP server is a physical or virtual machine.  I was reading about the port fast option for RSTP (HP), though I can see if I need to use that if it happens with XP and Windows 7.  I tried the following:

    • Disabled IPv6
    • Tried a physical and virtual machine
    • Ran hotfix 2459530 for both x64 and x32
    • Tried the Broadcast registry fix instead of using unicast 
    • Tried updating NIC drivers for both Intel and Broadcom
    • Changed the gateway for the DHCP options
    • Have GPO for "always wait for network before logon"
    • Have GPO for "Startup policy wait time (120 seconds)"

    I still run into the issue that some Windows 7 machines will get the Netlogon 5719 errors on startup.  I don't know where to go to next about this issue??  I'm hoping SP2 will help with this issue.

    Hi,

    I'm on the same boat with You. Almost all my Win 7 SP1 x86 PC's shows this error and I have tried same things as You and probably more :)
    Nothing.

    I'v also read, that if this is the only error and nothing else, then I should leave it behind. I don't think that this is the right way from MS to solve event log RED errors like this.


    rgds Sven

    Friday, March 09, 2012 12:39 PM