View Full Version : Port Forwarding public port 81 to 9000

Richard Grant
2005-01-29, 14:57
> -----Original Message-----
> From: discuss-bounces (AT) lists (DOT) slimdevices.com
> [mailto:discuss-bounces (AT) lists (DOT) slimdevices.com]On Behalf Of Philip Meyer
> Sent: Saturday, January 29, 2005 11:56 AM
> To: Slim Devices Discussion
> Subject: [slim] Port Forwarding public port 81 to 9000
> > I've configured everything on the server, so I'll give it a shot
> > tomorrow from work.
> >
> I'm pretty sure my home server is working okay, but I have
> problems getting puTTY to work through my work's proxy (at least
> I think that is what the problem is).

mmm.. proxy server complicates things a bit. Might need to do ssh over http.

> I have copied my proxy settings from Internet Explorer and put
> them in the Connection->Proxy settings section of puTTY. HTTP,
> proxy hostname, port 80, username and password. However, I get a
> connection error. I think the proxy doesn't support CONNECT in
> the standard way. I think it requires some special USER command

Probably CONNECT disabled.. try the USER authentication and use HTTP in
PuTTY or switch to port 443.

> instead, like "USER user@server Proxyuser". Does this mean it is
> not going to be possible? I thought I could try the telnet
> setting, so I could put a different command in, but haven't had
> any success yet - puTTY window seems to dissapear without any
> error or info written to the log.

Try the HTTP setting with an alternate telnet command.. see section 4.14.5:
Specifying the Telnet proxy command in PuTTY help. I might also try changing
the PuTTY connection to use HTTPS port (443) instead of port 22. Change your
home server to listen on the same port, or adjust your firewall to port
forward 443 traffic to your local machine running OpenSSH.

Not sure what needs to be done to OpenSSH on the other side.. I have
infrequently used private IP proxy servers, but if you have a full cygwin
install on the server machine.. there seem to be a few straightforward
options. This site provides a nice summary:


Sorry.. missed references to a proxy server in your original post. Also, you
should be aware that the client end point of the ssh connections seems to
have gone to considerable lengths to prevent certain forms of traffic.
Circumventing these restrictions may prove to have unfortunate consequences.