Knowledge Base
Searching in : Document
ID: DT12I00006
Version: NX 3.5
Added on: 2007-08-14
Last Update: 2015-11-05
Print this article

NX Node Installation Instructions (v. 3.5.0)

Table of Contents

1. NX Node Installation Instructions
1

1.1. Supported Platforms
2


1.2. Required Libraries for Installing NX Node on Linux
3

1.3. How to Obtain the Required Libraries for Your Linux Distribution 3
1.4. Prerequisites 3

2. NX Node Installation Instructions for Linux Platforms
4


2.1. List of Available NX Node Packages
4


2.2. Installing the NX Node RPM Package
4


2.3. Updating the NX Node Installation from RPM Package
4


2.4. Removing the NX Node Installation from RPM Package
6


2.5. Installing the NX Node DEB Package
6


2.6. Updating the NX Node Installation from DEB Package
6

2.7. Removing the NX Node Installation from DEB Package
8

2.8. Installing the NX Node Compressed TAR Package
8

2.9. Updating the NX Node Installation from Compressed TAR Package
8

2.10. Removing the NX Node Installation from Compressed TAR Package

9

3. NX Node Installation Instructions for Solaris Platforms

10

3.1 Installing the NX Node

10

3.2. Updating the NX Node

10

3.3. Removing the NX Node

11



 

1. NX Node Installation Instructions

Welcome to the NX Node installation guide. Below you will find some hints about the NX Node packages and step-by-step instructions on how to install, update or remove the node on your Operating System. You can download the latest available version of the package suitable for your O.S. at:

http://www.nomachine.com/download

In the following document, X.Y.Z-W indicates the version of the package you are going to install, e.g. nxnode-X.Y.Z-W.i386.rpm.

 

IMPORTANT

  • If you want to upgrade from version 1.5 to 3.x or higher, it is highly recommended you uninstall your previous NX Installation and proceed with the installation of NX Node and NX Server from scratch.
  • If you want to upgrade from version 2.x to 3.x or higher, you will need to force replacement of the HiRes.so library. This library is now shipped by the NX Node 3.x package, while it was provided by the NX Server package until version 2.x. This involves only RPM and DEB installations.
  • You may install, update and remove packages by using the sudo utility. If you don't have the sudo utility installed, log on as superuser ("root") and run the commands without sudo. If you don't have access to your machine as root user, please contact your Systems Administrator.

 

1.1. Supported Platforms

The supported platforms are:

Linux i386

  • Red Hat Enterprise Linux 4/5
  • SLED 10.x/11.x
  • SLES 10/11
  • Open SUSE 10.x/11.x/12.x
  • Mandriva 10.1/2005/2006/2007/2008/2009/2010/2011
  • Fedora Core 3/4/5/6
  • Fedora 7/8/9/10/11/12/13/14/15/16
  • Debian GNU/Linux 4.0 Etch/5.0 Lenny/6.0 Squeeze
  • Ubuntu 5.10 Breezy Badger/6.06 Dapper Drake/6.10 Edgy Eft/7.04 Feisty Fawn/7.10 Gutsy Gibbon/8.04 Hardy Heron/8.10 Intrepid Ibex/9.04 Jaunty Jackalope/9.10 Karmic Koala/10.4 Lucid Lynx/10.10 Maverick Meerkat/11.04 Natty Narwhal/11.10 Oneiric Ocelot
  • Xandros Desktop 4.1/Xandros Server 2.0

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/RHEL 3.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
  • SLED 10.x/11.x
  • SLES 10/11
  • Open SUSE 10.x/11.x/12.x
  • Mandriva 10.1/2005/2006/2007/2008/2009/2010/2011
  • Fedora Core 3/4/5/6
  • Fedora 7/8/9/10/11/12/13/14/15/16
  • Debian GNU/Linux 4.0 Etch/5.0 Lenny/6.0 Squeeze
  • Ubuntu 5.10 Breezy Badger/6.06 Dapper Drake/6.10 Edgy Eft/7.04 Feisty Fawn/7.10 Gutsy Gibbon/8.04 Hardy Heron/8.10 Intrepid Ibex/9.04 Jaunty Jackalope/9.10 Karmic Koala/10.4 Lucid Lynx/10.10 Maverick Meerkat/11.04 Natty Narwhal/11.10 Oneiric Ocelot
  • Xandros Desktop 4.1/Xandros Server 2.0

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:

