Windows 2003 Remote Desktop not working anymore

Posted on 2006-04-20
Medium Priority
Last Modified: 2010-04-18
I'm using Remote Desktop to administer my Windows 2003 server. Worked like a charm, till last week. The machine suddenly stopped accepting RDP sessions. I get the "could not connect" message. No logs in the firewall, no event log messages. Turns out the RDP port is not even listening (found that out with netstat). Of course the Remote Desktop is turned ON in System Properties. Has anyone got a clue on what's happening?
Question by:WebDvlp
  • 2
  • 2
LVL 11

Expert Comment

ID: 16495561

Since you've said that it has works till the last week it may be due to this recent Windows Update. It causes many problems these days.

See http://support.microsoft.com/?kbid=918165 for explanation and fix

Or do this (which is a quick way of doing what MS suggest):
Copy the following to the clipboard (it's all one line even if wrapped in your browser - paste into notepad and remove line breaks if necessary, and copy again)
Click Start, run
Paste into the dialogue box and hit return.

==Copy below here==
REG ADD "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Shell Extensions\Cached" /v "{A4DF5659-0801-4A60-9607-1C48695EFDA9} {000214E6-0000-0000-C000-000000000046} 0x401" /t REG_DWORD /d 1
=Copy above here==

Author Comment

ID: 16495683
The KB does not mention Remote Desktop as a possible "victim" for the patch, so I doubt this is the solution. But I'll try it.
LVL 11

Expert Comment

ID: 16495703
This is just one week old update and has caused already a lot of troubles so I suppose that a new undocumented ones will appear the next days. You've nothing to lose if you try it. :)
LVL 85

Accepted Solution

oBdA earned 2000 total points
ID: 16495723
Make sure the Terminal Services service is setup to Manual(!) start and running.
Open the Terminal Services Configuration from the Administrative Tools, and make sure the RDP-Tcp protocol isn't deactivated (little red X below the picture).
In the properties of the connection, under "Network Adapter", make sure RDP is bound to either All adpaters or to the one you're actually using.

Author Comment

ID: 16500520
The RDP-Tcp protocol was not active, thanks!!

Featured Post

Get your Disaster Recovery as a Service basics

Disaster Recovery as a Service is one go-to solution that revolutionizes DR planning. Implementing DRaaS could be an efficient process, easily accessible to non-DR experts. Learn about monitoring, testing, executing failovers and failbacks to ensure a "healthy" DR environment.

Question has a verified solution.

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

by Batuhan Cetin Within the dynamic life of an IT administrator, we hold many information in our minds like user names, passwords, IDs, phone numbers, incomes, service tags, bills and the order from our wives to buy milk when coming back to home.…
Scenerio: You have a server running Server 2003 and have applied a retail pack of Terminal Server Licenses.  You want to change servers or your server has crashed and you need to reapply the Terminal Server Licenses. When you enter the 16-digit lic…
This video shows how to quickly and easily deploy an email signature for all users in Office 365 and prevent it from being added to replies and forwards. (the resulting signature is applied on the server level in Exchange Online) The email signat…
In a question here at Experts Exchange (https://www.experts-exchange.com/questions/29062564/Adobe-acrobat-reader-DC.html), a member asked how to create a signature in Adobe Acrobat Reader DC (the free Reader product, not the paid, full Acrobat produ…

850 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