[ Date Index ] [ Thread Index ] [ <= Previous by date / thread ] [ Next by date / thread => ]
On Sun, 23 Nov 2008, Grant Sewell wrote: > Bill wrote: >>> 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. >>> >> 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 > Hi Bill, > > I'm actually using the Linux PuTTY client. I tried using ssh command at > College, but even when setting up proxy information system-wide, it > still fails to get through it... but I found that the PuTTy client does. > It is very strange. How about this: Use putty to establish a connection and then forward local port 2222 to remote port 22. (So putty will connect to the remote port 445 to login, but forward local 2222 to remote 22). Then run ssh and have ssh tunnel through the tunnel. ssh -p2222 gsewell@localhost -L26:localhost:25 -L143:localhost:143 It will be somwhat sub-optimal in that MTU fragmentation may slow down streamed data, but it ought to still work OK. (but as a bonus the data is doubly encrypted ;-) > I have just bought an "Internet & Email Add-on" to my 3 mobile account, > so I may just stop trying and use my phone instead of the College's > network. :D Well, there is that.. Assuming you can get 3G coverage... Gordon -- 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