remote desktop issue

[SKJoy2001]

Experiencing the same exact problem. My additional finding is, after the hung screen of the RDP to my desktop, when the desktop refuses to let you log in even locally, I closed the RDP client on my laptop, waited like 30 seconds or a few seconds more, and then my desktop allows me to log in locally, without a reboot.

It is something related to the topic that the previous RDP session gets hung and remote or local logging in are refused!

This problem in not related to ZoneAlarm or any other 3rd party firewall. I don't have ZoneAlarm or any other 3rd party firewall installed on any of my systems. All the systems are using Microsoft Windows 7 Ultimate x64, Microsoft Security Essentials & Windows Firewall.

I am trying to RDP inside my local WiFi network through a NetGear router which is working simply great.

Anyone out there with knowledge what is causing this and how to fix this?

 

[Feanor]

I am pulling my hair out on this one. This has been plaguing me since Windows 7 RC1 and I thought MS would have it fixed by now.

For me the problem is inconsistent (not 100% reproducible). Sometimes after disconnecting a remote desktop session I return to my desk to find the PC locked at a black screen where I can do nothing. I also cannot use RDP to get back into the machine because I receive the "remote desktop services is currently busy" error. For me this problem will last overnight, it will not go away for in 30 seconds like the previous poster.

I have to hard power off the machine to get back in.

We're not using Zone Alarm and we have been through a couple different antivirus/software firewall solutions. No change regardless of what we are using, including after performing a fresh installation of Windows 7. It happens when I remote in from various remote desktop clients, ranging from XP to Vista to Windows 7 (both 32 and 64-bit).

chev65, your response sounds like it came straight from Microsoft. Disconnecting is a perfectly legtimate option; sometimes you cannot stop all the running processes on the machine. We shouldn't have to work around this serious flaw in the OS.