none
Event 5719 Netlogon Problem

    Question

  •  

    Everyday this week, we have gotten this message in our event viewer and we are forced to restart the server to allow our web-based programs to work again

     

    Date:                       Source: NETLOGON

    Time:                       Category: None

    Type: Error               Event ID: 5719

     

    This computer was not able to set up a secure session with a domain controller in domain NTNET due to the following:

    Not enough storage is available to process this command.

    This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.

     

    I have a Windows 2003 Server that is not a Domain Controller and has plenty of resources still available when this happens and the internet connection is also still working because I can remotely log into it.

    Friday, February 15, 2008 5:41 PM

Answers

  • Hi,

     

    According to my research, event 5719 can be caused by many factors, such as network connectivity, non-paged memory leak occurs in Tcpip.sys, or out of buffer space in the NetBT datagram buffer etc. Based on the description of Event log, I suspect this may be caused by TCP/IP stack, so could you please try the following steps:

     

    1. Please increase the IRPStackSize by following the kB 285089:

    Description of the IRPStackSize parameter in Windows 2000, in Windows XP, and in Windows Server 2003

     

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

     

    2. Please configure the TCP to close the inactive connections in shorter period than the default behavior. To do this,

     

    (1). Logon to the problematic computer as an administrator.

     

    (2). Click Start ->Run-> regedit.exe and press Enter.

     

    (3). Navigate to the HKLM\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters.

     

    (4). Create the following two keys in under the Parameters key:

    Key name: TcpTimedWaitDelay
    Data type: REG_DWORD
    Value: 0000001e

    Key name: MaxUserPort
    Data type: REG_DWORD
    Value: 0000fffe

    For more information about the two keys, you may refer to:

    MaxUserPort

     

    http://technet2.microsoft.com/WindowsServer/en/library/730fb465-d402-4853-bacc-16ba
    78e9fcc01033.mspx?mfr=true

     

    TcpTimedWaitDelay
    http://technet2.microsoft.com/WindowsServer/f/?en/library/38b8bf76-b7d3-473c-84e8-e
    657c0c619d11033.mspx

     

    Please note these operations are related to modify registry. Make sure that you back up the registry before you modify it.

     

    I hope this helps.

     

    Best wishes

    --------------
    Morgan Che

    Microsoft Online Community Support

     

    Tuesday, February 19, 2008 9:35 AM
    Moderator

All replies

  • Where is your page file, how large is it and how much spare space is on the drive?

     

    Friday, February 15, 2008 7:57 PM
  • My page file is located at C:\\pagefile.sys and is 1.99 GB. The hard drive is partitioned into two drives. C: has 1.16 GB out of 10.0 GB free and D: has 521 GB out of 548 GB free.

     

    Friday, February 15, 2008 8:41 PM
  • Move the page file to your D:\ drive or free up a gig stuff on your C drive.

     

    Let me know if that helps,

     

     

     

    Friday, February 15, 2008 11:24 PM
  • Hi,

     

    According to my research, event 5719 can be caused by many factors, such as network connectivity, non-paged memory leak occurs in Tcpip.sys, or out of buffer space in the NetBT datagram buffer etc. Based on the description of Event log, I suspect this may be caused by TCP/IP stack, so could you please try the following steps:

     

    1. Please increase the IRPStackSize by following the kB 285089:

    Description of the IRPStackSize parameter in Windows 2000, in Windows XP, and in Windows Server 2003

     

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

     

    2. Please configure the TCP to close the inactive connections in shorter period than the default behavior. To do this,

     

    (1). Logon to the problematic computer as an administrator.

     

    (2). Click Start ->Run-> regedit.exe and press Enter.

     

    (3). Navigate to the HKLM\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters.

     

    (4). Create the following two keys in under the Parameters key:

    Key name: TcpTimedWaitDelay
    Data type: REG_DWORD
    Value: 0000001e

    Key name: MaxUserPort
    Data type: REG_DWORD
    Value: 0000fffe

    For more information about the two keys, you may refer to:

    MaxUserPort

     

    http://technet2.microsoft.com/WindowsServer/en/library/730fb465-d402-4853-bacc-16ba
    78e9fcc01033.mspx?mfr=true

     

    TcpTimedWaitDelay
    http://technet2.microsoft.com/WindowsServer/f/?en/library/38b8bf76-b7d3-473c-84e8-e
    657c0c619d11033.mspx

     

    Please note these operations are related to modify registry. Make sure that you back up the registry before you modify it.

     

    I hope this helps.

     

    Best wishes

    --------------
    Morgan Che

    Microsoft Online Community Support

     

    Tuesday, February 19, 2008 9:35 AM
    Moderator
  •  

    Moving the page file did not work for me so I will try what Morgan recommended and see if that fixes my problem.
    Wednesday, February 20, 2008 2:11 PM
  • I didn't have any problems until this morning. The web help desk we have running on this server went down but I did not have the netlogon errors in my event viewer. I had to stop and start the netlogon service to get it up again.  The web help desk is running on a SQL server and the help desk could not connect to the local database.

    Monday, February 25, 2008 3:43 PM
  • Hi,

    I have used this thread to create a new topic on the TechNet Wiki, Event ID 5719 source Netlogon (dsforum2wiki) at http://social.technet.microsoft.com/wiki/contents/articles/event-id-5719-source-netlogon-dsforum2wiki.aspx

    The Wiki is a great place to roll up answers for the community to improve an article (versus threads).  Take a look and share your feedback.

    Justin Hall, MSFT

    Tuesday, March 15, 2011 8:14 PM
  • Those 2 reg entries stopped the error on my Win2008 R2 SP1 server, but I'm concerned about them.  What do they do?  How will they affect my system?  The 2 links provided don't seem to work any longer.
    Tuesday, November 13, 2012 11:16 PM