Freenx Installation

Client installation

Supported Platforms

1.1 Windows

• Windows 2000/XP/2003/Vista

1.2 Linux i386

• Red Hat Enterprise Linux 4/5

• SuSe 10/10.1/10.2/Enterprise 10

• Mandriva 10.1/2005/2006/2007
• Fedora Core 3/4/5/6
• Fedora 7
• Debian GNU/Linux 4.0 Etch
• Ubuntu 5.10 Breezy Badger/6.05 Dapper Drake/6.10 Edgy Eft/7.04 Feisty Fawn
• Xandros 4.1

IMPORTANT

NoMachine's policy is to provide packages for the most recent versions of Linux which you can see listed above or on the download page: http://www.nomachine.com/download

Users of older Linux versions are pointed to a specific download page for the appropriate NX packages. Please note that, at the time of an NX release, it is possible that packages for the following older Linux distributions are slightly delayed:

• RedHat 7.2/7.3/8.0/9.0

• SuSE Linux 7.2/7.3/8.0/8.1/8.2/9.0
• Mandriva Linux 9.0/9.1/9.2/10.0
• Fedora Core 1/2
• Debian GNU/Linux 3.0 Woody/ 3.1 Sarge
• Ubuntu 5.04 Hoary
• Xandros 3.0

Linux x86_64

• Red Hat Enterprise Linux 4/5

• SuSe 10/10.1/10.2/Enterprise 10

• Mandriva 10.1/2005/2006/2007
• Fedora Core 3/4/5/6
• Fedora 7
• Debian GNU/Linux 4.0 Etch
• Ubuntu 5.10 Breezy Badger/6.05 Dapper Drake/6.10 Edgy Eft/7.04 Feisty Fawn
• Xandros 4.1

Mac OS X PPC

• 10.3
• 10.4

Mac OS X i386

• 10.3
• 10.4

Solaris SPARC

• 8/9/10

The list of the supported platforms and operating systems may be updated from time to time, so please refer to the download page to get the latest information:

2. NX Client Installation Instructions for Windows Platforms

2.1 Installing NX Client Double-click on the icon of the NX Client executable file you have downloaded from the NoMachine Web site: the NX Setup Wizard will take you through the installation.

Step 1

Select where to install NX Client and confirm by clicking on the Next button.

Step 2

• The Setup Wizard will allow you to create the program shortcut in the Start Menu by default or in any folder of your choice.

To proceed, click on the Next button as usual.

Step 3

A further dialog will enable you to create an additional shortcut to the application on your desktop.

Confirm according to your personal preference.

Step 4

• The final dialog will ask you to confirm the installation of NX Client on your machine.
• Exit the installation If you want to exit the installation, please click on the Cancel button and click on Yes.

2.2 NX Client Configuration:

• After the Installation, it will open an prompt window for nxclient configuration, if not, try find shortcut for access "NX Client for Windows"

• In NX Connection Wizard window, click on next then lead to "Session" window

• In Session box, type in the unique name of the server going to access to plus the terminal name of users,(e.g. Damro-lanka2, this is for user lanka2 to Damro server)

  • in Host box, type in the server domain name or ip address which ever is accessible, in the Port box, leave 22 as a default value

  • nothing very interesting on Selection of internet connection, so leave it for default selection, then click on next

• In Desktop window, keep the Unix drop-down list choose Unix as default, and in KDE drop-down list choose Custom, then click on Settings..., then open a new Custom - Settings pop-up window

  • In Application section, choose either

    • "Run the default X client..." or

    • "Run the following command", in the filed below type in the command to be run on remote server, e.g. very possibly fvwm for our scenario

  • In Options section, choose new virtual desktop for the reason of display requirement.

  • After check the configuration of above, click on ok then go back to main window, and then click on next

• In Configuration completed window, check the two check-boxes, and click on Finish, then another main configuration window will pop-up.

• In the top of the window, there are tabs named as General, Advanced, Services, Environment, About, focus on General tab only at this stage.

  • In the Server section, check Remember my password, then check the Key... button, in the pop-up window Key Management, the DSA key is the private key of the server key pair on the remote server, need to be copied from remote server, click on Import and locate the key then click Save

  • Back to the General tab, in Display section in the drop-down list select whatever display mode fit to client side, then simple click on Save and Ok

