Mailing List Archive

PuTTY uses a different command line syntax and case is important:
http://the.earth.li/~sgtatham/putty/0.60/htmldoc/Chapter3.html#using-gen
eral-opts


Mark Lavi
Senior Web Producer

sgi

46600 Landing Parkway
Fremont, CA 94538
(510) 933-5234 direct
mlavi@sgi.com
www.sgi.com


-----Original Message-----
From: listbounce@securityfocus.com [mailto:listbounce@securityfocus.com]
On Behalf Of Al Grant
Sent: Monday, December 27, 2010 2:04 AM
To: secureshell@securityfocus.com
Subject: Putty; Win7; IE8

Hi All,

I REALLY hope someone here can help me. I have been trying to setup a
SSH tunnel so that when I surf the net on my laptop I can SSH into my
Ubuntu box at home and go through that for web page traffic.

Now I tried to connect to Ubuntu@home from laptop running Win7 with:

putty -ssh my.dyndns.org -l username -P 443 -D 8080 -v

and the connection establishes just fine, but when I surf to
whatsmyip.org I get a different WAN IP to my Ubuntu WAN IP. Weird, so
after a lot or trying different things (IE7, Chrome etc) I rebooted that
same laptop into Ubuntu as well and issued the exact same command but
not using putty

ssh my.dyndns.org -l username -P 443 -D 8080 -v

Now it works like a charm, so I am thinking its something specific to
Win7 or Putty. But I am at the limit of my trouble shooting. Can someone
please help.

Apparently there are some logs I can attach but not sure if server side
or client?

Also I am thinking tcpdump might help but I don't know enough about it
to use it.

Any and all help gratefully accepted!

TIA

-AL

Hi,

> I REALLY hope someone here can help me. I have been trying to setup a
> SSH tunnel so that when I surf the net on my laptop I can SSH into my
> Ubuntu box at home and go through that for web page traffic.

I do the same thing when I use unsecured WiFi networks like at Maccas.

Perhaps instead of using putty, if it's for tunnel purposes you could
use plink instead? Its arguments are much closer to openssh's anyway...

plink -2 -C -N -D SOCKSPORT -v -p PORTNUM username@host.example.com

... where SOCKSPORT and PORTNUM match your config.

Also in your browser, assuming firefox, tell it to use the remote end
for DNS queries, not your local DNS.

Eg. In about:config set network.proxy.socks_remote_dns = true

Remember that -D switch means SOCKS not an HTTP proxy (only SOCKS
proxy field in browser config should be set) and make sure nothing else
is already using 8080 on your machine.

Also make sure that your browser IE etc. is not set to automatically
detect proxies either (explicitly disable that option if it has it).

I use 10801 myself for SOCKS controlled SSH tunnels.

Also, I like to explicitly say 127.0.0.1 and not "localhost" when
specifying in browser config - weird experiences over the years with
various programs seeing "localhost" and assuming some socket magic and
not TCP link.