"William L. (Bill) Barth" wrote:
> Assuming I understand your suggestion, the problem with trying to do
> it that way is that I'm not allowed to connect directly to or open
> ports on the firewall itself. All connections to the ssh port (22) on
> the work firewall are forwarded (transparently to me) to a _random_
> machine on the inside. So there are two ways I see that I can do this
>
> 1. Forward a local port on my home machine to the remote machine on
> which the Xvnc server is running. But I don't see how since I need
> to specify the machine on the _inside_ of a firewall which is (de
> facto) not addressable directly.
Doesn't matter. The forward host is contacted by the server, not the
client, so its reachability from the client is irrelevant. So in your
case where an ssh connection to "work" gets randomly forwarded to
"workN" for some N, you can VNC to "work3" by:
ssh -L 5910:work3:5900 work
and then connect your vncviewer to localhost:0. If you get connected,
say, to "work5", "work5" will happily forward the connection to
"work3".
-- Joe Knapka
---------------------------------------------------------------------
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
---------------------------------------------------------------------
