Solved

Windows 2003 Sp1 Server unresponsive to RDP connections.

Posted on 2007-03-30
10
942 Views
Last Modified: 2013-11-21
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.  
0
Comment
Question by:sonofamund
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
10 Comments
 
LVL 29

Expert Comment

by:Alan Huseyin Kayahan
ID: 18824482
               *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?
0
 

Author Comment

by:sonofamund
ID: 18824651
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.  
0
 
LVL 3

Expert Comment

by:jhoop2002
ID: 18824795
besides not having sp2, is your machine fully patched?
0
How Do You Stack Up Against Your Peers?

With today’s modern enterprise so dependent on digital infrastructures, the impact of major incidents has increased dramatically. Grab the report now to gain insight into how your organization ranks against your peers and learn best-in-class strategies to resolve incidents.

 

Author Comment

by:sonofamund
ID: 18824891
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.
0
 

Author Comment

by:sonofamund
ID: 18824896
Yes, ihop2002, the machine is fully patched other than Sp2.
0
 

Author Comment

by:sonofamund
ID: 18825982
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.

0
 
LVL 1

Expert Comment

by:dstynchula
ID: 18826438
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.

Cheers.

Dan
0
 

Author Comment

by:sonofamund
ID: 18876922
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.
0
 
LVL 1

Accepted Solution

by:
Computer101 earned 0 total points
ID: 19271521
PAQed with points refunded (500)

Computer101
EE Admin
0

Featured Post

[Webinar] Code, Load, and Grow

Managing multiple websites, servers, applications, and security on a daily basis? Join us for a webinar on May 25th to learn how to simplify administration and management of virtual hosts for IT admins, create a secure environment, and deploy code more effectively and frequently.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Welcome to my series of short tips on migrations. Whilst based on Microsoft migrations the same principles can be applied to any type of migration. My first tip is around source server preparation. No migration is an easy migration, there is a…
Welcome to my series of short tips on migrations. Whilst based on Microsoft migrations the same principles can be applied to any type of migration. My first tip Migration Tip #1 – Source Server Health can be found here: http://www.experts-exchang…
In this video, we discuss why the need for additional vertical screen space has become more important in recent years, namely, due to the transition in the marketplace of 4x3 computer screens to 16x9 and 16x10 screens (so-called widescreen format). …
With the advent of Windows 10, Microsoft is pushing a Get Windows 10 icon into the notification area (system tray) of qualifying computers. There are many reasons for wanting to remove this icon. This two-part Experts Exchange video Micro Tutorial s…

752 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question