locked
Event ID:5719 - Netlogon - Server 2003 R2 RRS feed

  • Question

  • The following message came up on our server and I have been searching for an answer.

    Event Type:    Error
    Event Source:    NETLOGON
    Event Category:    None
    Event ID:    5719
    Date:        9/27/2010
    Time:        7:27:29 AM
    User:        N/A
    Computer:    WLFS01
    Description:
    This computer was not able to set up a secure session with a domain controller in domain UNISEMGROUP 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. 

    ADDITIONAL INFO
    If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
    Data:
    0000: 17 00 00 c0               ...À   

     

    When this happens all of our printers stop and there is no memory to open Task manager

    Has anyone else had this problem. It has only just started to be an issue.

    Wednesday, September 29, 2010 1:50 PM

Answers

  • Hi,

     

    Please refer to the following KB article and change the logon cache number to 0:

     

    Cached domain logon information

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

     

    If the solution above doesn’t help your case, please make the TCP to close ports that have been inactive for 30 seconds by changing the following key:

     

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters

     

    "TcpTimedWaitDelay": dword: 0000001e

    "MaxUserPort": dword: 0000fffe

     

    If the issue persists, please also refer to the following link to check if it can fix the issue for you:

     

    http://www.eventid.net/display.asp?eventid=5719&eventno=104&source=NETLOGON&phase=1

     

    Note: Since the web site is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.

     

    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.
    Thursday, September 30, 2010 3:13 AM
  • Hi

    I have changed

    HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\Current Version\Winlogon\
    To O

    was unable to chnage  - HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters

     

    "TcpTimedWaitDelay": dword: 0000001e

    "MaxUserPort": dword: 0000fffe

    This was not present in the  registry

     

    You have to add them to the registry, that is why Arthur put "Dword" there for you. So you could enter the registry values properly.

    Not all registry keys are entered. Some are left blank and added for instance, some GPO settings do not have any entries in a fresh install system that are listed in the registry but are added when they are enabled or disabled with 0, 1, or the value of the listed variable for certain policies.


    Steve Kline
    Microsoft Certified IT Professional: Server Administrator
    Microsoft Certified Product Specialist
    Microsoft Certified Network Product Specialist
    This posting is "as is" without warranties and confers no rights.
    Thursday, September 30, 2010 6:07 PM

All replies

  • Hi,

     

    Please refer to the following KB article and change the logon cache number to 0:

     

    Cached domain logon information

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

     

    If the solution above doesn’t help your case, please make the TCP to close ports that have been inactive for 30 seconds by changing the following key:

     

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters

     

    "TcpTimedWaitDelay": dword: 0000001e

    "MaxUserPort": dword: 0000fffe

     

    If the issue persists, please also refer to the following link to check if it can fix the issue for you:

     

    http://www.eventid.net/display.asp?eventid=5719&eventno=104&source=NETLOGON&phase=1

     

    Note: Since the web site is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.

     

    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.
    Thursday, September 30, 2010 3:13 AM
  • Hi

    I have changed

    HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\Current Version\Winlogon\
    To O

    was unable to chnage  - HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters

     

    "TcpTimedWaitDelay": dword: 0000001e

    "MaxUserPort": dword: 0000fffe

    This was not present in the  registry

     


    Thursday, September 30, 2010 2:54 PM
  • Hi

    I have changed

    HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\Current Version\Winlogon\
    To O

    was unable to chnage  - HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters

     

    "TcpTimedWaitDelay": dword: 0000001e

    "MaxUserPort": dword: 0000fffe

    This was not present in the  registry

     

    You have to add them to the registry, that is why Arthur put "Dword" there for you. So you could enter the registry values properly.

    Not all registry keys are entered. Some are left blank and added for instance, some GPO settings do not have any entries in a fresh install system that are listed in the registry but are added when they are enabled or disabled with 0, 1, or the value of the listed variable for certain policies.


    Steve Kline
    Microsoft Certified IT Professional: Server Administrator
    Microsoft Certified Product Specialist
    Microsoft Certified Network Product Specialist
    This posting is "as is" without warranties and confers no rights.
    Thursday, September 30, 2010 6:07 PM
  • Hi,

     

    I would like to confirm that have you tried all the above troubleshooting suggestions and what is the current situation?

     

    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.
    Tuesday, October 5, 2010 1:59 AM