Version 12.4.3.0 - RDP through SSH

Hello,

Unfortunately we haven't been able to reproduce the issue even with the template you provided.

Could you try to create an SSH Tunnel entry as a standalone and see if it can connect, then use a standalone RDP session that passes through it? I want to see if the issue is with the template itself, or with the SSH tunnel / RDP passing through it.

If you have any log you can send us from the SSH Tunnel it would be helpful.

Regards,

So a liitle more digging...

It appears that if i try to connect 3-5 times in a row, it will eventually connect. If i try to create a ssh connection with putty outside of RDM it appears to work everytime.. ill see if i can screen capture it for you.

Chris

Thank you Chris. If you can enable logs in your SSH tunnel entry or otherwise give us any other relevant information, it might be useful for us to pinpoint the issue, too.

Regards,

hi gents... perfect timing... First time worked... second time failed...





[10/04/2017 18:40:58] Looking up host "home.XXXX.XX"
[10/04/2017 18:40:58] Connecting to 80.229.XX.XX port 22
[10/04/2017 18:40:58] We claim version: SSH-2.0-PuTTY_Release_0.67
[10/04/2017 18:40:59] Server version: SSH-2.0-OpenSSH_6.8p1-hpn14v6
[10/04/2017 18:40:59] Using SSH protocol version 2
[10/04/2017 18:40:59] Doing Diffie-Hellman group exchange
[10/04/2017 18:40:59] Doing Diffie-Hellman key exchange with hash SHA-256
[10/04/2017 18:40:59] Host key fingerprint is:
[10/04/2017 18:40:59] ssh-rsa 2048 XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:d5:d0:48:6a:81
[10/04/2017 18:40:59] Initialised AES-256 SDCTR client->server encryption
[10/04/2017 18:40:59] Initialised HMAC-SHA-256 client->server MAC algorithm
[10/04/2017 18:40:59] Initialised AES-256 SDCTR server->client encryption
[10/04/2017 18:40:59] Initialised HMAC-SHA-256 server->client MAC algorithm
[10/04/2017 18:40:59] Sent password
[10/04/2017 18:40:59] Access granted
[10/04/2017 18:40:59] Local port 127.0.0.1:33390 forwarding to lyncfe3.XX.net:3389
[10/04/2017 18:41:05] Opening connection to lyncfe3.XX.net:3389 for forwarding from [::1]:21699
[10/04/2017 18:49:06] Forwarded port closed due to local error: Network error: Software caused connection abort
[10/04/2017 18:49:14] Looking up host "home.XXX.XX"
[10/04/2017 18:49:14] Connecting to 80.229.XX.XX port 22
[10/04/2017 18:49:14] We claim version: SSH-2.0-PuTTY_Release_0.67
[10/04/2017 18:49:14] Server version: SSH-2.0-OpenSSH_6.8p1-hpn14v6
[10/04/2017 18:49:14] Using SSH protocol version 2
[10/04/2017 18:49:14] Doing Diffie-Hellman group exchange
[10/04/2017 18:49:14] Doing Diffie-Hellman key exchange with hash SHA-256
[10/04/2017 18:49:14] Host key fingerprint is:
[10/04/2017 18:49:14] ssh-rsa 2048 XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:d5:d0:48:6a:81
[10/04/2017 18:49:15] Initialised AES-256 SDCTR client->server encryption
[10/04/2017 18:49:15] Initialised HMAC-SHA-256 client->server MAC algorithm
[10/04/2017 18:49:15] Initialised AES-256 SDCTR server->client encryption
[10/04/2017 18:49:15] Initialised HMAC-SHA-256 server->client MAC algorithm
[10/04/2017 18:49:15] Sent password
[10/04/2017 18:49:15] Access granted
[10/04/2017 18:49:15] Local port 127.0.0.1:24507 forwarding to lyncfe3.XX.net:3389
[10/04/2017 18:49:21] Opening connection to lyncfe3.XX.net:3389 for forwarding from [::1]:21820
[10/04/2017 18:49:22] Forwarded port closed due to local error: No error

i have taken out some of the private data... i can DM if you need it...

As i said earlier. When i tried with the stable version - works everytime

first disconnect was due to me closing the window... assume thats what

Software caused connection abort

means

I think the error you're getting is the same we fixed internally last week. I attached to this post two DLL files that contain that fix. Could you put them in the x86 and x64 folders located in your RDM installation folder? It fixed the "no error" bug for our other clients.


Regards,

Boom.... That worked!

Perfect, straight in every time....

just to let you know... i am on 12.4.4.0 now

Glad to hear it works :) The DLL fixes will be available officially in the next beta version.

Regards,

Big thumbs up....

Thanks for a terrific product and keep up the good work