putty "time out error" with ssh winxp->suse10.2

[ninjaprawn]

i think ive configured putty right in winxp, a friend in work told me the exact settings to go a win xp box, but those settings arent working to suse! ive changed translation to utf-8, and made it use version 2only! putty does nothing for 4 mins, then gives a "proxy error: 504 time out" i am going thru a proxy on port 8080 which is fixed!

[ninjaprawn]

i brought up puttys log file, it gives;-

2007-04-20 17:05:41 Looking up host "77.xx.xx.236"
2007-04-20 17:05:41 Connecting to 193.xx.xxx.20 port 8080
2007-04-20 17:06:50 Proxy error: 504 Gateway Time-Out

the first ip is mine! the 2nd, i have no idea where it is

[SuSEholic]

2007-04-20 17:06:50 Proxy error: 504 Gateway Time-Out

It seems the errors cause because you're XP machine can't reach the gateway and/or the SuSE machine.

The SuSE machine, is it "inside" your building or at the internet?

My guess is, probably you have a non-working gateway.
Trying ping-ing the SuSE machine.

[ninjaprawn]

yeah, my suse box is just on a normal cable internet connection, but the xp box is behind a company proxy, so have to tunnel thru it! would i be adle to ping the suse box, as surely the firewall would block ping requests??

thanks

[SuSEholic]

but the xp box is behind a company proxy

I never used proxy before , but could the proxy server have some settting to open or at least to see whether the ssh port (usually port 22) is blocked or not?
And for the SuSE machine, you have to make sure that the firewall opened the ssh port (22) for the interface you're connecting from.
Usually SuSE blocked the ssh port for interface belong to "External Zone", you can configure it with YaST.

[ninjaprawn]

yeah, my proxy blocks all traffic but port 80 and 443! so i changed my sshd_config file to use port 443, and in my suse firewall, i have ssh as an allowed service. so iset putty to go from 8080 in my xp box, to the proxy on port 8080, then as with secure sites, it leaves on port 443 ton port 443 on my suse box, which has ssh enabled in the firewall! but for some reason, the proxy times out, and gives 504 bad gateway!!