root@server13:~# wget
http://64.34.161.181/download/3.5.0/Linux/nxclient_3.5.0-7_amd64.deb http://64.34.161.181/download/3.5.0/Linux/nxnode_3.5.0-7_amd64.deb http://64.34.161.181/download/3.5.0/Linux/FE/nxserver_3.5.0-9_amd64.deb
--2012-07-30 19:05:48--
http://64.34.161.181/download/3.5.0/Linux/nxclient_3.5.0-7_amd64.deb
Verbindungsaufbau zu 64.34.161.181:80... fehlgeschlagen: Verbindungsaufbau abgelehnt.
--2012-07-30 19:05:48--
http://64.34.161.181/download/3.5.0/Linux/nxnode_3.5.0-7_amd64.deb
Verbindungsaufbau zu 64.34.161.181:80... fehlgeschlagen: Verbindungsaufbau abgelehnt.
--2012-07-30 19:05:48--
http://64.34.161.181/download/3.5.0/Linux/FE/nxserver_3.5.0-9_amd64.deb
Verbindungsaufbau zu 64.34.161.181:80... fehlgeschlagen: Verbindungsaufbau abgelehnt.
root@server13:~# dpkg -i nx*_3.5.0-*_amd64.deb
(Lese Datenbank ... 124523 Dateien und Verzeichnisse sind derzeit installiert.)
Vorbereitung zum Ersetzen von nxclient 3.5.0-7 (durch nxclient_3.5.0-7_amd64.deb) ...
Ersatz für nxclient wird entpackt ...
Vorbereitung zum Ersetzen von nxnode 3.5.0-9 (durch nxnode_3.5.0-9_amd64.deb) ...
Ersatz für nxnode wird entpackt ...
Vormals abgewähltes Paket nxserver wird gewählt.
Entpacken von nxserver (aus nxserver_3.5.0-11_amd64.deb) ...
nxclient (3.5.0-7) wird eingerichtet ...
nxnode (3.5.0-9) wird eingerichtet ...
NX> 701 Autodetected system 'debian'.
NX> 701 Update log is '/usr/NX/var/log/update'.
NX> 701 Updating node at: Mo Jul 30 19:06:07 2012.
NX> 701 Checking NX node configuration using /usr/NX/etc/node.cfg file.
NX> 701 Running: innserv to remove init script.
NX> 701 Verifying that all init scripts have been removed.
NX> 701 WARNING: Cannot find file: printers.conf.
NX> 701 WARNING: Please verify your CUPS configuration.
NX> 701 Update of NX node has been completed with warnings.
NX> 701 Please review the update log for details.
NX> 701 Showing file: /usr/NX/share/documents/node/cups-info
CUPS Printing Backend
The NX Node setup procedure could not detect your "CUPS"
installation: either CUPS is not installed on your system
or it was installed in a non-standard path. CUPS is needed
in order to enable printing support in your NX system.
Please note that you can enable printing support for your
NX system at any time; to do this make sure that you have
CUPS installed then run:
/usr/NX/scripts/setup/nxnode --nxprintsetup <pathname>
to specify the location of the CUPS root path.
NX> 701 Bye.
nxserver (3.5.0-11) wird eingerichtet ...
NX> 700 Installing: server at: Mo Jul 30 19:06:09 2012.
NX> 700 Autodetected system: debian.
NX> 700 Install log is: /usr/NX/var/log/install.
NX> 700 WARNING: Found file: /usr/NX/etc/keys/node.localhost.id_dsa.
NX> 700 WARNING: Skipping generation keys for NX users authentication.
NX> 723 Cannot start NX statistics:
NX> 709 NX statistics are disabled for this server.
NX> 700 WARNING: Error when trying to connect to NX server, error is:
NX> 700 WARNING: nxsetup cannot validate the sanity of the current installation:
NX> 700 WARNING: the current system or NX configuration could be broken.
NX> 700 WARNING: If difficulties arise (for example sessions cannot be started),
NX> 700 WARNING: it is advisable that you try to uninstall the NX server and the
NX> 700 WARNING: NX client packages then install them again.
NX> 700 WARNING: Search also the NoMachine Knowledge Base at the URL below:
NX> 700 WARNING:
http://www.nomachine.com/kb
NX> 700 WARNING: for common errors encountered when performing a software update
NX> 700 WARNING: and the related hints on how to solve them..
NX> 700 Installation of NX server was completed with warnings.
NX> 700 Please review the install log '/usr/NX/var/log/install'
NX> 700 for further details.
NX> 700 Showing file: /usr/NX/share/documents/server/install-notices
Server keys
The initial login between client and server happens through a DSA key
pair, i.e. a couple of specially generated cryptographic keys, called
the private key and the public key, which allow you to establish a
secure connection, by means of SSL encryption, between NX client and
NX server.
The public part of the key-pair is provided during the installation
of the server, while the private part of the key-pair is distributed
together with the NX Client. This ensures that each NX client is able
to authenticate to the server and to start the procedure for autho-
rizing the user and negotiating the session.
If you want to create a virtual private network (VPN) instead, you
need to generate a new DSA key-pair and distribute the private part
of the key-pair to those NX clients you want authenticated to the NX
server. More information on how to generate and distribute a new DSA
key-pair is available at:
http://www.nomachine.com/ar/view.php?ar_id=AR01C00126
Creating Users
NX is configured to allow access from any system user, as long as
valid credentials are given to the user for the SSH login. NX pro-
vides an alternative authorization method, allowing system admin-
istrators to determine which users are given access to the NX fun-
ctionalities. This works by implementing a separation between the
system password and the NX password, so that, for example, it is
possible to forbid remote access to the system by any other means
except via NX and use the NX tools to implement effective accounting
of the system resources used by the user, or to share NX passwords in
an external database.
To activate the NX user and password DBs, you will have to edit the
NX server configuration file by hand or use the NX Server Manager
Web tool available for download on the NoMachine Web site at:
http://www.nomachine.com/download-manager.php
Session Shadowing and Desktop Sharing
The session shadowing functionality allows you to share NX sessions
running on the node. The desktop sharing functionality instead, gives
access to the native display of the X server as if you were in front
of the monitor. By default you can access sessions in interactive mode
and upon authorization of the session owner. You can modify this beha-
viour by tuning the server configuration according to your needs, for
example by allowing access to sessions in view-only mode, or connecting
to either a suspended session or the local display via the Desktop
Manager login window.
Load Balancing
NX Advanced Server provides support for multi-node capabilities and
load balancing. In its current implementation, NX server can only
manage accounts on the host machine, so to grant access to the node
running remotely, you will need to create the user account directly
on the remote node host by issuing the NX node commands as root user.
You will also need to add the NX Server public DSA Key to the node to
allow this server to connect to the node running on the remote host.
Documentation
For further information on how to manage the configuration of your
NX system, please refer to the System Administrator's Guide available
on the NoMachine Web site at:
http://www.nomachine.com/documentation/admin-guide.php
The NoMachine Team.
NX> 700 Bye.
root@server13:~#
