Remote Desktop keeps dropping connection

Question

Hi,

I've just upgraded to Windows 8 from Windows 7. The main issue I have now with Windows 8 is that the remote desktop client is somehow broken for me. Whenever I use it, it blocks (i.e. I cannot interact with the remote computer) and then I get the pseudo-dialog box stating reconnecting and it will reconnect and I get back the remote access. It does this all the time (about every few minutes). Note that when I cannot interact with the remove computer, I can still ping it just fine. So clearly it is not a connection problem.

It seems to be an issue with the Microsoft Remote Desktop Client because I was so fed up, that I tried 2 alternatives: Terminals and mRemoteNG. Using them, the connection never drops.

However I'd like to use the Microsoft client as it is more practical to use. I've tried to copy some binaries from Windows XP or Windows 7, but they don't work properly when I try to launch them, I guess it is more than just `mstsc.exe' that one needs to copy (I've copied mstscax.dll as well, but it kept loading the one from Windows 8).

Anyone having a similar issue?

Thanks,

Manu

Answer 1

A hotfix came out on 11/13 that appears to fix this issue for me. The KB number is 2897602.

http://support.microsoft.com/kb/2897602

Answer 2

I'm linking this to my issue as it all points to the same kind of faults in Windows 8, its all about Windows 8 failing and you gotta keep looking for answers somewhere. My temporary workaround involves leaving the printer turned on all day while I use Win 8. That's not a 100% solution to RDP but it mitigates the issue and allows it to connect without dropping 90% of the time. Using the Metro UI causes it to fail more though. 

http://answers.microsoft.com/en-us/windows/forum/windows_8-networking/remote-desktop-keeps-dropping-connection-this-is-a/4ab6791f-855c-475a-96e9-07b31f2faecb

Answer 3

Vinod, this issue is NOT better suited in the TechNet community.

This is a well known issue and Microsoft should work on resolving it.

Please do your work and escalate this. Thanks.

Answer 4

I think this is related to my post (very similar issue), and my testing confirmed it is caused by the printer drivers.

Answer 5

Could you provide the location of that setting in gpedit.msc?

Thanks