NX NoMachine Remote Control of SLES Server

By: msallee

January 5, 2010 2:48 pm





NX NoMachine (Free Edition) is a great tool to take remote control of a Linux server desktop. Summary of steps for setup:

  1. Install RPMs
  2. Create new key with nxserver –keygen
  3. Transfer keys to Client
  4. Install client software on your system
  5. Start the service: sudo nxserver –restart

Install RPMs:

Download and install the nxclient, nxnode, and nxserver rpm packages for your architecture:

sudo rpm -i nxclient-xx.i386.rpm
sudo rpm -i nxnode-xx.i386.rpm
sudo rpm -i nxserver-xx.i386.rpm

Download the Windows/Mac NoMachine NX client for your desktop.

Create a new ssh key pair in /usr/NX/share/keys/:

sudo /usr/NX/bin/nxserver --keygen

Update permissions:

chmod 640 /usr/NX/home/nx/.ssh/authorized_keys2

Now we’ll need to copy the secure key that was generated onto the client machines so that your NX client can use it.

The key on the server is located in: /usr/NX/share/keys/default.id_dsa.key.

For Windows client machines, you will need to copy the key to “C:\Program Files\NX client\Windows\share\keys\” with a distinct name. Later you can point to the appropriate key in your NX Client config. On Mac, you can create an NX folder under your home folder and scp the key with an appropriate naming convention to remember which server it is for.

Use /usr/NX/bin/nxserver –help to see options.

Config file: /usr/NX/etc/server.cfg (though I didn’t have to edit anything here by default)

If using TCP-wrappers:
Add sshd:, <yoursubnet> to hosts.allow


sudo /usr/NX/bin/nxserver --restart

Use the NX Connection Wizard to set up new connection profiles for your servers, and select Advanced to go into the menu that will allow you to point to the key for a particular server.

0 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 5 (0 votes, average: 0.00 out of 5)
You need to be a registered member to rate this post.

Tags: , ,
Categories: SUSE Linux Enterprise Server, Technical Solutions

Disclaimer: As with everything else in the SUSE Blog, this content is definitely not supported by SUSE (so don't even think of calling Support if you try something and it blows up).  It was contributed by a community member and is published "as is." It seems to have worked for at least one person, and might work for you. But please be sure to test, test, test before you do anything drastic with it.

1 Comment

  1. By:bfrancom

    There is also a great tutorial in the openSUSE wiki:

    -Ben Francom