Windows 2003 Sp1 Server unresponsive to RDP connections.

Windows 2003 Sp1 Server becomes unresponsive to RDP connections.   RDP connection screen comes up blank without a login window.  Sp1 was supposed to fix this issue (826139).  Rebooting the server resolves the problem for about 4 days.  Server is a Dell 1600SC.  This is a file and print server.  
Who is Participating?
Computer101Connect With a Mentor Commented:
PAQed with points refunded (500)

EE Admin
Alan Huseyin KayahanCommented:
               *Win2003 Sp2 is released i think. You should install it.
                *Try stoping spooler service and then try RDP.
                 *What is the CPU utilization during RDP?
                *Have you got enough space on HDD?
sonofamundAuthor Commented:
Sp2 is not an option at this point.  Spooler service stoped, with no change.  Disk space is ok.  I will try and set up some performance monitors on that box.  
The 14th Annual Expert Award Winners

The results are in! Meet the top members of our 2017 Expert Awards. Congratulations to all who qualified!

besides not having sp2, is your machine fully patched?
sonofamundAuthor Commented:
Performance monitor will not connect to the server having the RDP problem.  Not sure how I'm able to measure CPU utilization at this point.  Terminal Services manager, however will (correction- did) connect to that box from another server.  It showed 6  connections including Console, Down1, Down2,Down3,Down4,Down5.  I'm unable to reset the Down# connections and not sure I want to reset the console connection.  There are no users sessions active or disconnected.  I've tried resetting the RDP-TCP listener.  At this point I'm unable to connect to the TS manager from another box.

An article suggests the RPC service tieing up TCP port 3389.  The registry can be adjusted for this problem.  I might try it tonight.
sonofamundAuthor Commented:
Yes, ihop2002, the machine is fully patched other than Sp2.
sonofamundAuthor Commented:
Some new interesting information:  Wedesday night's NT backup to external USB drive has failed for some time now.  USB drives are rotated weeknights and Wednesday's external backup drive was bad.

Reboots usually take place on the weekend and the problem is usually discovered towards the middle or later part of the week.  Original theory was that after 4 days it became a problem, but more likely could be related to the drive problem occuring on Wednesday.

Do the application or system event logs contain any recurring errors? When RDP hangs, are you always logging in as the same user? If so, try logging in as a different user in the local administrators group. If that works, it's likely a profile issue. Blowing away the old profile should do the trick. Try connecting to the server console over RDP: mstsc /v SERVERNAME /CONSOLE. If this works, run qwinsta and kill all the idle sessions you're likely to see hanging around. Try connecting to the server using the Computer Management MMC. Once inside, try stopping and starting the "Terminal Services" service. If this resolves the issue, try re-installing terminal services in the add/remove programs > Windows Components Control Panel.

Posting the event IDs you see in the app and system logs will go a long way in identifying the problem.


sonofamundAuthor Commented:
As it turns out, A USB backup drive that was defective caused the problem.  USB external backup drives get rotated every evening.  The Wednesday night backup drive was bad and caused the RDP to become unresponsive Wednesday evening.  Every Thurday the problem would surface.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.