Nx
From Wsms
Note: This page should be titled nx (all lowercase). It is Nx due to technical limitations of Mediawiki.
Contents |
nx
nx sets up an X server from one machine to another over a network. It is sort of like vnc. Versions of nx, both the server and the viewer, are available for most operating sytems.
FIXME: This page applies to Fedora 7, setup and configuration for other Linux distributions is somewhat different. The Fedora 7 specific stuff needs to be moved to a sub-page.
nxclient-3.2.0-9 is the latest version at the time of this writing.
tips
You need to generate a key for your server.
/usr/NX/scripts/setup/nxserver --keygen
You need to import a key to the client. You can find the key The key you need is /usr/NX/share/keys/default.id_dsa.key
To restart the server use nxserver --restart. I don't know if you need to be root or not.
You can nx into a server with the same username and password from more than one client computer. Be sure that you set up each client with a different name for the nx session, or the second will take over the first instead of creating a new session. I use names like arthur-harrison and arthur-lincoln for nxing to arthur from harrison and lincoln.
The key combo to toggle fullscreen is Ctrl-Alt-f.
Linux installation and configuration
installation
On Fedora Core 7 install the client with:
[root@ws05 ~]# yum -y install wget ... [root@ws05 ~]# wget http://64.34.161.181/download/2.1.0/Linux/nxclient-2.1.0-17.i386.rpm ... [root@ws05 ~]# yum -y install freenx ... [root@ws05 ~]# yum -y install compat-libstdc++-296.i386 ... [root@ws05 ~]# rpm -ivH nxclient-2.1.0-17.i386.rpm ...
configuration
First, get the key for the server you are going to access:
[ggeller@harrison ~]$ scp arthur:default.id_dsa.key . ggeller@arthur's password: default.id_dsa.key 100% 668 0.7KB/s 00:00
Launch the client:
Use the configuration dialog. Make sure you select "Enable SSL encryption of all traffic" and used the advanced configuration to import the key.
tunnel nx
You can tunnel nx if you have root access on your local machine. You have to have root access because nxclient always wants to authenticate on port 22. So, you listen on port 22 locally and forward it to port 22 remotely through a convenient port. Let's also suppose that you have root access on the remote machine that is going to be the nx server and that you are in a location like a school that blocks outgoing connections on port 22. Here's what you do.
One the server, (re)configure httpd so that it doesn't listen on port 443. Configure sshd so that it listens port 443 in addition to port 22. Make sure port 443 is open in the server's firewall.
[root@harrison ~]# service sshd stop [root@harrison ~]# ssh -f -N -L 22:localhost:22 -p 443 ggeller@myserver.com ...
When you configure nxclient, tell it to go to localhost:22.
Nobody is going to block outgoing connections on port 443. But, they might make you go through a proxy. In that case you might have to set up httptunnel.
see also
vino and vinagre
rdesktop
nomachine.com
20070515a#nx_on_vista
https://help.ubuntu.com/community/FreeNX - install on ubuntu and LinuxMint
nx/Fedora Core 5
nx/Fedora Core 6
Nx/Linux Mint Celena
Nx/Linux Mint Daryna
Nx/CentOS 5
