FreeNX on Ubuntu & CentOS

Fairly simple stuff.

When prompted about the key while running nxsetup, you should select Y and install your own key all around unless you want an unsecure connection.


Ubuntu:

1. sudo add-apt-repository ppa:freenx-team
2. sudo apt-get update
3. sudo aptitude install freenx qtnx
4. wget https://bugs.launchpad.net/freenx-server/+bug/576359/+attachment/1378450/+files/nxsetup.tar.gz
5. tar -zxf nxsetup.tar.gz && sudo mv nxsetup /usr/lib/nx/nxsetup && sudo chown root:root /usr/lib/nx/nxsetup && sudo /usr/lib/nx/nxsetup --install
6. cd /etc/nxserver
7. cp node.conf.sample node.conf (if necessary, see below)

CentOS:
You need the Extra Repos or the RPMS for expect libnxcl nx qt4 freenx

Expect & QT4 are in the normal distribution and should be already installed in most cases. Latest FreeNX and libnxcl from the Extra repos are:

• freenx-0.7.3-5.el5.centos.x86_64.rpm
• nx-3.4.0-3.el5.centos.x86_64.rpm
• libnxcl-0.9.0-3.el5.centos.x86_64.rpm

1. yum install qtnx freenx
2. nxsetup --install
3. cd /etc/nxserver
4. cp node.conf.sample node.conf (if necessary, see below)

Windows
download client from http://www.nomachine.com/download-client-windows.php

Apparently the nomachine client has problems with the DISPLAY_BASE.
If you connect to Server A and then Server B, it fails to open a port. Suprisingly, this works perfectly fine on qtnx client without any changes. For servers being accessed with Windows, edit /etc/freenx-server/node.conf and modify DISPLAY_BASE to have a unique value plus an offset for possible multiple connections