Multiple VPN (Tunnelier) sessions opened
I've got approximately 10 MS RDP sessions that are configured to launch Bitvise's Tunnelier software (which is now called "Bitvise SSH Client", with new executable names, FYI) before the RDP sessions can connect. I have the Bitvise SSH Client configured with a profile that creates 10 port forwards for RDP (e.g. 127.0.0.1:1001 goes to server1:3389; 127.0.0.1:1002 goes to server2:3389; etc). I have also configured each of the RDP sessions in RDM to be in the same VPN group, thinking that it would only launch the SSH tunnel once. Unfortunately, the SSH tunnel is re-launched for each RDP session that I try to open, and because all of the port forwards are already in use from the first connection, additional errors are generated.
Is there any way for these connections to recognize that the VPN/SSH connection has already been established and to just utilize it, rather than trying to re-open the connection?
I am currently using RDM Enterprise 7.6.1.0 with the Bitvise Tunnelier addon 2.2.0.1. The Bitvise SSH Client is version 4.50.
Thank you!
All Comments (9)
Have you tried the option "connect if unable to connect" on the vpn tab?
best regards
Tobias
Tobias,
I assume that you are referring to the "Connect if unable to ping" option. If so, that won't work in this case, as 127.0.0.1 (and the server's regular addresses) will return pings without the tunnel open.
yes, but you can try "connect if unable to ping (custom)" and define the regular IP (like 172.16.x.x) of the server in the field "ping host (custom)" (I use version 7.6.2)
So if the tunnel is established the host should be reachable with his IP, isn't it?
best regards
Tobias
The only thing that is sent through the SSH tunnel is RDP traffic (via 127.0.0.1 port forwarding on the client). The server's IP (which is a public IP) will always return a ping, regardless of whether or not the SSH session is open.
is it important that the server (with a public IP) is answering to a ping? (what about the security?)
If it's not important you could allow (if possile) ping within the tunnel.
best regards
Tobias
Since ICMP and ping requests don't use ports, I don't believe that they can be forwarded through an SSH tunnel - I'd just get a response from the localhost, which would always reply.
you are right through a SSH tunnel its very difficult :-/
with a normal vpn tunnel it would be easy ;)
sorry I am out of ideas at the moment
best regards
Tobias
Maybe you can come up with something using the "VPN group" function?
edited by alphanimal on 10/1/2012
alphanimal, as previously indicated that did not work, unfortunately.