• In small Login window

  • Login

  • Password

  • Session

  • make sure they are correct corresponding to each other, then click on Ok, the session will start connecting.

• Please find all related files and keys on our Website http://www.crecom.com.au/freenx/

  • In directory config-files contains the configuration files for client "Damro-Sri-Lanka" and "Frathouse", just download the related files to your local folders, and/or create shortcut on desktop for them, then click on to use it.

  • In directory client-keys contains the corresponding private keys for the server to be connected, please refer to in only when create new client access to server.

Server FreeNX Installation

• Prerequisite: sshd must be running as a daemon on port 22 (This can be modified later.)

Setup FreeNX on Fedora Core 5 or later

1. Make sure you are up-to-date
   • #yum update
2. Install FreeNX and all dependencies
   • #yum install freenx

Setup FreeNX on FC4 or earlier

1. Make sure you are up-to-date
   • #yum update
2. Install NX rpm dependencies
   • #yum install expect nc
3. Grab a Freenx package
   1. Use this package for FC2, FC3, FC4, and xorg based distributions

      • #wget http://fedoranews.org/contributors/rick_stout/freenx/freenx-0.4.4-2.fdr.0.noarch.rpm

   2. Use this package for FC1, RH9, RHEL3 or XFree86 based distributions

      • #wget http://fedoranews.org/contributors/rick_stout/freenx/freenx-0.4.4-2.rh.0.noarch.rpm

4. Next, grab an nx package
   1. This package was built on FC4

      • #wget http://fedoranews.org/contributors/rick_stout/freenx/nx-1.5.0-4.FC4.1.i386.rpm

   2. This package was built on FC3

      • #wget http://fedoranews.org/contributors/rick_stout/freenx/nx-1.5.0-4.FC3.1.i386.rpm

   3. This package was built on FC2

      • #wget http://fedoranews.org/contributors/rick_stout/freenx/nx-1.5.0-4.FC2.1.i386.rpm

   4. Use this package if you are using FC1, RH9, RHEL3 or a Redhat compatible distribution using XFree86

      • #wget http://fedoranews.org/contributors/rick_stout/freenx/nx-1.5.0-4.FC1.1.i386.rpm

5. Install the RPM's
   1. #rpm -Uvh nx-1.5.0-4.FC4.1.i386.rpm
   2. #rpm -Uvh freenx-0.4.4-2.fdr.0.src.rpm

Configuration after Installation

1. Since package installation successful, need to setup nx for FreeNX running

   • set PATH including /usr/libexec/nx, in order that file nxloadconfig is searchable during setup

   • locate nxsetup file, and run it as root

     • #/PATH/TO/nxsetup
2. Configuration files location:

   • /etc/nxserver/

     node.conf.sample

     passwords.orig

     passwords

     server.id_dsa.pub.key

     client.id_dsa.key

     users.id_dsa.pub

     users.id_dsa

   • For FreeNX versions >=0.5.0 you might need to edit the file /etc/nxserver/node.conf

   • copy node.conf configuration file from sample

     • #cp -p node.conf.sample node.conf

   • Then edit file node.conf correspondingly, comment out the following lines, and edit similar as shown:

     1. DISPLAY_BASE=4000
     2. SESSION_LIMIT=200
     3. SESSION_USER_LIMIT=200
     4. DISPLAY_LIMIT=200
     5. NX_LOG_LEVEL=6
     6. NX_LOGFILE=/var/log/nx/nxserver.log
     7. SESSION_LOG_CLEAN=1
     8. USER_X_STARTUP_SCRIPT=.Xclients

3. Every time after edit configuration file node.conf, restart nxserver:

   • #nxserver --restart

4. Before nxclient is able to connect with nxserver, need to copy the PRIVATE KEY to client side for ssh authentication purpose.

   • The file is located at /etc/nxserver/client.id_dsa.key

Further details of freenx instructions will be updated shortly.