SSH Port Forwarding
NOTE: Seems to only be a bug with PuTTY.
When trying to connect to Radmin clients behind a server running SSH, in the past I would use Tunnelier (great SSH client BTW) to forward ports to the appropriate machines.
I.E.:
127.0.0.1:50001 --> 192.168.0.1:4899
127.0.0.1:50002 --> 192.168.0.2:4899
...
127.0.0.1:50125 --> 192.168.0.125:4899
etc.etc.
So, I created these forwards for the whole subnet of 192.168.0.1-255, using ports 50001-50255, and when trying to connect through PuTTY with Remote Desktop Manager, I would just get a connection failed message.
I started removing port forwarding rules until I had about 5, which resulted in a "Out of space for port forwardings" message with PuTTY. I googled that and found this:
http://the.earth.li/~sgtatham/putty/0.60/htmldoc/Chapter10.html#errors-portfwd-space
This will be quite a hindrance for me. Hopefully we will see an update for that from PuTTY in the near future, although it looks like this hasn't been touched since 2004.
All Comments (3)
Hi,
You're right, it seems to be a bug in Putty, maybe you should use Tunnelier with a command line session type ?
David Hervieux
Devolutions inc.
David Hervieux
hmm, I'll have to look into the command line session type thing
another option for me is to break apart the sessions... forwarding ~40 ports at a time and having my radmin connections point to the appropriate session. For the sake of end-user simplicity, this might be a better way to go for me.
I'll definitely play with the command line session option, I didn't pay much attention to that...
So far my solution to this is as I mentioned, to add multiple PuTTY SSH connections, sometimes 3 or 4, for a location that needs more than 39 port forwards. It seems to be fine. I was weary of creating these connections but once I got the hang of importing a host list with a template and exporting to .rdm and editing it as an .xml file using various methods, its been a breeze.
edited by sbonilla on 2/13/2010
