RDM v2020.1.19.0 Not able to embed WINSCP window

Hello,

I'm not sure that IPV6 could cause this issue, could you test with a IPV4 server with the socks5 proxy?

Also, which version of WinSCP are you testing with?
And what is the Windows version please?

Regards,

Hi,

I have tested IPv4 with sock5 proxy settings, it is able to embed properly.

The information you have requested are as follow:

Hi,

We were able to reproduce the issue. The error is caused by the "[ ]". When we try to embed an external window, we are looking at the title name.

Character "[ ]" are required for RDM to support IPV6 but WinSCP delete it in the Window title.

I opened a ticket with the engineering department to fix it.

That said, I will strongly recommend using the embedded SCP which is our own integration of SCP and doesn't require any external application.

Could you test the SCP entry and tell me if it works well?

Regards,

Hi,

Great! At least the issue is found.
I have try the built-in SCP but I cant seems to get it work with the sock5 proxy, no specific error was given even with verbose log.
Thus resorting to winscp

Thank you..

Hi,

Verbose and logs can be added through the Advanced tab. Is there any information inside the logs that can help to diagnose?


Regards,

Hi,

I took a look at why would the connection through a proxy could not work and found some problems indeed. I have made the fix and it should be available in the next release. It seems remote working is making proxies more popular these days.

Regards

Hi David and Denis,

Thanks for all the support!
Hope the next release would be available soon :)

Thank you.

Hi,

Sorry to bump this old thread.
I have tried on RDM v2020.2.12.0  and it seems that the problems still persist. The WINSCP in IPV6 is not embedded and the Native SCP does not work on proxy.
Just checking if the mentioned issues are fixed in RDM v2020.2.12.0

Thank you.

Hi,

Correct the WinSCP and IPV6 integration is not yet available in the latest version of RDM.
Regarding the SCP and proxy we made a fix but it seems that something is blocking.

How is the Host and Proxy Host syntax? Is it an IPv4, IPv6 and how do you write it? (Ex. 192.168.x.x, FQDN, 2001:db8::1, 2001:db8:0:0:0:0:2:1, [2001:db8:0:0:0:0:2:1], etc)

Also, if SFTP is enable on the server could you try the embedded mode of SFTP?

Regards,

Hi David,

Thanks for the info that WinSCP and IPV6 integration is yet to be available. Hope it will be available soon.

As for the Host and Proxy Host syntax, it is as follow:
For host field, i have tried both this format 2001:db8:0:0:0:0:2:1, [2001:db8:0:0:0:0:2:1], the result is similar not working.
The Proxy Host (IPv6) is a SSH tunnel to JumpHost with dynamic (-D) options.
This same tunnel works on Winscp

There is one thing i see missing in the Native SCP. I cannot specify the shell to use. I need to specify the shell for my use case.
The sample Winscp setting is as follow:
/rawsettings Shell=bash ProxyHost=127.0.0.1 ProxyPort=8081 ProxyMethod=2

The SFTP is not available on remote server and I can only use SCP in my use case.

Thank you.

Hi,

At this point it will be easier to do a remote session to look at the issue. Soon you will receive an email from our ticketing system to schedule a session.

We also opened a ticket (RDMW-5415) for the shell feature for SCP.

Regards,