Windows 10: Win10 won't connect to 2012 server with rdp

One of the office computers I have running windows 10 Pro stopped connecting to 1 of our 2012Server using remote desktop connection (RDP). It will connect or other 2012 servers at different locations using different IP Addresses I have disabled the Firewall, Turned off Antivirus, and yes, I have rebooted the PC. Also the User account and password do work if I login to the Remote Server from another PC in the Same office, So it is a Problem with the Win10 PC. I Changed the Network group from Public to Private, still no go. It acts like it just wont connect just that one remote IP server address, all the other remote server I try to connect to work just fine. Is there a file that needed to be Updated, or cache that needs flushed? This happened after the w10 update, but again I dont want to remove all updates, as this connection problem is only giving me trouble on 1 server connection.*Think

:)

 

Slow remote desktop after windows 10 updates

I can't even use UDP.. I have enabled all settings but it doesn't show that UDP is enabled in conn. info box...

I have win10 anniversary update

RDP computer has windows server 2012 r2

 

Windows 10 Remote Connection: Remote taskbar not visible - new quirk

Actually SilvertonOregon's issue was very accurately described.

When a remote desktop connection is made from a Windows 10 computer, the resulting RDP screen shows the remote but with the local taskbar.

For instance, when I connect to one of our Windows 2012 servers, I see the server screen but with my Win10 taskbar.

The issue is new and probably caused by some Win10 update that 'came in' lately.

The following screenshot show the IIS manager of the server and the taskbar of my local Win10 workstation.

T

 

When RDP gets flaky like this, I find that going into System, Remote Settings, and then toggling the radio button for Remote Desktop often helps. That is, you'll click the radio button to "don't allow" then click apply, then click the radio button to "allow remote connections," then click apply again.





Don't ask me why, but it has restored RDP capability to me several times recently on both the Current Branch and on Insider Preview editions of Windows 10. Perhaps it might help you as well?

Here's hoping so!
--Ed--

 

Ok so after trying about every fix and patch, it ended up being a problem with the CISCO E1500 WLS Routers, I reset it back to factory defaults and then re-connected all the computers in the office and the problem with connecting to the Problem 2012 Server's IP went through just fine.

 

Glad you not only found a fix, but shared it with the rest of us. Good work!
--Ed--