Putty remote port forwarding

Nefarious · 20 Jun 2017 at 11:55

I need to connect to someone behind a firewall. I'm trying to setup remote port forwarding so that I can access his computer through TightVNC

What's I've tried to do is to set remote portwarding

R 5905:localhost:5900

Which I thought would mean that on my linux server I'd just use tigervnc to attach to 127.0.0.1:5905

I've edited the sshd_config to 'allowagentforwarding yes' and 'gateway ports yes'

Help??

memyselfandi · 20 Jun 2017 at 12:23

Wouldn't that allow the remote system to use 5905 to access your system on 5900?

Take a look at: https://www.akadia.com/services/ssh_putty.html

edit: i.e. don't you need L 5905 localhost 5900

Connect to port 5905 locally
--- ssh tunnel ---->
traffic connects to port 5900 on the localhost at the other end

Nefarious · 20 Jun 2017 at 12:40

No, L5905:localhost:5900 would change the local port 5905 (on the computer running putty) to viewing its own 5900, L5905:badgerfaces.com:5900 would change the local port to viewing 5900 on badgerfaces.com

R5905 changes the remote computer (say I was sshing into badgerfaces.com) into having their 5905 port connect to 5900

Rather than using a server to allow me access behind a NAT, I am trying to get putty to present itself over NAT if that makes sense

Steveocee · 20 Jun 2017 at 12:43

Ive always used the following from my Ubuntu desktop when SSH tunneling, I've ammended it a bit to try and make it closer to what you need. This forwards the localhost port 5905 to the remote 5900;
ssh [email protected] -L5905:remote.lan.ip.here:5900

Nefarious · 20 Jun 2017 at 13:59

Ah, thanks for your response, but I've literally just managed to get it to work.

I eventually abandoned the putty menu and went straight to plink so I could get a slightly more verbose output.

For anyone interested, the eventual command I used was like this:

plink.exe -v -ssh -R *:7402:computername:5900 badgerfaces.com

for some reason, you HAVE to put your windows computer name and not simply 127.0.0.1 or localhost. I assume this may be a windows feature to prevent loopback?