http://www.nomachine.com/download

1.2 Required Libraries for Installing NX Node on Linux

The NX Node packages ship their own (updated) version of most of the required libraries, which link with GLIBC dynamically. This kind of packaging solves the problem of offering a package that works everywhere, especially on older distributions, but one that is small enough to be manageable.

These are the libraries required on the system to install the NX Node:

- libXpm.so.4
- libc.so.6(GLIBC_2.2.3)
- libnsl.so.1(GLIBC_2.0)

1.3 How to Obtain the Required Libraries for Your Linux Distribution

To find any required library missing on your O.S., please check if the installation CD from your vendor provides it, or refer to the official Web site of your distribution.

1.4 Prerequisites

Installation of the NX Client package is a prerequisite for installing NX Node. To install NX Client, please follow the instructions reported in the NX Client Installation Instructions:

NX Client Installation Instructions

 

2. NX Node Installation Instructions for Linux Platforms

You may install, update and remove the package by using the sudo utility. If you don't have the sudo utility installed, log on as superuser ("root") and run the commands without sudo. Alternatively, for RPM and DEB packages, you can use the graphical package manager provided by your Linux distribution.

2.1 List of Available NX Node Packages

The following NX Node packages are available:

  • RPM, DEB and Compressed TAR for 32bit architecture
  • RPM, DEB and Compressed TAR for 64bit architecture
  • RPM, DEB and Compressed TAR for 32bit architecture for earlier Linux versions

Please note that NX Node package for 32bit architecture for earlier Linux versions works correctly on 64bit hardware, for example with CPUs based on the AMD64 chipset reference design, as long as the Operating System offers support for 32bit applications.

2.2 Installing the NX Node RPM Package

Open an xterm terminal or similar, move to the directory where you have downloaded the package from the NoMachine Web site and install the package using the RPM utility:

$ sudo rpm -ivh nxnode-X.Y.Z-W.i386.rpm

2.3 Updating the NX Node Installation from RPM Package

It is highly recommended you disable access to new NX sessions and terminate all running sessions before proceeding with the upgrade of the node.

To disable access to new NX sessions, open an xterm or similar and run the following command. Please note that this will not affect users' ability to login to the system by other means (f.e. ssh or telnet):

$ sudo /usr/NX/bin/nxserver --stop

You might want to issue a warning to all connected users to inform them of the operation. Run:

$ sudo /usr/NX/bin/nxserver --broadcast "Your message here"

Then, after the warning, terminate all the running sessions:

$ sudo /usr/NX/bin/nxserver --shutdown

If the load balancing feature is enabled on your NX server, you can also proceed with the upgrade of individual node(s) on remote machines and forbid starting new NX sessions on the specified nodes until the operation is completed. By running:

$ sudo /usr/NX/bin/nxserver --stop NODELIST

You can specify the list of nodes you want to disable, for example:

$ sudo /usr/NX/bin/nxserver --stop 111.222.333.xxx:22 111.222.333.yyy:22

 

Then proceed with the upgrade instructions provided below and, after the operation is completed, enable access to the node(s) by running:

$ sudo /usr/NX/bin/nxserver --start NODELIST

 

For example:

$ sudo /usr/NX/bin/nxserver --start 111.222.333.xxx:22 111.222.333.yyy:22

Before upgrading the installation, make a backup of your current NX installation and protect sensitive information that may be present inside the TAR archive by making the backup readable only by the 'root' user:

$ sudo tar cvzf /root/nx-BACKUP.tar.gz /usr/NX
$ sudo chmod 0600 /root/nx-BACKUP.tar.gz

Next move to the directory where you have downloaded the package from the NoMachine Web site and run:

$ sudo rpm -Uvh nxnode-X.Y.Z-W.i386.rpm

 

IMPORTANT

Upgrading NX Node 2.x to 3.x from RPM package
You need to run the update with the --replacefiles option which installs the package. This will replace files from other packages already installed:

[user@machine]$ sudo rpm -Uvh --replacefiles nxnode-3.0.0-xx.i386.rpm

2.4 Removing the NX Node Installation from RPM Package

The rpm utility will fail if NX Server is installed. First uninstall NX Server, then proceed with the uninstall of the NX Node. To uninstall the server, please follow the instructions reported in the NX Server Installation Instructions available at:

https://www.nomachine.com/DT12I00007

Open an xterm terminal or similar and uninstall the package using the rpm utility:

