pzam
asked on
Terminal Server hanging intermittently on Server 2003
We just migrated (moved cabinets) a Windows 2003 server that is a dedicated terminal server. Ever since the migration, the terminal server service intermittently hangs - about once each day. We can still ping the server, but we cannot connect via RDP or remote console app without restarting the server.
The server averages about 30-35 concurrent users at any given time, and there are 100 TS licenses installed on the system.
I have yet to find anything in the logs that seemed like a smoking gun - mostly the normal printer driver issues and occassional hive key notices. (we are running UPHClean). I have found a number of articles on the net that reference this issue, but I have yet to find a solution that works.
The server has SP2 installed, and memory usage hovers around 50%.
Any assistance would be greatly appreciated.
The server averages about 30-35 concurrent users at any given time, and there are 100 TS licenses installed on the system.
I have yet to find anything in the logs that seemed like a smoking gun - mostly the normal printer driver issues and occassional hive key notices. (we are running UPHClean). I have found a number of articles on the net that reference this issue, but I have yet to find a solution that works.
The server has SP2 installed, and memory usage hovers around 50%.
Any assistance would be greatly appreciated.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
The only other comment was good advice...just not the solution.
I'm assuming you've gone through the event viewer (system, application). Anything odd? When it's hanging go to the command prompt and do "netstat -an | more" and check your outbound & inbound traffic. Is port 3389 listening? Are there existing connections on port 3389? I'd also download process explorer from Sysinternals. It's small & free. Keep that running and watch for running out of resources: memory, cpu, check disk i/o, network traffic. Also make sure you don't have something odd like a resource or handle leak...a process or app that uses resources like tcp sockets and never releases them...after a while you have no more free ports to make new incoming or outbound connections.