[ Date Index ] [ Thread Index ] [ <= Previous by date / thread ] [ Next by date / thread => ]
> That's just it... it doesn't. Right now (as in *now*) I am at my > girlfriend's house using my ssh command-line (as in the first email) to > forward local:26 to remote:25, and it works wonderfully. It is *only* > when I use PuTTY to do so that it fails, and yet PuTTY forwards 143 > flawlessly. Essentially, the remote end (ie the server) shouldn't be > aware that I'm using :26 on the laptop as all the traffic it sees will > be received on :25, as per a normal connection. > > Grant. > > So as you say, it must be a putty problem if openssh can handle everything just fine. If putty is necessary because you're looking for a windows solution, is it worth looking at cygwin + openssh Bill -- The Mailing List for the Devon & Cornwall LUG http://mailman.dclug.org.uk/listinfo/list FAQ: http://www.dcglug.org.uk/linux_adm/list-faq.html