[Gllug] VNC problem

[Mark Hazell]

On Mon, 7 Jul 2003 20:51:50 +0100 Doug typed:

> On Mon 07 Jul Simon Morris wrote:
> > I often connect to my machine at work from home using VNC. Both
> > machines run RH 9.0
> > 
> > Once connected to work I then get another VNC session onto our
> > Windows servers to do some out-of-hours stuff (Like rebooting --
> > who'd have thought it!!)
> 
> Why do you VNC to the redhat system, rather than going straight to the
> Windows box?
> 
> If it's because of NAT making the Windows box unaddressable, or
> similar firewall type issues, you might find ssh tunneling useful. 
> vncviewer supports this with the "-via" switch, although you can
> create them manually using ssh if you'd rather, using the -L and -R
> switches.
> 
> With vncviewer, you can just:
> 
> $ vncviewer -via gateway-system windows-system

It would be interesting to see if this is quicker than X-forwarding
vncviewer (running on the work RH9 machine), tunnelled over SSH, which
is my preferred route (as it then gives you the opportunity to use other
apps on the work RH9 machine as well as vncviewer).

I do this all the time, it's awesome :-)

Cheers,
M.

-- 
"All that was needed was to parse the cat root slash dev etcetera file
for eth0 and pugle the forward identity-locking rehooliginator and
symlink it to the libgc perl humongisooler module after a kernel
decompile and basic repatch update." - theregister.co.uk


-- 
Gllug mailing list  -  Gllug at linux.co.uk
http://list.ftech.net/mailman/listinfo/gllug