$ sudo rpm -e nxnode

2.5 Installing the NX Node DEB Package

Open an xterm terminal or similar, move to the directory where you have downloaded the package from the NoMachine Web site and install the package using the dpkg utility:

$ sudo dpkg -i nxnode_X.Y.Z-W_i386.deb

2.6 Updating the NX Node Installation from DEB Package

It is highly recommended you disable access to new NX sessions and terminate all running sessions before proceeding with the upgrade of the node.

To disable access to new NX sessions, open an xterm or similar and run the following command. Please note that this will not affect users' ability to login to the system by other means (f.e. ssh or telnet):

$ sudo /usr/NX/bin/nxserver --stop

You might want to issue a warning to all connected users to inform them of the operation. Run:

$ sudo /usr/NX/bin/nxserver --broadcast "Your message here"

Then, after the warning, terminate all the running sessions:

$ sudo /usr/NX/bin/nxserver --shutdown

If the load balancing feature is enabled on your NX server, you can also proceed with the upgrade of individual node(s) on remote machines and forbid starting new NX sessions on the specified nodes until the operation is completed. By running:

$ sudo /usr/NX/bin/nxserver --stop NODELIST

you can specify the list of the nodes you want to disable, for example:

$ sudo /usr/NX/bin/nxserver --stop 111.222.333.xxx:22 111.222.333.yyy:22

Then proceed with the upgrade instructions provided below and, after the operation is complete, enable access to the node(s) by running:

$ sudo /usr/NX/bin/nxserver --start NODELIST

For example:

$ sudo /usr/NX/bin/nxserver --start 111.222.333.xxx:22 111.222.333.yyy:22

Before upgrading the installation, make a backup of your current NX installation and protect sensitive information that may be present inside the TAR archive by making the backup readable only by the 'root' user:

$ sudo tar cvzf /root/nx-BACKUP.tar.gz /usr/NX
$ sudo chmod 0600 /root/nx-BACKUP.tar.gz

Next move to the directory where you have downloaded the package from the NoMachine Web site and run:

$ sudo dpkg -i nxnode_X.Y.Z-W_i386.deb

The dpkg utility will automatically uninstall the old version present on the system and install the new one.

IMPORTANT

Upgrading NX Node 2.x to 3.x from DEB package
You need to run the update with the --force-overwrite option to overwrite a file from one package with another:

[user@machine]$ sudo dpkg -i --force-overwrite nxnode_3.0.0-xx_i386.deb

2.7 Removing the NX Node Installation from DEB Package

The dpkg utility will fail if NX Server is installed. First uninstall NX Server, then proceed with the uninstall of the NX Node package. To uninstall the server, please follow the instructions reported in the NX Server Installation Instructions available at:

https://www.nomachine.com/DT12I00007

 

Open an xterm terminal or similar and run:

$ sudo dpkg -r nxnode

2.8 Installing the NX Node Compressed TAR Package

Open an xterm terminal or similar. You should have downloaded the tar.gz package to the /usr directory. If not, move the package to the /usr directory. For example:

$ sudo mv nxnode-X.Y.Z-W.i386.tar.gz /usr

Then extract the archive:

$ cd /usr
$ sudo tar xvzf nxnode-X.Y.Z-W.i386.tar.gz

and run the setup script for nxnode:

$ sudo /usr/NX/scripts/setup/nxnode --install

 

2.9 Updating the NX Node Installation from Compressed TAR Package

It is highly recommended you disable access to new NX sessions and terminate all running sessions before proceeding with the upgrade of the node.

To disable access to new NX sessions, open an xterm or similar and run the following command. Please note that this will not affect users' ability to login to the system by other means (f.e. ssh or telnet):

$ sudo /usr/NX/bin/nxserver --stop

You might want to issue a warning to all users connected to inform them of the operation. Run:

$ sudo /usr/NX/bin/nxserver --broadcast "Your message here"

Then, after the warning, terminate all the running sessions:

$ sudo /usr/NX/bin/nxserver --shutdown

If the load balancing feature is enabled on your NX server, you can also proceed with the upgrade of individual node(s) on remote machines and forbid starting new NX sessions on the specified nodes until the operation is completed. By running:

$ sudo /usr/NX/bin/nxserver --stop NODELIST

you can specify the list of the nodes you want to disable, for example:

$ sudo /usr/NX/bin/nxserver --stop 111.222.333.xxx:22 111.222.333.yyy:22

