Windows 10: RDP to Windows from Linux, strange disconnects after latest feature update

My Windows 10 work PC recently updated itself and ever since I've been having trouble using Remote Desktop.

The behavior is inconsistent and weird:

• If I am already logged in on the host PC, I can connect remotely and everything works the way it normally did, if I specify credentials at the inital login, e.g. on the command line on rdesktop or in Remmina connection settings or in. Before the update I would just be presented with the login screen otherwise and could proceed from there.
• If I am signed out on the host PC, all remote connections just fail, except for a single time immediately after a reboot of the host. In this scenario I can even get the remote login screen. But only that one time. After that, if I sign out, all subsequent connections fail until the next reboot.
• It doesn't seem to matter what client I use (tried a whole bunch that used to work and now suddenly don't.)
• At one point I was able to connect with rdesktop (a particular Linux client), but only if I specified the correct password and an incorrect (!) username. Then I would get the login screen and could enter the complete username (including machine name) and successfully connect. It was consistent for a couple of hours but I can't reproduce it anymore though. Suspiciously, this would only work with the correct password, even though the username was wrong. WTF, right?

Now, I could go on to detail how this behavior is the same on a LAN or through a VPN etc., but I feel fairly confident the issue has nothing to do with that. Because when I look at the Windows (host) event log, I always see the following, in order:

• RemoteConnectionManager: Listener RDP-Tcp received a connection
• RemoteConnectionManager: Remote Desktop Services accepted a connection from IP address x.x.x.x
• Session x has been disconnected, reason code 17

The thing is that when I look up disconnect reason codes, there's like a whole bunch of them. Here on TechNet, or here, for example. But 17 is not listed anywhere, as far as I can tell.

This leads me to think that it's related to some as-of-yet undocumented update to RDP.

So I'm pretty lost here. Do I just accept that RDP is broken and switch to some other (clunkier) solution? Or is there anywhere I might figure out what reason code 17 means?

submitted by /u/ReturningTarzan
[link] [comments]

:)

 

windows 10 RDP disconnection issue

i have windows 10 laptop. i do RDP to windows and Linux machines in Azure cloud.

The RDP is through Cisco anyconnect VPN. using VPN, we connect to our office network first and then we connect to the Azure VMs.

intermittently the RDP is getting disconnection with the following error. sometimes it works for few mins and then disconnect. for some users, it disconnects immediately.

"Because of an error in data encryption, this session will end. Please try connecting to the remote computer again"

taking pcap on the local client, i see the client is sending Rest.

RDP event logs in Microsoft-Windows-TerminalServices-RDPClient%4Operational say the any of the following: messages

RDPClient_SSL: An error was encountered when transitioning from TsSslStateHandshakeInProgress to TsSslStateDisconnecting in response to TsSslEventHandshakeContinueFailed (error code 0x80004005).

RDPClient_SSL: An error was encountered when transitioning from TsSslStateHandshakeComplete to TsSslStateDisconnecting in response to TsSSlNotifyUpperHandlerFailed (error code 0x80004005).

if i disconnect from VPN, no RDP disconnection and its smooth.

any clue about what this error means?

 

Guide: How to enable, use, and configure SLI on Linux.

I guess the next logical step would be to report on the performance you can get with SLI in Linux. That'd be my suggestion anyway.

 

Switch to Linux ??

Find a suitable Linux forum and request comments from people who converted from Linux to Windows, in particular on

• Stability
• Ease of use
• Availability of external help in case of trouble
• Availability of applications, games
• Data exchange with the Windows world