<?xml version="1.0"?>
<rss version="2.0">
<channel>
<title>DEVOLUTIONS - Remote Desktop Manager - Bug Report - SSH Port Forwarding - Messages</title>
<link>http://forum.devolutions.net/forum/topic399-ssh-port-forwarding.aspx</link>
<description>DEVOLUTIONS - Remote Desktop Manager - Bug Report - SSH Port Forwarding - Messages</description>
<language>en-us</language>
<docs>http://blogs.law.harvard.edu/tech/rss</docs>
<generator>Jitbit AspNetForum</generator>
<pubDate>Sat, 13 Feb 2010 10:31:41 GMT</pubDate>
<lastBuildDate>Sat, 13 Feb 2010 10:31:41 GMT</lastBuildDate>
<item>
<link>http://forum.devolutions.net/forum/topic399-ssh-port-forwarding.aspx</link>
<title>Message from sbonilla</title>
<description><![CDATA[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.<br/><em>edited by sbonilla on 2/13/2010</em>]]></description>
<pubDate>Sat, 13 Feb 2010 10:31:41 GMT</pubDate>
</item>
<item>
<link>http://forum.devolutions.net/forum/topic399-ssh-port-forwarding.aspx</link>
<title>Message from sbonilla</title>
<description><![CDATA[hmm, I'll have to look into the command line session type thing<br/><br/>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.<br/><br/>I'll definitely play with the command line session option, I didn't pay much attention to that...]]></description>
<pubDate>Mon, 14 Dec 2009 17:52:15 GMT</pubDate>
</item>
<item>
<link>http://forum.devolutions.net/forum/topic399-ssh-port-forwarding.aspx</link>
<title>Message from dhervieux</title>
<description><![CDATA[Hi,<br/>  You're right, it seems to be a bug in Putty, maybe you should use Tunnelier with a command line session type ?<br/><br/>David Hervieux<br/>Devolutions inc.]]></description>
<pubDate>Mon, 14 Dec 2009 17:50:03 GMT</pubDate>
</item>
<item>
<link>http://forum.devolutions.net/forum/topic399-ssh-port-forwarding.aspx</link>
<title>Message from sbonilla</title>
<description><![CDATA[NOTE: Seems to only be a bug with PuTTY.<br/><br/>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.<br/><br/>I.E.:<br/>127.0.0.1:50001 --&gt; 192.168.0.1:4899<br/>127.0.0.1:50002 --&gt; 192.168.0.2:4899<br/>...<br/>127.0.0.1:50125 --&gt; 192.168.0.125:4899<br/><br/>etc.etc.<br/><br/>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.<br/>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:<br/><br/><a href="http://the.earth.li/~sgtatham/putty/0.60/htmldoc/Chapter10.html#errors-portfwd-space" target="_blank" rel="nofollow">http://the.earth.li/~sgtatham/putty/0.60/htmldoc/Chapter10.html#errors-portfwd-space</a><br/><br/>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.]]></description>
<pubDate>Mon, 14 Dec 2009 14:18:54 GMT</pubDate>
</item>
</channel>
</rss>
