Installing RPM's on linux server for configuring NX :
Nx is used as a GUI interface for acessing Linux servers.
1. Need to install NX client on Windows machine.
2. Install Nxclient, NXnode and Nxserver RPM's on Linux server on which you need to acess through GUI.
[root@Servername
/]# rpm -ivh nxclient-3.5.0-7.x86_64.rpm
Preparing...
########################################### [100%]
1:nxclient
########################################### [100%]
Showing
file: /usr/NX/share/documents/client/cups-info
CUPS Printing Backend
The NX Client set-up procedure detected that
your "IPP CUPS" printing
backend doesn't allow printing from the NX
session. In order to have
printing support in your NX system, you need
to set proper permissions
on the IPP backend. Please execute:
chmod 755 /usr/lib/cups/backend/ipp
[root@Servername
/]# rpm -ivh nxnode-3.5.0-6.x86_64.rpm
Preparing...
########################################### [100%]
1:nxnode
########################################### [100%]
NX>
700 Starting: install node operation at: Tue Sep 06 15:45:08 2011.
NX>
700 Autodetected system 'redhat'.
NX>
700 Install log is '/usr/NX/var/log/install'.
NX>
700 Creating configuration in /usr/NX/etc/node.cfg.
NX>
700 Inspecting local CUPS environment.
NX>
700 Generating CUPS entries in: /usr/NX/etc/node.cfg.
NX>
700 Installation of version: 3.5.0-6 completed.
NX>
700 Bye.
[root@Servername
/]# rpm -ivh nxserver-3.5.0-8.x86_64.rpm
Preparing...
########################################### [100%]
1:nxserver
###########################################
[100%]
NX>
700 Installing: server at: Tue Sep 06 15:45:37 2011.
NX>
700 Autodetected system: redhat.
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 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@Servername
/]# service nxserver restart
Trying to
restart NX server:
NX>
123 Service stopped.
NX>
153 Stopping NX server monitor.
NX>
153 NX server monitor already stopped.
NX>
122 Service started.
NX>
999 Bye.
Trying to
restart NX statistics:
NX>
723 Cannot start NX statistics:
NX>
709 NX statistics are disabled for this server.
NX>
999 Bye.
[root@Servername
/]#
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Uninstall
nxservice packages on RHEL5 server
[root@Servername /]# rpm -e nxserver-3.5.0-8.x86_64.rpm
error:
package nxserver-3.5.0-8.x86_64.rpm is not installed
[root@Servername /]# rpm -e nxserver-3.5.0-8.x86_64
NX>
702 Pre-uninstalling: server at: Tue Sep 06 15:50:30 2011.
NX>
702 Shutting down.
NX>
702 Shutdown complete.
NX>
702 Cleaning up NX session DB.
NX>
718 Cannot stop NX statistics:
NX>
709 NX statistics are disabled for this server.
NX>
702 Cleaned up NX session DB.
NX>
702 Bye.
NX>
702 Uninstalling: server at: Tue Sep 06 15:50:33 2011.
NX>
702 Autodetected system: redhat.
NX>
702 Uninstall log is: /usr/NX/var/log/uninstall.
NX>
702 Deleting user: nx from the system.
NX>
702 Saving configuration file to: /usr/NX/etc/server.cfg.backup.
NX>
702 Saving passwords DB to: /usr/NX/etc/passwords.db.backup.
NX>
702 Saving users DB to: /usr/NX/etc/users.db.backup.
NX>
702 Saving administrators DB to: /usr/NX/etc/administrators.db.backup.
NX>
702 Saving profiles DB to: /usr/NX/etc/profiles.db.backup.
NX>
702 Saving guests DB to: /usr/NX/etc/guests.db.backup.
NX>
702 Running: chkconfig to remove init script.
NX>
702 Verifying that all init scripts have been removed.
NX>
702 Uninstallation of version: 3.5.0-8 completed.
NX>
702 Bye.
[root@Servername
/]# rpm -ivh nxclient-3.5.0-7.x86_64
error:
open of nxclient-3.5.0-7.x86_64 failed: No such file or directory
[root@Servername /]# rpm -e nxclient-3.5.0-7.x86_64
error:
Failed dependencies:
nxclient >= 3.0.0 is needed by
(installed) nxnode-3.5.0-6.x86_64
[root@Servername /]# rpm -e nxnode-3.5.0-6.x86_64
NX>
702 Starting: uninstall operation at: Tue Sep 06 15:51:07 2011.
NX>
702 Autodetected system 'redhat'.
NX>
702 Uninstall log is '/usr/NX/var/log/uninstall'.
NX>
702 Running: chkconfig to remove init script.
NX>
702 Verifying that all init scripts have been removed.
NX>
702 Saving configuration file to: /usr/NX/etc/node.cfg.backup.
NX>
702 Version '3.5.0-6' uninstall completed.
NX> 702 Bye.
[root@Servername
/]#
Regards,
Navaneeth
