Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have a suprising number of issues in a client environment that revolve around being unable to RDP to a system that has remote administration enabled. In all cases a reboot resolves the issue. Is there anything else that others are doing to resolve this? I'd really rather not reboot an otherwise functional server.

Is there a way to reset the RDP connection via WMI? Is there a way to test if the RDP protocol is functional (other than telnet to 3389)


As far as I can tell, no updates have been added. It seems to just die without cause.

share|improve this question
We had this happen a little while ago. I suspect a Windows update broke it, another round of Windows updates a few months later fixed it. I never bothered to figure out which update it was. – Chris S Sep 1 '10 at 16:16
up vote 0 down vote accepted

From our experience this is due to a bug in Windows Server 2003 that causes issues with the remote desktop service. From what we can tell the issues start when selecting the option to apply patches and restart. Our mitigation is to apply patches and don't allow the process to shut down your box, then restart it manually.

share|improve this answer
That sounds reasonable. I can try to correlate RDP issue with patch installs - thanks! – Jim B Oct 7 '10 at 12:26

This can often be caused by services being started in the wrong order following an update. Sometimes starting the terminal services service will fix it but other times there are too many other services which also failed and a reboot is required.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.