Then proceed with the upgrade instructions provided below and, after the operation is complete, enable access to the node(s) by running:

$ sudo /usr/NX/bin/nxserver --start NODELIST

For example:

$ sudo /usr/NX/bin/nxserver --start 111.222.333.xxx:22 111.222.333.yyy:22

Before upgrading the installation, make a backup of your current NX installation and protect sensitive information that may be present inside the TAR archive by making the backup readable only by the 'root' user:

$ sudo tar cvzf /root/nx-BACKUP.tar.gz /usr/NX
$ sudo chmod 0600 /root/nx-BACKUP.tar.gz

Next ensure that the downloaded package is in the /usr directory, extract the archive and run the setup script for nxnode:

$ sudo tar xvzf nxnode-X.Y.Z-W.i386.tar.gz
$ sudo /usr/NX/scripts/setup/nxnode --update

This operation will overwrite all the files from the previous installation.

2.10 Removing the NX Node Installation from Compressed TAR Package

This operation will remove both the NX Client and the NX Node and the NX server when installed. Open an xterm terminal or similar.

Run the setup script for uninstalling the server, if present, and/or the setup script for uninstalling the node. Finally remove the installation directory:

$ sudo /usr/NX/scripts/setup/nxserver --uninstall 
$ sudo /usr/NX/scripts/setup/nxnode --uninstall
$ sudo rm -rf /usr/NX

Please note that if NX Server is installed, it is advisable to uninstall it before removing the /usr/NX directory. This will ensure a clean installation of any successive NX Server version.

 

3. NX Node Installation Instructions for Solaris Platforms

Log on as superuser ("root") to install, update and remove the package.

3.1 Installing the NX Node

Open a terminal and move to the directory where you have downloaded the package from the NoMachine Web site. Expand the package archive and install it using the pkgadd utility:

 # gunzip nxnode-X.Y.Z-WW.sparc.gz
 # pkgadd -d nxnode-X.Y.Z-WW.sparc

3.2. Updating the NX Node Installation

It is highly recommended you disable access to new NX sessions and terminate all running sessions before proceeding with the upgrade of the node.

To disable access to new NX sessions, open an xterm or similar and run the following command. Please note that this will not affect users' ability to login to the system by other means (f.e. ssh or telnet):

# /usr/NX/bin/nxserver --stop

You might want to issue a warning to all connected users to inform them of the operation. Run:

# /usr/NX/bin/nxserver --broadcast "Your message here"

Then, after the warning, terminate all running sessions:

# /usr/NX/bin/nxserver --shutdown

If the load balancing feature is enabled on your NX server, you can also proceed with the upgrade of individual node(s) on remote machines and forbid starting new NX sessions on the specified nodes until the operation is completed. By running:

# /usr/NX/bin/nxserver --stop NODELIST

you can specify the list of the nodes you want to disable, for example:

# /usr/NX/bin/nxserver --stop 111.222.333.xxx:22 111.222.333.yyy:22

Then proceed with the upgrade instructions provided below and, after the operation is complete, enable access to the node(s) by running:

# /usr/NX/bin/nxserver --start NODELIST

For example:

# /usr/NX/bin/nxserver --start 111.222.333.xxx:22 111.222.333.yyy:22

Before upgrading the installation, make a backup of your current NX installation and protect sensitive information that may be present inside the TAR archive by making the backup readable only by the 'root' user:

#  tar cvzf /root/nx-BACKUP.tar.gz /usr/NX
# chmod 0600 /root/nx-BACKUP.tar.gz

The next step is to remove the previous installation, otherwise the installation will fail because only a single instance of the package is supported at any one time on the same system:

# pkgrm NXnode

Finally, expand the package archive and install it using the pkgadd utility:

# gunzip nxnode-X.Y.Z-W.sparc.gz
# pkgadd -d nxnode-X.Y.Z-W.sparc

3.3 Removing the NX Node Installation

The pkgrm utility will fail if NX Server is installed. First, uninstall NX Server, then proceed with the uninstall of the NX Node package. To uninstall the server, please follow the instructions reported in the NX Server Installation Instructions available at:

https://www.nomachine.com/DT12I00007

 

Open a terminal and remove the NX node installation using the pkgrm utility:

# pkgrm NXnode

For further information about NX Node and NoMachine's range of other products, users are invited to visit our website at www.nomachine.com