"Todd A. Jacobs" wrote:
>
> In order to get VNC to work over SSH, I need to forward the local
> connection to the remote host instead of the other way around. This seems
> a little counter-intuitive to me, and I was hoping someone could explain
> why it works this way.
>
> Since the VNC server is running on port 5901 on machine foo, why am I not
> forwarding 5901 on foo to 5901 on localhost? Doing so doesn't work (I keep
> making that mistake) but sending localhost:5901 to foo:5901 does the job
> properly.
>
> Please enlighten me.
>
> --
> Todd A. Jacobs
> Senior Network Consultant
It's just like postal forwarding:
"Forwarding X to Y" means "When a connection is made to X, actually
connect to Y instead." The forwarder listens at address X, and delivers
any data it finds there to address Y; similarly it delivers replies at
Y to X. The data path is bi-directional once it is established, but
the critical thing is that the forwarder is *listening for connections*
at X.
When you forward foo:5901 to localhost:5901, the forwarder attempts to
listen for connections at foo:5901 and hook them up to some process
listening at localhost:5901. This attempt is doomed, since the VNC
server is already listening at foo:5901, and there's (probably)
nothing running on localhost:5901.
HTHTIWUIIJCTF*
-- Joe Knapka
* Hope This Helps, Though I Would Understand If It Just Confuses
Things Further
---------------------------------------------------------------------
To unsubscribe, send a message with the line: unsubscribe vnc-list
to [EMAIL PROTECTED]
See also: http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------
