1) Turn off the firewall or anything that may be a 3rd party firewall
2) Check the 3 event logs
3) See if there is an optional Log for RDP
I hope this helps !
Main Topics
Browse All TopicsI've used Remote Desktop to connect to my work machine for years. As of two days ago, it stopped working. To be more specific, when I try to connect to it now, I click the "Connect" button, and then nothing happens. No error message. No "failure to connect." It just doesn't do anything.
Some relevant facts:
- This is all on our work network (both via VPN and when I'm in the office)
- I can remote desktop successfully to many other machines in the office
- I did just recently install LogMeIn on the computer, but it did work after that for a few days.
- I have LogMeIn disabled at this point, just to be sure, though.
- I did just install XP SP3, but it worked after that for awhile.
My problem is I can't think of how to debug this. There is nothing in the event logs. There seems to be no verbose or debug mode for mstsc.exe. I'm stuck.
Any ideas?
Thanks,
-Dave
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Thanks for the ideas, guys.
I eventually did see something in an event log that rdpdd.dll was failing (though it only gave a warning, oddly). That led me to some Googling, where I find that the latest nVidia driver can cause this, and I had recently upgraded it. I rolled back the driver, and voila, remote desktop is working fine again.
Thanks!
-Dave
JediBecker,
Thank you for the update! This was excellent as I had the exact same problem. I use RDC all the time from work and struggled to find out why it quit.
Everything works beautifully now. After rolling from nVidia Driver 175.16 back to 169.21 everything work perfectly! In fact I beleive it solved my problem with Star Craft (Broodwar) as well, as it was freezing.
Thanks again!
Well what do you know. Found this forum post that completely fixed this problem for me with the NEW driver:
http://forums.nvidia.com/i
(the relevant post is on that page, and copied here):
This problem is not specific to any one graphics company. It can probably happen with printer drivers too.
The root of the problem is that the session image space is too small and it can't load any more drivers into it. The session image space is shared for the display driver drivers and printer drivers. rdpdd = remote desktop protocol display driver.
You can fix this bug by increasing the size of the session image space via a registry key. Add the following key:
[HKEY_LOCAL_MACHINE\SYSTEM
"SessionImageSize"=dword:0
0x20 == 32 MB works on my system anyway.
Business Accounts
Answer for Membership
by: JediBeckerPosted on 2008-05-29 at 14:31:36ID: 21673465
Incidentally, I just came across the portqueryui.exe app. Here is the result of running that and checking for port 3389. I'm not sure if remote desktop is TCP or UDP, though, so I'm not sure what to make of this. Hopefully it helps someone smarter than me out there...
Starting portqry.exe -n 127.0.0.1 -e 3389 -p BOTH ...
Querying target system called:
127.0.0.1
Attempting to resolve IP address to a name...
IP address resolved to localhost
querying...
TCP port 3389 (unknown service): LISTENING
UDP port 3389 (unknown service): NOT LISTENING
portqry.exe -n 127.0.0.1 -e 3389 -p BOTH exits with return code 0x00000001.