Ihave a Windows 2003 R2 SP2 terminal server (member server, not a dc). They are both completely patched. The terminal server some third party applicationsandoffice 2003 installed. It supports about 10 users.The terminal server is a dellpoweredge with 2GB of ram. TheDC's areWindows 2003 and Windows 2008 inWindows 2003 DFL.The problem is that the terminal server will function just fine for a week or so and then suddenly when a new user tries to log on they get an error message indicating that not enough resources are available to log them on.When this happens I can get current stats from the serverconsole and the CPU and memory are both perfectly normal (1.4GB memory available, CPU is fairly steady around 8%). This error continues to occur for all new users until the tserver is rebooted.The following events show up when this happens:eventid 1053, UserenvWindows cannot determine the user or computer name. (Not enough storage is available to complete this operation. ). Group Policy processing aborted. eventid 1219, WinlogonLogon rejected for *username*. Unable to obtain Terminal Server User Configuration. Error: Not enough resources are available to complete this operation. eventid 2004, PerfNetUnable to open the Server service. Server performance data will not be returned. The error code returned is in the first DWORD in the Data section. Any ideas? Thank you.

Hello,is the server multihomed, 2 NICs with different ip addresses? An unedited ipconfig /all from the server and a client mahcine could be helpful.See here about 1219:http://www.eventid.net/display.asp?eventid=1219&eventno=2848&source=winlogon&phase=11053:http://www.eventid.net/display.asp?eventid=1053&eventno=1584&source=Userenv&phase=1Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties, and confers no rights.

The server has two NICS one if enable and set up with TCP/IP the other one has not TCP/IP settings on it and is disabled. I also have noticed that I get the following IDs:eventid 2004, PerfNetUnable to open the Server service. Server performance data will not be returned. The error code returned is in the first DWORD in the Data section.and sometimes under the system node:event id 5719, NETLOGONThis computer was not able to set up a secure session with a domain controller in domain NRC 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. 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.event ID40960 ,LSASRVThe Security System detected an authentication error for the server DNS/ The failure code from authentication protocol Kerberos was "There are currently no logon servers available to service the logon request.(0xc000005e)".Event ID10009 ,DCOMDCOM was unable to communicate with the computer DC1.dnsdomain.loc using any of the configured protocols.When the server gets rebootedthe users canlogon finethenrandomlyyou can't logon anymore and you get a message saying that users denied logon because not enough resources are available.I hope that gives a little more of information. Thank you.

Hi, Please install the update 948496 or manually disable RSS and TCP Offload on the Terminal server and check if the issue goes away: An update to turn off default SNP features is available for Windows Server 2003-based and Small Business Server 2003-based computers http://support.microsoft.com//kb/948496 If the issue persists, I suggest that you post to the Terminal Services forum for further discussion: Terminal Services Forum http://social.technet.microsoft.com/Forums/en-US/winserverTS/threads

hi depaul, did you had a chance to follow joson's workaround ?sainath windows driver development.