I have a Windows 2003 R2 SP2 domain controller and a Windows 2003 R2 SP2 terminal server (member server, not a dc). They are both completely patched. The terminal server has ACT 2007 for workgroups, lotus notes and office 2003 installed. It supports about 10 users. Both servers are less than a year old, the dc is a dell poweredge 2800 and the terminal server is a dell precision with 2GB of ram.
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. Sorry, I didn't screenprint the exact message and I can't reproduce it. When this happens I can get current stats from the terminal server using Remotely Anywhere 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, Userenv
Windows cannot determine the user or computer name. (Not enough storage is available to complete this operation. ). Group Policy processing aborted.
eventid 1219, Winlogon
Logon rejected for *username*. Unable to obtain Terminal Server User Configuration. Error: Not enough resources are available to complete this operation.
I'm wondering what peoples thoughts are on this, I'm pretty stumped.