[ Multiple RDP via one SSH Tunnel ] - Is it possible to have Dynamic SSH port forwarding ?
[ Multiple RDP via one SSH Tunnel ] - Is it possible to have Dynamic SSH port forwarding ?
Dear Support,
I am new to your RemoteDesktopManager (Enterprise version).
1\
Until Today, I am using Royal TS in order to connect via SSH Tunnel.
In Royal TS, I am using the built-in Putty SSH client.
and I must pre-configure the local-port mapping in the Putty SSH tunnel .
e.g.
1) local Port 50001 will be mapped into RemoteServer01_IP:3389
2) local Port 50002 will be mapped into RemoteServer02_IP:3389
3) local Port 50003 will be mapped into RemoteServer03_IP:3389
...
Next, when I create RDP object on Royal TS, I must set the destination IP to 127.0.0.1:50001 for RemoteServer01 ....
2\
I search your different guides on how to setup RDP via SSH tunnel on RDM product.
Indeed I could see several methods.
e.g. SSH VPN ; SSH Tunnel ; SSH port-forwarding ......
But,
Recently I saw a nice implementation of this on SecureCRT version 8, as followed:
Step 1: Create a standard SSH object toward the SSH Tunnel server.
Step 2: for each new SSH server that you need to declare , to connect via the SSH tunnel:
You create it normally by setting the actual Remote Server IP address, and not the local host 127.0.0.1 mapped into a local port.
At the same screen where you configure the remote server real IP,
you have a Firewall field where you select the SSH Tunnel session you created.
My point is: You don't need to worry about the local ports mapping....
3\
So, my question to you please :-)
Is there a way to declare several RDP server on your product,
and configure the real server IP (and not 127.0.0.1)
and it will use the SSH dynamically , based on the fact that In the VPN - Settings tab, we can click on the drop down menu next to Session and select your SSH Tunnel entry previously created ...:- )
Thank you!
All Comments (25)
Hello,
I think the information's that you are looking for is described in the article below
https://help.remotedesktopmanager.com/howto-setupsshtunnel.htm
Best regards,
Jeff Dagenais
Hello,
Thanks for the feedback.
But, it is not what I am looking for.
Based on this procedure, I MUST:
create SSH object for each RDP session.
On the RDP object, I must set it with destination address 127.0.0.1
I am looking for a solution like in SecureCRT.
In the RDP object you configure the actual IP address of the remote server.
And via Generic setting, it will know to route through the SSH tunnel.
I don't want to manage local ports mapping if I have for example 50 RDP objects to configure on my Servers Tree...
Thanks!
Hello,
Inside the SSH Tunnel session, it's possible to select Dynamic regarding the port fowarding
It's also possible to configure several sessions at the same time to use the same SSH Tunnel if you would like.
This is possible using the Batch Edit feature.
https://help.remotedesktopmanager.com/edit_batch.htm
Best regards,
Jeff Dagenais
Hi Jeff,
I am not sure you understood what I asked.
Thanks.
Hi,
We aren't sure about the technology used to perform what you explained, but is it similar to this step? https://www.vandyke.com/support/tips/socksproxy.html
If yes, in SecureCRT the local port 127.0.0.1 is also bound to let you link to a remote server.
Otherwise, if you do not bind anywhere the localhost IP, it looks more to be a VPN connection.
What is the step performs with the external application. Base on this I could confirm if RDM have that feature?
Best regards,
David Grandolfo
Hi David,
Thank you for your feedback.
Indeed the link you provide is what I am looking for.
Specifically, pay attention to the following statement from this SecreCRT link:
When connecting through an SSH SOCKS proxy, host name resolution occurs on the SSH gateway server. Therefore, you would specify the Hostname as it is known by the gateway server, which will be making the connection to the host on behalf of SecureCRT
So indeed as you say, also SecureCRT bind local port 1080 with 127.0.0.1
But,
Every new client session that you create, you configure it with the actual remote ip that you want to reach. (And not 127.0.0.1 + specific local port).
In SecureCRT, the way you associate any new client connections via local port , via tunnel,
Is simply select to connect via the firewall (firewall = existing SSH TUNNEL).
In RDM,
You can set a folder of 50 RDP servers which need to connect via tcp port 3389,
To connect via existing SSH session.
But in all your tutorials/examples, it specify to configure each RDP with remote ip as 127.0.0.1
And I don’t want to do that. I don’t want to manage 50 RDP servers, each of them set with different local port, and have their real IP somewhere in the SSH TUNNEL object.
Hope my question is clear enough.
Thanks
Hi,
This looks very nice, but I do not see/understand how to configure the RDP connection to connect through the SOCKS proxy.
Are you able to send us your configuration "Outside of RDM" to perform the RDP connection through Secure CRT.
Best regards,
David Grandolfo
Hi David,
Thank you for your support.
To clarify: I do not have this nice feature for anywhere in relation to RDP! It is working on SecureCRT for SSH connections, and also I was able to test Dynamic HTTP from Chrome Browser through this SecureCRT connection.
To clarify#2, I do not need it to be specific SecureCRT SOCKS proxy.
Let me try to rephrase/start over :-)
Lets assume that I have a remote platform with 10 Windows Servers (i.e. Windows Server 2012) + 10 Ubuntu Servers.
Lets assume that their IP Addressed are :
172.182.70.01
172.182.70.02
172.182.70.03
172.182.70.04
...
172.182.70.20
Lets assume that first 10 IPs are windows Servers (172.182.70.01-172.182.70.10 , and 172.182.70.11-172.182.70.20 are Ubuntu).
And Lets Assume that I have to use SSH Tunnel with IP 202.202.182.182 in order to be able to access the above 20 IPs.
Today,
On Royal TS, I need to create SSH connection to a SSH TUNNEL connection.
On this SSH Tunnel Object,
I MUST configure MANUALLY a local port mapping.
for example:
Source port 30001 will be mapped to windows server IP 172.182.70.01 on port 3389.
Source port 30002 will be mapped to windows server IP 172.182.70.02 on port 3389.
Source port 30003 will be mapped to windows server IP 172.182.70.03 on port 3389.
Source port 30004 will be mapped to windows server IP 172.182.70.04 on port 3389.
Source port 30005 will be mapped to windows server IP 172.182.70.05 on port 3389.
...
Source port 30010 will be mapped to windows server IP 172.182.70.10 on port 3389.
AND all the Ubuntu servers should be:
Source port 30011 will be mapped to windows server IP 172.182.70.11 on port 22.
Source port 30012 will be mapped to windows server IP 172.182.70.12 on port 22.
Source port 30013 will be mapped to windows server IP 172.182.70.13 on port 22.
Source port 30014 will be mapped to windows server IP 172.182.70.14 on port 22.
Source port 30015 will be mapped to windows server IP 172.182.70.15 on port 22.
...
Source port 30020 will be mapped to windows server IP 172.182.70.20 on port 22.
Next,
As Step#2, I need to create a tree with all these 20 servers.
And each of the servers on the tree, MUST be configured to connect toward destination IP 127.0.0.1 and the relevant local mapped port.
e.g.
Server#01 (representing 172.182.70.01) , will be created with remote IP 127.0.0.1 and port 30001
Server#02 (representing 172.182.70.02) , will be created with remote IP 127.0.0.1 and port 30002
Server#03 (representing 172.182.70.03) , will be created with remote IP 127.0.0.1 and port 30003
Server#04 (representing 172.182.70.04) , will be created with remote IP 127.0.0.1 and port 30004
...
Server#20 (representing 172.182.70.20) , will be created with remote IP 127.0.0.1 and port 30020
To summarize:
This type of configuration is complicated :-)
It require me to remember that local port 30007 for example, represent the platform SQL DB.
i.e. The server representation is through specific port and not by the real IP. All servers are configured with 127.0.0.1 ...
And it is hard to manage environment like this....
The point I am trying to make is the following:
Assuming it is currently not supported in RDM,
it would be nice to configure all the servers with their real IP address.
And at the Folder that contains all these 20 servers, specify that they MUST connect via specific SSH Tunnel object.
And by doing this, the RDM will know to perform this local mapping automatically !
e.g.
I will create the 20 objects with the servers real IP address and real ports:
Server#01 (representing 172.182.70.01) , will be created with remote IP 172.182.70.01 and port 3389
Server#02 (representing 172.182.70.02) , will be created with remote IP 172.182.70.02 and port 3389
...
Server#10 (representing 172.182.70.10) , will be created with remote IP 172.182.70.10 and port 3389
Server#11 (representing 172.182.70.11) , will be created with remote IP 172.182.70.11 and port 22
Server#12 (representing 172.182.70.12) , will be created with remote IP 172.182.70.12 and port 22
Server#13 (representing 172.182.70.13) , will be created with remote IP 172.182.70.13 and port 22
...
Server#20 (representing 172.182.70.20) , will be created with remote IP 172.182.70.20 and port 22
And the fact that we specify the folder to go through another existing SSH Object ,
means that RDM will know to perform this local mapping automatically !
Meaning:
- when I will create the RDM built-in SSH-Tunnel object / SSH-Port Forwarding object,
I will only need to configure it with the remote server Credentials and Destination IP address (in this example , 202.202.182.182 ).
- I should not need to specify it with any information about local port mapping and 127.0.0.1 ...
- This way,
the configuration is much more easier , and not complicated like with Royal TS.
Please let me know if this is currently supported ? Or perhaps you can move this to the feature request area ?
Thanks a lot!
Hi,
Wow what an explanation, thanks. I will take all this information and try to test it without RDM and with RDM.
Please let me 2 days to test everything and to come back with a clear answer.
Best regards,
David Grandolfo
I was following this post and I'm also interested in this feature. I also went back to my Royal Tx installation and tried the tunneling there. I'm not sure your statement is correct that you need to create a tunnel object for each connection. In fact you can reuse the tunnel object there for all your connections and it will assign the local ports automatically. So in general, it would be cool if RDM can do the same...