Hi, I've recently been trying to configure RDP connections through an SSH Tunnel.
The tunnel connects fine, but when it tries the RDP connection it immediately fails with the following error.
I've turned on logging for the SSH Tunnel connection and see the following, but am unsure of what it means.[26/06/2019 13:11:15] Sending kex init[26/06/2019 13:11:15] Received kex init[26/06/2019 13:11:15] Selected algorithms: curve25519-sha256, ssh-ed25519, chacha20-poly1305@openssh.com, chacha20-poly1305@openssh.com, implicit by cipher, implicit by cipher, none, none[26/06/2019 13:11:15] Sending Ed25519 kex init[26/06/2019 13:11:15] Received Ed25519 kex reply[26/06/2019 13:11:15] Successfully authentified server[26/06/2019 13:11:15] Sending new keys message[26/06/2019 13:11:15] Sending userauth service request[26/06/2019 13:11:15] Received new keys message[26/06/2019 13:11:15] Received service accepted message[26/06/2019 13:11:15] Sending userauth init request[26/06/2019 13:11:15] Received userauth failure: publickey,password[26/06/2019 13:11:15] Starting password authentication[26/06/2019 13:11:15] Sending userauth password request[26/06/2019 13:11:15] Received userauth success[26/06/2019 13:11:15] User authenticated successfuly by password[26/06/2019 13:11:15] Listening on 127.0.0.1:12737[26/06/2019 13:11:17] Received global request: hostkeys-00@openssh.com , no need to reply[26/06/2019 13:11:24] Aborting connection, unknown SOCKS version: 3[26/06/2019 13:11:24] Closed tunnel: 127.0.0.1:12737 -> ?:0
Hello,
The issue seems to be that your RDP connection tries to use the SOCKS 3 protocol which isn't supported by the tunnel itself.
What version of RDP are you using and what operating system are you on? Is your entry configured to use FreeRDP?
Regards,
Hubert Mireault
Hi Hubert,
I'm running Windows 10 1809, and the connection is set to use 'Latest'.
I've just now tried to change it to use RDP 8.1, RDP 7.0 and FreeRDP 7.0 and force it, but still receive the same error.
Any suggestions what further to try?
Could you try MSTSC.exe (Microsoft Remote Desktop Connection)? If it doesn't work with MSTSC it would mean there is either an issue or a configuration of RDP that prevents it from using a SOCKS 4 and above proxy.
Regards,
Hubert Mireault
Apologies for the ignorance, how would I do that with mstsc?
Would I open a proxy connection manually and then try using mstsc to connect to localhost on that port?
Hello Raphael,
It will be a pleasure to help you to test with mstsc, that being said, before doing this test. Could you confirm some details of your configuration?
What type of entry is used in RDM, is it an SSH Tunnel? If so is the tunnel Dynamic or Static?
If you prefer sending us a print screen feel free to send them at ticket@devolutions.net .
If the tunnel is dynamic the socks 3 seems to be open by other tools have you any tools that convert dynamic tunnel to make it usable with RDP? Or you use the standard Windows Proxy feature?
Best regards,
David Grandolfo