[FreeNX-kNX] Re: Using NX with VNC

[chris at ccburton.com]

Tim Rice <harleyvrodred at yahoo.com> wrote on 01/04/2011 22:45:47:
[SNIP]
>Node-L <= VPN-A => VNC-Server <= VPN-B => Node-R
[SNIP]
> 
> The Telnet and FTP apps perform well enough but the X Windows 
> Desktop you get on Node-L for Node-R is just too slow to be usable.
>
You don't really tell us enough about your VPNs . . .

If you can't connect directly from "Node-L" to "Node-R" I guess not,
but are you sure ??
but
if you can:-
        ssh "VNC-Server" from "Node-L" (check in case
they've changed the port from 22 to something else)
then
you can try telling ssh to conect a tunnel to "Node-R"
i.e
on "Node-L" try (all on one line)
        ssh -f -N -p ssh-port-on-VNC-Server-default-is-22
        -L 1010:Node-R:ssh-port-on-Node-R-default-is-22
        ssh-user-on-VNC-server at VNC-server 
(NOTE WELL The "Node-R" needs to be resolveable from
"VNC-Server" not "Node-L" )
and
see if it sets up forwarding from port 1010 on "Node-L"
to port 22 (or whatever) on "Node-R"
(test with ssh -p1010 ssh-user-on-Node-R at localhost
assuming sshd is actually running on "Node-R")

If that tunnels through (over the original VPNs) then you can
install FreeNX on "Node-R" andconnect from "Node-L" by
running nxclient and pointing the session at localhost:1010
else
If VPN-A only gives you VNC to "VNC-Server" (probable senario)
then
see if you can install nxclient on "VNC-Server" (guess not)
or
on another machine with with access to "Node-R" via VPN-2
which will allow you to NX half the link anyway.

You may find you need NX end-to-end, even if the links individualy
are quick, because it may well prove to be too slow over both with
a protocol change in the middle.

[SNIP]
> Thanks,
> -Tim
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/freenx-knx/attachments/20110403/84c9b453/attachment.html>