rdp reconnect over secure ssh gateway not working
I have successfully set up and used RDP and browser sessions over a secure SSH gateway. Great feature - Thanks!
When the remote RDP windows sessions go into a screen-lock mode due to idleness, I normally will right-click on the RDP entry and choose reconnect so that my credentials are entered automatically for me (our passwords change every 10 hours and have to be retrieved from a vault). However, reconnect does not work over secure ssh gateway and I have to close the session and double-click on the entry in order to connect again.
I can't be sure of this because I don't have another machine where I can install an older version of RDM, but I believe that reconnect used to work and that it stopped working with either the most recent update or the one right before that one.
From what I can tell from the screen messages, the reconnect is atempting to connect over the same random port that was used when the initial connection was made, but it fails.
Note: you don't have to wait until the remote session is screen-locked to duplicate this behavior --any time you try to reconnect it will fail. But the only time I will use reconnect is when the remote session is screen locked.
VPN chaining?
Yes, thank you. That procedure worked. I had not seen that secure gateway documentation before, but had tried to make it work that way on my own before switching gears and going with the proxy over a tunnel approach. I think the only thing I missed when I originally tried it was to check the "Use over secure gateway checkbox".
Thanks again.
VPN chaining?
No, the RDP session does not need to automatically start. If I manually start the RDP session (i.e. double-click on the entry or select the entry and click on the "open session" action), I would like it to launch the proxy which in turn will launch the SSH VPN. What currently happens is that the proxy is launched, but the SSH VPN is not.
VPN chaining?
I have a SSH VPN configured with a dynamic (SOCKS5) outgoing tunnel. I also have a proxy tunnel that proxies a localhost port to a remote host and port via the SSH session. I then have a RDP session that connects to the localhost port on the proxy tunnel (which should then forward that connection through the proxy tunnel an on to the remote host). The tunnel is configured to connect always to the SSH VPN and the RDP session is configured to always connect to the proxy tunnel.
This all works fine if I manually start the SSH VPN first. But my hope was that the chain of VPNs would start automatically (i.e. starting the RDP session would start the proxy tunnel which would then start the SSH VPN). What happens instead is that the RDP session starts the proxy tunnel, the proxy tunnel fails to connect after 5 seconds of waiting (because the SSH VPN is not running), it then starts and tries (and fails) for another 5 seconds to connect to the same proxy tunnel, and finally, it tries (and fails) to connect via RDP.
So my question is: should this kind of VPN chaining work?
remote controlled window title
It would be better than it is now, but personally, I undock my SSH Shells --so also being able to see the changed title on the undocked window's title bar would be the complete solution.
remote controlled window title
The title of the SSH Shell windows does not change when the remote side sends the "Escape <something> Bell" sequence in the same way that Putty and xterms windows do. Do I need to configure or enable something to make this work, or is it not available with the SSH Shell? If it is not available, is it being planned?
My use case is that we use a jump server to access our Linux hosts, so I only have a single SSH Shell connection to our jump server defined in RDM. I may open 10 SSH Shell connections, but they are all (originally) connected to the same jump server and they all have the same window title. From the jump server command lines, I will ssh to whatever servers I need to work on. But since the Window title doesn't change when I ssh to another server, I have to click through all my various Windows to find the session I am looking for when I am working on multiple hosts at the same time.
Putty supports remote controlled title changes (as well as other remote controlled terminal changes like sizing and scrollback clearing), so as I jump from the jump server to another server, the Putty window title changes --making it easier to find the window I am looking for when I have multiple sessions open.
I realize that I can configure and use Putty sessions from within RDM, but I would like to use some of the additional features provided by the stock SSH Shell in RDM --particularly the post login scripting.