I'm trying to allow ssh access from a remote RHEL server to a local RHEL box via Win/Putty gateway. Basically, I'd like to be able to do 'ssh localhost -p 512' on a remote server so that it would connect to the RHEL server in the local network. The local network is beyond a firewall so I can connect from my Win PC to the remote server with Putty/ssh but not vice verse.

LclSrv----WinXP/Putty-----||-----RmtSrv

So, I've added the following tunneling settings to the current RmtSrv session in Putty (actually I use Kitty but doesn't matter):

R512 LclSrv:22

I expect that this would create a process on the remote server that listens port 512 and transfers the connections to a local network/LclSrv port 22.

After pressing start button, Putty opens a regular ssh terminal session successfully but nothing happens. (options show active port forwarding). I've checked with netstat -l that port 512 is not listening on RmtSrv. ssh on this port returns 'connection refused'. What am I doing wrong? May be there is something in the sshd_config that needs to be changed in order to allow the tunneling? Could it be user privileges on RmtSrv that prevents me from creating tunnels? I have sudo btw.

Cheers, Vlad.


Question: What does it mean to interpret the Bible literally?
Answer: Those who claim to interpret scriptures "literally" will otherwise propose this means to "accept the plain meaning" of the text, rather than seeking a symbolic, allegoric, or otherwise subtle hidden meaning.

Of course the "plain meaning" itself can be subjective, causing differences in interpretation based on the "literal" approach.