Hi All!

I'm a relative linux noob, and am in need of a bit of help.

I'm trying to set up port forwarding using SSH and Putty (for a windows machine on the work network).

I'm running Fedora 4 with an Apache server and SSH (set up to listen on ports 443 and 22). I've disabled Apache from binding to port 443, and have used iptables to make sure the connection gets through.

Putty is configured to tunnel source port 80 to [linux ip] port 80.

So far, Putty will connect fine to the linux box. After I log in, though, I set IE to use localhost for the proxy on port 80, and I get nothing. No webpages will display at all... Any ideas? The help would be greatly appreciated, as my eyes are getting a bit crossed from reading man pages all day

thanks!!

-Max

PuTTY does not offer tunneling for other applications as far as I know.
It is a SSH Client. You might have to look for another solution.

Port forwarding is usually used if you have a firewall in between you and your destination machine.

IE: You access port 123 on the firewall and get forwarded to port 456 on the destination machine.

It might be helpful to know what you are trying to acheive.

apache isn't a hypertext proxy. if ssh is forwarding your port 80 of your apache to your workstation and you want to see what apache is serving, point your broswer to localhost but don't play with your proxy settings. if you want to forward a proxy to 'browse' from the server IP, use squid instead of apache.

hth,
-b

You can set up putty for tunneling/port forwarding. I use it here for tunneling VNC. For example, I connect my VNC viewer to 127.0.0.1:1 on my Windows box and putty forwards the connection to port 22 on the Linux box and it gets handed over to the VNC server running there.

What are your settings on the Tunnels tab of putty? I just added a local port number to the Source Port text box (for example 5901) and the server address to the Destination text box (for example ahost.adomain.com.au:5901). I left everything else at default settings.

As others here have already pointed out - it's not for proxying though...

for diagnostic purposes you can try to telnet into your forwarded port on your workstation-- that's how to find out what is actually there, for instance to decouple your problem into two cases: either the forwarding doesn't work or you have a browser or browser config problem.

if you see anything (text) you can try GET and POST commands to talk to apache directly.