Tachtler: nx_freenx
Contents
NX / FreeNX
FreeNX is a new and amazing way to remotely access a remote screen. The main libraries ofFreeNX come from the company NoMachine and released under the GPL license. FreeNX is a GPL implementation of the NX Server and NX Client Components.A transmission of a remote screen can also be realized with a small range of Internet connection (56k modem) thanks to a high compression.
Installation server
From this point on
root privileges to run the following commands needed. To root to be, please enter the following command:$ Su - Password:
With the following command the necessary components from the default repository's are from CentOS -
extras installed:# Yum install nx freenx Loaded plugins: fastestmirror, refresh-packagekit, security Loading mirror speeds from cached hostfile Setting up Install Process Resolving Dependencies -> Running transaction check ---> Package freenx.x86_64 0:0.7.3-8. El6.centos will be installed -> Processing Dependency: xorg-x11-apps for package: freenx-0.7.3-8.el6.centos.x86_64 -> Processing Dependency: / usr / bin / expect for package: freenx-0.7.3-8.el6.centos.x86_64 -> Processing Dependency: expect for package: freenx-0.7.3-8.el6.centos.x86_64 -> Processing Dependency: nc for package: freenx-0.7.3-8.el6.centos.x86_64 ---> Package nx.x86_64 0:3.5.0-1. El6.centos will be installed -> Processing Dependency: libXpm.so.4 () (64bit) for package: nx-3.5.0-1.el6.centos.x86_64 -> Running transaction check ---> Package expect.x86_64 0:5.44.1.15-2. El6 will be installed -> Processing Dependency: libtcl8.5.so () (64bit) for package: expect-5.44.1.15-2.el6.x86_64 ---> Package libXpm.x86_64 0:3.5.8-2. El6 will be installed ---> Package nc.x86_64 0:1.84-22. El6 will be installed ---> Package xorg-x11-apps.x86_64 0:7.4-10. El6 will be installed -> Processing Dependency: libXaw.so.7 () (64bit) for package: xorg-x11-apps-7.4-10.el6.x86_64 -> Running transaction check ---> Package libXaw.x86_64 0:1.0.6-4.1. El6 will be installed ---> Package tcl.x86_64 1:8.5.7-6. El6 will be installed -> Finished Dependency Resolution Dependencies Resolved ================================================== ============================== Package Arch Version Repository Size ================================================== ============================== Installing: freenx x86_64 0.7.3-8.el6.centos extras 94 k nx x86_64 3.5.0-1.el6.centos extras 2.7 M Installing for dependencies: expect x86_64 5.44.1.15-2.el6 base 256 k libXaw x86_64 1.0.6-4.1.el6 base 167 k libXpm x86_64 3.5.8-2.el6 base 59 k nc x86_64 1.84-22.el6 base 57 k tcl x86_64 1:8.5.7-6. el6 base 1.9 M xorg-x11-apps x86_64 7.4-10.el6 base 296 k Transaction Summary ================================================== ============================== Install 8 Package (s) Total download size: 5.5 M Installed size: 14 M Is this ok [y / N]: y Downloading Packages: (1/8): expect-5.44.1.15-2.el6.x86_64.rpm | 256 kB 00:00 (2/8): freenx-0.7.3-8.el6.centos.x86_64.rpm | 94 kB 00:00 (3/8): libXaw-1.0.6-4.1.el6.x86_64.rpm | 167 kB 00:00 (4/8): libXpm-3.5.8-2.el6.x86_64.rpm | 59 kB 00:00 (5/8): nc-1.84-22.el6.x86_64.rpm | 57 kB 12:00 (6/8): nx-3.5.0-1.el6.centos.x86_64.rpm | 2.7 MB 12:00 (7/8): tcl-8.5.7-6.el6.x86_64.rpm | 1.9 MB 12:00 (8/8): xorg-x11-apps-7.4-10.el6.x86_64.rpm | 296 kB 12:00 -------------------------------------------------- ------------------------------ Total 9.9 MB / s | 5.5 MB 12:00 Running rpm_check_debug Running Transaction Test Transaction Test Succeeded Running Transaction Installing: libXpm-3.5.8-2.el6.x86_64 1/8 Installing: libXaw-1.0.6-4.1.el6.x86_64 2/8 Installing: xorg-x11-apps-7.4-10.el6.x86_64 3/8 Installing: nx-3.5.0-1.el6.centos.x86_64 4/8 Installing: nc-1.84-22.el6.x86_64 5/8 Installing: 1: tcl-8.5.7-6.el6.x86_64 6/8 Installing: expect-5.44.1.15-2.el6.x86_64 7/8 Installing: freenx-0.7.3-8.el6.centos.x86_64 8/8 Stopping sshd: [OK] Starting sshd: [OK] Starting freenx-server: [OK] Installed: freenx.x86_64 0:0.7.3-8. el6.centos nx.x86_64 0:3.5.0-1. el6.centos Dependency Installed: expect.x86_64 0:5.44.1.15-2. el6 libXaw.x86_64 0:1.0.6-4.1. el6 libXpm.x86_64 0:3.5.8-2. el6 nc.x86_64 0:1.84-22. el6 tcl.x86_64 1:8.5.7-6. el6 xorg-x11-apps.x86_64 0:7.4-10. el6 Complete!
The following user was also created, which can be checked with the following command:
# Cat / etc / passwd | grep nx nx: x: 495:490 :: / var / lib / nxserver / home :/ usr / bin / nxserverIn addition, the following groups were created, which can be checked with the following command:
# Cat / etc / group | grep nx nx: x: 490:
To start the FreeNX server to realize even after a system (re)-start permanent in the future, the following command can be used. Here is xxx to the start scripts of runlevel of the operating system added:
# Chkconfig freenx-server on A verification that the FreeNX server is started in each runlevel of the operating system on a system-(re)-start with can be queried with the command:
# Chkconfig - list | grep freenx-server freenx-server 0: off 1: off 2: on 3: on 4: on 5: on 6: off
Finally, the will FreeNX server started via the following command:
# Service freenx-server start Starting freenx-server: [OK]
IMPORTANT - Poss. is the user account nx locked (locked)!If this is the case, the user's subsequent configurations
nx
required:
First, it can be determined with the following command if the user is actually blocked:
# Passwd-S nx nx LK 2012-03-08 0 99999 7 -1 (Password locked.)
After following commands can be used to unlock the user:
# Usermod-U nx and# Passwd-u nx Unlocking password for user nx. passwd: Warning: unlocked password would be empty. passwd: Unsafe surgery (use-f to force)
Finally MUST have a password, be assigned to the user:
# Passwd nx Changing password for user nx. New password: Retype new password: passwd: all authentication tokens updated successfully.
Configuration Server
With the following command from a sample configuration file in the configuration directory
/etc/nxserver of FreeNX server configuration file/etc/nxserver/node.conf copied: # Cp / etc / nxserver / node.conf.sample / etc / nxserver / node.conf IMPORTANT - Make any adjustments to the configuration by eg sshd port equal to 22 and so on!Finally, it must have the configuration file
/etc/nxserver/node.conf , which was only reprinted be adjusted as follows (only relevant part):Before:
... # This adds the passdb to the possible authentication methods ENABLE_PASSDB_AUTHENTICATION # = "0" ...After:
... # This adds the passdb to the possible authentication methods ENABLE_PASSDB_AUTHENTICATION = "1" ...
Below it is required in the directory
/var/lib/nxserver/home/.ssh/ file authorized_keys2 to copy with the following command: # Cp-a / var/lib/nxserver/home/.ssh/authorized_keys2 / var / lib / nxserver / home / .ssh / authorized_keys As a next step, a server restart is required, which can be realized with the following command:
# Service freenx-server restart Then, in the configuration file of the SSH daemon
/etc/ssh/sshd_conf following adaptation perform (only relevant part):Before:
... AllowUsers jolanda ...After:
... AllowUsers jolanda nx ...
To give effect to this amendment, it is necessary also the SSH daemon durchzustarten me The following command:
# Service sshd restart Configuration Server Logging
To the logging of FreeNX server to activate, the following changes in the configuration file is
/etc/nxserver/node.conf required (only relevant segment)):... # This controls the verbosity of the directives server-wide log. # 0: No Logging # 1: Errors # 2: Warnings # 3: Important information # 4: Server - Client communication # 5: Information # 6: Debugging information # 7: stderror of some applications # Tachtler # Defautl: # NX_LOG_LEVEL = 0 NX_LOG_LEVEL = 3 # By setting this to 0 the nxserver might also be a bit faster, but passwords can be found in the log files. # Tachtler # Default: # NX_LOG_SECURE = 1 NX_LOG_SECURE = 1 # Before turning logging on, please make surethat NX_LOGFILE is # Writeable for the "nx" user # Tachtler # Default: # NX_LOGFILE = / var / log / nxserver.log NX_LOGFILE = / var / log / nx / nxserver.log ...
IMPORTANT - The log file /var/log/nx/nxserver.log must BEFORE first use AND not created with write permissions for the user nxbe provided!This can be realized using the following commands. Conditioning an empty log file with the following command:
# Touch / var / log / nx / nxserver.log Write permissions for the user nx set with the following command: # Chown nx.root / var / log / nx / nxserver.log Property rights for the user nx set with the following command: # Chmod 600 / var / log / nx / nxserver.log Finally restart the is FreeNX server with the following command is required:
# Service freenx-server restart Restarting freenx-server: Stopping freenx-server: [OK] Starting freenx-server: [OK]
Download Client for Linux
The client to the FreeNX server to access can not part of the CentOS repository's. This can be downloaded from the following page:
Installation Client for Linux
With the following command the necessary components from the directory and the name of the installation RPM package be here eg
/tmp/nxclient-3.3.0-6.i386.rpm installed:# Yum local install - nogpgcheck / tmp/nxclient-3.3.0-6.i386.rpm Loading "fastestmirror" plugin Setting up Local Package Process Loading mirror speeds from cached hostfile * Update: linux install * Base: linux install * Addons: linux install * Extras: linux install Examining / tmp/nxclient-3.3.0-6.i386.rpm: nxclient - 3.3.0-6.i386 Marking / tmp/nxclient-3.3.0-6.i386.rpm to be installed Resolving Dependencies -> Running transaction check ---> Package nxclient.i386 0:3.3.0-6 set to be updated -> Finished Dependency Resolution Dependencies Resolved ================================================== =========================== Package Arch Version Repository Size ================================================== =========================== Installing: nxclient i386 3.3.0-6 / tmp/nxclient-3.3.0-6.i386.rpm 9.7 M Transaction Summary ================================================== =========================== Install 1 Package (s) Update 0 Package (s) Remove 0 Package (s) Total download size: 9.7 M Is this ok [y / N]: y Downloading Packages: Running rpm_check_debug Running Transaction Test Finished Transaction Test Transaction Test Succeeded Running Transaction Installing: nxclient # # # # # # # # # # # # # # # # # # # # # # # # # [1/1] Showing file: / usr / NX / share / documents / client / cups-info CUPS Printing Backend The NX Client set-up procedure detected did your "IPP CUPS" printing backend does not 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 Installed: 0:3.3.0-6 nxclient.i386 Complete!
Installation Client for Windows
After the successful installation of the Windows client (via double- 
), Some adjustments must be made.
), Some adjustments must be made.Configuration of the client's
IMPORTANT - The here newly created user MUST have a local user account, so in /etc/passwd to be included!Furthermore, it is required a user with a local user account on the system to be accessed with the and on the desktop, also the
nxserver admit known, what can be done with the following commands:# Nxserver - adduser jolanda NX> 100 nxserver - Version 3.2.0-73 OS (GPL, using backend: not detected) NX> 1000 NXNODE - Version 3.2.0-73 OS (GPL, using backend: not detected) NX> 716 Public key added to: / home/jolanda/.ssh/authorized_keys2 NX> 1001 Bye. NX> 999 Byeand
# Nxserver - passwd jolanda NX> 100 nxserver - Version 3.2.0-73 OS (GPL, using backend: not detected) New password: Password changed. NX> 999 Bye
The contents of the file
/home/jolanda/.ssh/authorized_keys2 MUST then to an existing file named/home/jolanda/.ssh/authorized_keys are appended, or they are simply copied, as shown by both the following commands:Copy:
# Cp-a / home/jolanda/.ssh/authorized_keys2 / home / jolanda / .ssh / authorized_keys - Or -
Attach
# Cat / home/jolanda/.ssh/authorized_keys2 >> / home / jolanda / .ssh / authorized_keys On Linux, the following private key from the directory
/etc/nxserver/ named client.id_dsa.key in the installation directory of NX Clients for Linux can be copied, which would subsequently directory:/usr/NX/share/keys/client.id_dsa.key
On Windows, the following private key must be in the directory
/etc/nxserver/ named client.id_dsa.key in the installation directory of NX Clients for Windows to copy, which would subsequently directory:C:\Program Files\NX Client for Windows\share\keys\client.id_dsa.key
Configuration of the client's graphical user interface
The configuration of the clients, exceptionally, shown herein in one Configuration in Windows © ® Vista ™:
1 Start the NX Connection Wizard
2 Here, the information such as session name, host, port, and the bandwidth can be set.
3 This determines which X window manager running on the server (in this case GNOME) and what resolution should be displayed in the display window.
4 Here may (but need not) a desktop icon will be created, but more importantly, here the Advanced settings can be made in the next screen to display ...
5 On this tab, the button - Key to be changed on the page with a click of the left mouse button.
6 IMPORTANT - The existing key is IRRELEVANT, it must be imported as shown below, another key!
IMPORTANT - The existing key is IRRELEVANT, it must be imported as shown below, another key!
7 IMPORTANT - The following key must be in the directory
IMPORTANT - The following key must be in the directory C:\Program Files\NX Client for Windows\share\keys\client.id_dsa.key be imported!
8 After entering the local user on Linux here
jolanda and password to login ...
9 ... should be a connection can be established!
Tachtler / nx_freenx.txt · Last modified: 29/08/2012 11:40 by claus
Pages Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Noncommercial-Share Alike 3.0 Unported
0 件のコメント:
コメントを投稿