Take the 2-minute tour ×
Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

When I remote into my Windows 8 desktop with Windows 7 it works fine but when try with Windows 8 I get an empty screen after it connects. Keyboard commands work despite the screen being black; I can open Explorer etc. using them and they persist when I reconnect with Windows 7.

Any ideas on what is wrong?

share|improve this question
    
Have you fully patched both computers including option updates? (RDP version 8.0 has come out several weeks ago on Windows 7 and maybe also on 8). –  harrymc Jan 10 '13 at 15:06
    
In addition to @harrymc's suggestion, take a look at the source Win8 RDP settings. Also, are the source (Win7 and Win8) hosts on the same LAN as the target Win8, and the NIC and Comms port speeds verified OK? Lastly, try different NIC ports for the source hosts on your switch. –  Lizz Jan 11 '13 at 6:35
    
Does changing the Windows 8 theme have any effect? On the Experience tab for Remote Desktop Connection, what happens if you connect choosing Modem (28.8 Kbps) and deselect Bitmap Caching? –  user314104 Jul 30 '13 at 1:13

3 Answers 3

A Technet thread suggests typing Ctrl + Alt + End, then cancel, then exiting and reconnecting: http://social.technet.microsoft.com/Forums/en-US/winserverTS/thread/31b681c5-3658-45a5-8158-a0a0f967c4a2

You could also try disabling bitmap caching http://support.microsoft.com/kb/555840

share|improve this answer
    
Link-only answers are a no-no, due to possible future link rot. Please include pertinent information directly in your answer. –  Ƭᴇcʜιᴇ007 Jan 13 '13 at 17:53
1  
Microsoft is usually pretty good about keeping links up, especially KB articles. –  K.A Jan 13 '13 at 18:17
2  
This doesn't work unfortunately –  Michael Jan 17 '13 at 17:42
    
It might not be the same issue - the one in the link is Win Server 2008. At least in my case, nothing happens when I press Ctrl-alt-end, the screen is just black. –  AD. Nov 27 '13 at 14:34
    
@K.A, Tell that to silverlight.net –  Joel McBeth Dec 27 '13 at 21:53
up vote 1 down vote accepted

Open the Local Group Policy Editor on the machine you are running the Remote Desktop client.

Under Computer Configuration>Administrative Templates>Windows Components>Remote Desktop Services?Remote Desktop Connection Client

Enable the setting called Turn Off UDP On Client

Now I'm able to connect without issue... somehow UDP isn't making it through and this change fixes the problem!

share|improve this answer

I spent hours diagnosing this issue, "Turn Off UDP On Client" works around it for me also.

Turns out our office Draytek 2820 has a UDP flood DoS attack trigger which was set to 300 packets / second. Upping to 1000 packets per second resolves this for me.

share|improve this answer
    
This does not really answer the question. If you have a different question, you can ask it by clicking Ask Question. You can also add a bounty to draw more attention to this question once you have enough reputation. –  Chenmunka Jul 11 at 18:48
    
Yes it does. "Any idea what is wrong?" Yes. My router UDP flood attack was false triggering. Exactly the same symptoms and that fixed it. This answers the question. –  Andrew Edwards Jul 13 at 12:21

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.