RDP Fails After Server Restart; No Process Listens on Port 3389


I faced really interesting problem – one of our servers stopped responding to RDP after server restart. I spent some time trying to troubleshoot it.  This article from Microsoft gives good a course of troubleshooting. This one also can help. Unfortunalely, nothing helped in my case. Finally I opened a ticket with Microsoft. It took 4 hours to find the real root cause of the issue

First, we tried to install a hotfix, described here, but the installer hung up every time during the file backup. The further investigation showed, that if the Print Spooler service stopped, RDP worked just fine. Then we checked the
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Printers registry key and found a few keys for redirected printers, which was not deleted after server restart. Deleting these keys resolved the issue.

Advertisements

3 Responses to RDP Fails After Server Restart; No Process Listens on Port 3389

  1. Anonymous says:

    I had the same issue. Your post led me to delete the redirected printer registry keys. Many thanks!

  2. Anonymous says:

    Thanks to this post, my issue was resolved

  3. MohamedRaja says:

    Thank you very much this article resolved my issue.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: