Windows 2003 Remote Desktop not working anymore

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?
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.


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 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==
WebDvlpAuthor Commented:
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.
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. :)
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.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
WebDvlpAuthor Commented:
The RDP-Tcp protocol was not active, thanks!!
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2003

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.