1

I have been able to remote desktop into my Windows Server 2008 R2 machine no problem. But then I installed a bunch of updates (including SP1) and now I can't RDP.

Some background info:

RDP is enabled (and Everyone is set to have connect permissions)

I have disabled the firewall with no luck.

I can ping the server no problem and can connect through all other normal means.

What could be causing this?

Edit: The port TCP 3389 is NOT LISTENING. Why would it be NOT LISTENING if the firewall is disabled??

4 Answers 4

3

I've been in a struggle with this same problem exactly today: a Windows Server 2008 R2 server was handling RDP fine, until someone installed SP1; then, all of a sudden, the Remote Desktop service started crashing on startup and/or on user connection. Looks like the problem was somewhat related to applying SP1 after the system had been up and running for a while... probably some pre-SP1 update is not compatible with SP1 itself.

Some suggestions:

  • Check that the "Remote Desktop" service is started. If it's not, start it.
  • Check that the "Software Protection" service is started, too. If it's not, start it.
  • Check the event log for an application crash related to the Remote Desktop service. If you find it, look at the version number of the referenced DLL(s). Chances are, it's 6.1.7600.X (RTM), instead of 6.1.7601.X (SP1). If this is the case, try replacing those files with the same ones from a working SP1-ed server.
  • If all else fails, uninstall SP1 and then re-install it; but this time, use the full installation package, do not apply SP1 through Windows Update.
3
  • Weird. I've done lots of server updates and the remote deskop always worked
    – ADNow
    Apr 5, 2012 at 20:40
  • 1
    That was it!!! The Remote Desktop service WASN'T started and it was set to Manual. Funny, huh. Thanks!!!! Apr 5, 2012 at 20:44
  • The same for me. I spent the whole day thinking "weird weird"... I still don't know what actually happened. But I know installing a SP via Windows Update is just asking for troubles.
    – Massimo
    Apr 5, 2012 at 20:45
3

As documented in the blog post here, I found the problem is due to hotfix 2667402.

I was able to solve the problem by logging into the affected server locally and running

wusa /uninstall /kb:2667402 /quiet /forcerestart

at a command prompt. After the server rebooted I was able to RDP to it again

0

From what OS are you trying to connect?

Check the remote desktop settings, is it the middle option?

enter image description here

3
  • The connecting OS is Win7, and yes that option is set. No luck. Any other ideas? Apr 5, 2012 at 20:25
  • Any unusual events in Event logs?
    – ADNow
    Apr 5, 2012 at 20:25
  • Unfortunately no. Apr 5, 2012 at 20:35
0

I was connected to an rdp session which suddenly hung and disconnected me, not letting me reconnect anymore. I scoured the net and tried everything to no avail (sc, pskill, etc.), as Terminal Services was running, but for some reason was unresponsive to requests. This is how I got it to work again once I accessed it via vnc:

On the server:

  • Open Windows explorer.
  • Right-click on "This PC" and select properties.
  • Click on remote settings and select the "Remote" tab.
  • Select "Don't allow remote connections to this computer."
  • Click on Apply.
  • Select "Allow remote connections to this computer."
  • Click on Apply and then OK.

A few answers I found mentioned that rebooting fixed the problem. I couldn't do this at the time, as I had users at work - I did reboot after they had left for the day, for good measure. As a side note, while this rdp non-sense was going on, everything was normal as far as my users was concerned (no one even knew that something was off).

I always install an alternative program to allow remote control of computers, even if I have RDP set up. TightVNC is a good option, or you can go with TeamViewer or a number of other programs used for this purpose.

Alex

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .