Port Forward - Fatal Error

Hello,

Do you get the error after the portforward connection has been connected for a long time, or is it after it opens? If there are any logs they should be located in the Help tab of RDM then in application logs.

Regards,

It's after it's been open for a while. Sometimes a few hours, sometimes 15 minutes.
I checked the Application Log and there is only a bunch of info about DB Upgrades. Is there somewhere I can turn on extra logging?

Hi,
I will assign this to Denis. Have you tried RDM 10.9.12?

I'm on the latest Beta. It's been happen for the last few versions but is random.

Just checked with others in our area and we're all getting this error periodically. Let me know if I can provide any info from my side to help narrow down what might be causing this.

Thanks.

Hello,

Does the "Fatal error" message box contain any additional info? It should contain at least a longer message starting in RDM 11. Could you try the latest version of RDM which should be 11.0.8.0?

Regards,

I'm using 11.0.7.0 and the error only has 1 extra line from the original screenshot.

Hi,

What kind of traffic are you forwarding through the connection? For example is it RDP, Telnet, something else?

Denis will take a look at this when he can. Unfortunately, since the error message is pretty vague and the issue seems to happen at random, it might take some time to find and fix the problem. We think it might be a timeout issue but we aren't sure yet.

Regards,

We just use a Port Forward session to open a bunch of SSH connections to the servers. From there we then RDP into the servers we need to use. It definitely could be a certain server on the other end is losing its connection or something. I just don't see any info to help me verify what's going on.

Hi,
we're using RDP Manager 11.0.10.0 and are facing the same problem.
We also use a lot of ssh tunnels to rdp to different servers.
In these profiles we use "localhost" - port "0" for RDP and under "VPN/SSH/Gateway" -> settings we use "127.0.0.1" with "use dynamic port" enabled and remote host "target IP" with Remote-Port 3389

Are you able to reproduce it with one specific connection or it's random?

sorrily I am not, as I'm nearly always having at least 2 connections online.
I'll tell you as soon as possible when it happens when only one RDP is connected

I suppose that if you retry it works?

if you hit "ok" you can continue working without any problem.

Hello,

Does the SSH tunnel connection close or does it stay open? What prompt shows that requires you to click "ok", is it an error message?
Denis will take a look at this when he's available.

Regards,

I don't know if it stays open or not, but I think it does stay open because I can continue working without any downtime.
The error message is exactly the same that Kelemvor posted 22 days ago.

it just happend without any connected session! very strange

Could verify if you have anything in the application logs?

I don't see anything - sry

Hello,

Just to confirm, the error message also says "Network error: Software cause connection to abort"?

By default, when encountering an error, the tunnel entry closes. Could you try something:
1. Uncheck the "close on disconnect or error" checkbox in the tunnel's settings, and check the "show logs" if unchecked
2. When the error happens, the tunnel session should stay open
3. Check the log output in the session itself. There might be information as to what caused the issue there. It might be the timeout issue we're trying to figure out.

Regards,

Hi,

this is what I see in the log:

-----
Looking up host "remote.host.de"
Connecting to 8.9.10.11 port 225
We claim version: SSH-2.0-PuTTY_Release_0.64
Server version: SSH-2.0-OpenSSH_6.7p1 Debian-5
Using SSH protocol version 2
Doing Diffie-Hellman group exchange
Doing Diffie-Hellman key exchange with hash SHA-256
Host key fingerprint is:
ssh-rsa 2048 b5:05:5b:8....:01:1b:10
Initialised AES-256 SDCTR client->server encryption
Initialised HMAC-SHA-256 client->server MAC algorithm
Initialised AES-256 SDCTR server->client encryption
Initialised HMAC-SHA-256 server->client MAC algorithm
Sent password
Access granted
Opening session as main channel
Opened main channel
Local port 127.0.0.17:62359 forwarding to 192.168.150.246:3389
Allocated pty (ospeed 38400bps, ispeed 38400bps)
Started a shell/command
Opening connection to 192.168.150.246:3389 for forwarding
Initiating key re-exchange (timeout)
Doing Diffie-Hellman group exchange
Doing Diffie-Hellman key exchange with hash SHA-256
Initialised AES-256 SDCTR client->server encryption
Initialised HMAC-SHA-256 client->server MAC algorithm
Initialised AES-256 SDCTR server->client encryption
Initialised HMAC-SHA-256 server->client MAC algorithm
Initiating key re-exchange (timeout)
Doing Diffie-Hellman group exchange
Doing Diffie-Hellman key exchange with hash SHA-256
Initialised AES-256 SDCTR client->server encryption
Initialised HMAC-SHA-256 client->server MAC algorithm
Initialised AES-256 SDCTR server->client encryption
Initialised HMAC-SHA-256 server->client MAC algorithm
Initiating key re-exchange (timeout)
Doing Diffie-Hellman group exchange
Doing Diffie-Hellman key exchange with hash SHA-256
Initialised AES-256 SDCTR client->server encryption
Initialised HMAC-SHA-256 client->server MAC algorithm
Initialised AES-256 SDCTR server->client encryption
Initialised HMAC-SHA-256 server->client MAC algorithm
Initiating key re-exchange (timeout)
Doing Diffie-Hellman group exchange
Doing Diffie-Hellman key exchange with hash SHA-256
Initialised AES-256 SDCTR client->server encryption
Initialised HMAC-SHA-256 client->server MAC algorithm
Initialised AES-256 SDCTR server->client encryption
Initialised HMAC-SHA-256 server->client MAC algorithm
Initiating key re-exchange (timeout)
Doing Diffie-Hellman group exchange
Doing Diffie-Hellman key exchange with hash SHA-256
Initialised AES-256 SDCTR client->server encryption
Initialised HMAC-SHA-256 client->server MAC algorithm
Initialised AES-256 SDCTR server->client encryption
Initialised HMAC-SHA-256 server->client MAC algorithm
Network error: Software caused connection abort
----------

(I changed the IP, Remote-Host and RSA Key)

Regads,
Harry

Hello,

We will investigate this behavior.

In the next version of RDM, there will be an "Enable TCP keepalives" option with a timer in the advanced tab which might help against these issues. When it's live, could you give that new option a shot? If the issue is still there, could you paste your logs like you did in your last post? Thank you.

Regards,

As a test I opened up my 4 Port Forward session and let them sit. I did not actually open any RDP connections over those connections so just the basic SSH connections where made but no traffic was passed. After 20 or so minutes I got 4 Fatal Errors and all 4 of my sessions disappeared.

I just now launched 1 RDP connection to each of my locations which auto launched my 4 Port Forward sessions again. I'll let this sit and see what happens.

*push*
Sorry guys, it happens again!
This was fixed and came back with another update.
Please fix it again!

Regards,
Harry

Did the "Enable TCP keepalives" fix the issue previously? Apart from that, we hadn't changed anything, so that is strange.
Does it happen randomly or is it every single time?

Regards,

interesting. we didn't change anything last time and the error was gone.
Now I activated the keepalive in every single connection. Sorrily I had to edit every single connection manually because group editing would override the custom destination IP :(
Maybe you could change that too!

I'll keep an eye on the error message.

Regards,
Harry

It would be interesting to add, we'll have to check how to do it properly.

If you ever need to change it again, you can do a Batch Action > Custom Powershell Command, and use the following:

$connection.Terminal.EnableTCPKeepalives = $True;
$RDM.Save();

You can replace $True with $False if you want to disable the TCP Keepalives. That will allow you to only change this value in a batch.

Regards,

I ran the Powershell command just now so I'll keep an eye on it too.

Thanks.