RDP file in a text editor and add these lines to the end: Open the MS RDP Client (The UWP Client may not work).RDP file that can connect to a Windows Server system that has TLS 1.0 disabled: Re-enabling TLS 1.0 did not make sense in our case, so we we created a special saved-RDP session that could be used to connect to the server. RDP session file to force the windows RDP client to connect. When looking for solutions to this problem I found that I could either re-enable TLS 1.0 -or- enable some obscure flags in a saved. Windows RDP clients do not fall-back to an insecure mode and instead give you a cryptic error message which is meaningless. So, mystery solved: If the Mac encounters an RDP server that does not support TLS, it falls-back to 'RDP Security' and 'dont negotiate' by default. Once the Mac RDP client has passed in all zeros for its requestedProtocols, the server responds back with a valid RDP session that can be used. When that fails (the mac gets the hard-reset from the server), it tries again and this time it sets requestedProtocols to 0x00000000. The answer lies in the way the Microsoft RDP client for Mac works: It tries to connect to the server using reasonable security settings by setting requestedProtocols to TLS, CredSSP and Early User Authorization Result PDU Supported. The big question I had was why RDP was working from a Mac and not from any of our PCs. The SysAdmin in charge of the system had unchecked the "Allow connections only from computers running Remote Desktop with Network Level Authentication (recommended)" checkbox to allow RDP to work again on his Mac. After TLS is disabled, RDP with NLA ceases to work. This issue appears to be tied to disabling TLS 1.0 on the Windows Server. You can see that the Server resets the connection suddenly and without explanation.Īn RDP session initiated from a Mac works and looks like this: When you use Wireshark to examine the connection, you see this:īroken out the traffic exchange looks like this:
When you try to connect to a Windows Server 2008 R2 system (other versions may be impacted as well) using the RDP client from any version of windows (I tried 10, 8.1, 7 and XP) you get the following error message:
How do I disable TLS 1.0 without breaking RDP?.Mac clients can RDP into server yet Windows clients are unable to connect.It took a little time to track this down and now that I've been through the troubleshooting process I know how to fix it and can see how we wound up in this situation in the first place Paradoxically, SysAdmins who run Macs were not affected. An interesting problem surfaced earlier this year that prevented our systems administrators from using RDP to connect to a windows server if they use a windows laptop.
0 kommentar(er)
