Ok I entered the command 'ssh -R 8080:routerip:80 user@localssh' from the vnc connection on the remote computer, replacing routerip and localssh with their respective IP's. I was prompted to enter the password and then I had to accept the new key etc...
But now I'm logged in.

Was I supposed to look for something?


Many thanks for your help by the way

When you connect using those options, it creates a reverse proxy between your local computer and the address specified after the first colon.

ssh -R 8080:routerip:80 user@localssh

From 'localssh' if you open your webbrowser and connect to 127.0.0.1:8080, ssh will pick up that connection and forward it to 'routerip:80'

(This is so you can reconfigure the port forwarding on the router..)

I found out what router is being used on this LAN. It's a comcast router. Here is the link to the documentation of this router. http://documentation.netgear.com/wnr...5-01/index.htm

We tried to get port22 working by deleting the portforwarding configuration for port22 and then re-creating it. It didn't work.

OK 'ssh -R 8080:router:80 user@localssh' is working and when I go to 127.0.0.1:8080 it takes me to the root directory of the web server.


I'm going through the routers documentation, but I have no idea how to resolve this problem other than what the owner and I did yesterday.

Try forwarding a different external port to port 22 on the ssh server.

Now ssh is working on an alternative port.

Thanks every one for your help.

But what could have broken port22 and how can I fix it?

I have seen some routers not want to forward ports that they use (like a VOIP router that won't forward port 5060)

Does your router accept connections on port 22?

How would I find that out?

Port forwarding has worked previously on port22. Also the router software does not complain when enabling port forwarding on port22.

I've noticed that since changing ssh to use another port, sftp does not work. Even if I define the new port number in the connection settings.

You reconfigure the portforwarding but it didn't work, and you changed it to another port, it worked.

I guess it means there are some other service run on your router which used port 22.
try netstat command on the router and post the result.
It would be better if you post the portfowarding rule too.