Add-on Problem: Veeam plugin

avatar

Hello again,

I'm using the veeam add-on and trying to use it with a ssh forward session. Issue is it doesn't seem to honour the port set in the veeam connection

I have an ssh port forward set with source 127.0.0.1 source port 40202 destination 192.168.0.9 destination port 9392.

I then have a veeam connection that connects to 127.0.0.1 on port 40202.

While its connecting it looks like its works (see connecting.jpg) however it then fails and shows that it was trying 127.0.0.1:9392 instead of 127.0.0.1:40202 (see failed.jpg)


I can make it work one of two ways but both will mean i can only connect to one console at a time as the local 9392 port is required.

fix 1
if i leave the ssh port forward as 40202 and add another with the settings ssh port forward to source 127.0.0.1 source port 9392 destination 192.168.0.9 destination port 9392. Then also leave the veeam connection on port 40202, it works

fix 2
If I modify the ssh port forward to source 127.0.0.1 source port 9392(from 40202) destination 192.168.0.9 destination port 9392 and set the veeam connection to 9392 it works.

Another thing of note is if i don't have the ssh port forward source of 127.0.0.1:9392 it still knows if i get the login details wrong(see weird.jpg) or if i have the wrong version of the veeam client installed on my pc with just the 40202 forwarded

Is there a way to resolve this as we have multiple veeam servers in a dmz (accessible via the ssh tunnel) that i need to connect to(obviously I just change the source port for each console.)

Cheers,
Craig

weird.jpg

failed.jpg

connecting.jpg

All Comments (3)

avatar

Hello Craig,

Thank you for taking the time to report your issue. I'll take a look and see if I can reproduce the problem as soon as possible and keep you updated on the progress.

Regards,

Michaël Beaudin

avatar

Hello,

I've just completed a few tests using Veeam from outside of RDM and I still got the same issues. This eliminates the possibility of our add-on having an issue.

Our port-forwarding also works with everything but Veeam. It seems to me that the problem lies with the Veeam software itself and doesn't originate from our side.

This is the error we get on the forward session : "Forwarded port closed due to local error: Network error: Software caused connection abort" which happens after Veeam refuses the connection.

Veeam already has a thread on this error though I'm not convinced it will help in this case. If you want to give it a try here is the support thread: https://www.veeam.com/kb2127

If the thread doesn't help, I'd recommend using either the fixes you have stated in your earlier post or get in contact with Veeam's support department to see if they have any problem with their port handling.

Best regards,

Michaël Beaudin

avatar

Thanks Michaël, you time looking in to that is much appreciated.

Regards,
Craig