1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
|
Setting up Freenx on Slackware Linux
-------------------------------------------------------------------------------
Introduction:
-------------------------------------------------------------------------------
Many thanks to Rick Stout <zipsonic.AT.gmail.com> who wrote a small HOWTO for
Redhat/Fedora users, however much of it applies to Slackware too.
See http://fedoranews.org/contributors/rick_stout/freenx/
FreeNX is the GPL-ed re-implementation of Nomachine's NX server. NX server is a Terminal Server solution which runs on Linux/Unix with clients that run on Linux,Unix,MS Windows and Mac OSX. NX technology uses ssh compression and ssl encryption to deliver near-native performance for displaying and working with a remote X environment.
Once you've started using NX, you'll never go back to VNC.
Prerequisite: sshd must be running as a daemon on port 22
The server:
-------------------------------------------------------------------------------
The Slackware package of FreeNX takes care of the installation and setup, so there is no need to run "nxsetup". The nx package needs to be installed to, as the FreeNX package (which really just consists of a number of shell scripts) wrap around Nomachine's nx libraries.
After installing the nx and freenx packages, the server side of the setup is done!
Clients:
-------------------------------------------------------------------------------
Next, you will need a client. Client programs for several Operating Systems are available at http://www.nomachine.com/download.php - they are all released under the GPL, just as the nx libraries. Installation help can be found at the 'resources' link: http://www.nomachine.com/resources.php
Using the NoMachine SSH key
---------------------------
After installation, the FreeNX server package is configured to accept connections from NX clients with their default SSH key. This is done to give you an "out-of-the-box" NX experience: install the server, get a client, connect, ready!
If you do not want every NX client to make successful connections to your server, you will need to delete the line with the NoMachine key (the line that ends with "root@nettuno") from the file "~nx/.ssh/authorized_keys".
NOTE:
The NX-server's SSH key (or any other key that you might want to use as replacement) is not used for *authentication*. The key is only used to make the automated initial 'null'-connection from NX client to the NX server. The real user authentication occurs at a later stage.
Enforcing use of our own SSH key ('more secure' say the paranoid)
-----------------------------------------------------------------
In case you decide not to use the Nomachine SSH key, the most important part of the initial connection is the correct key file. This file, "client.id_dsa.key", must be copied from the server to your client machine. For example:
# On the server
scp /var/lib/nxserver/home/.ssh/client.id_dsa.key <user>@<client.machine>:
# this should copy the DSA key to your client
# On the client (do as root)
mv /home/<user>/client.id_dsa.key /usr/NX/share/ # hit y to overwrite
chmod 644 /usr/NX/share/client.id_dsa.key
If you are using win32 client, its nx/share is located at:
C:\Program Files\NX Client for Windows\share
If you want to use a key file with a different name (for instance when you connect to more than one FreeNX server, or FreeNX and NomachineNX servers) you can click the "Import" button in the client configuration, and select the key-file that you want to use.
Setting up the connection parameters
------------------------------------
The easiest way to setup the client is to run the wizard. Most settings are pretty self-explanatory. Make sure you select:
* Unix, and Gnome (or kde, or whatever wm you use, ymmv)
* A resolution
* Enable SSL traffic
Click next and finish.
Time to Connect! Start the client. Type your username, password and select the session.
Voila! You're connected.
Note
----
If you created the connection icon, it will only prompt for username and password. Your first connection will give you an error about cache - This is normal.
Sound:
-------------------------------------------------------------------------------
If you want sound, the Linux NX client uses artsd and the Windows/Mac clients use esd. Gnome sessions will work out of the box (Gnome uses esd) but to get sound in KDE, you'll have to configure your client to use "UNIX/Custom" and then finn in "nxesddsp startkde" for the command to run. In KDE, enable "networked sound" and select the "Enlightened Sound Daemon". Now, sound will work!
#-----------------------------------------------------------------------------#
Eric Hameleers < alien -at- slackware -dot- com > :: 18aug2005
$Id$
|
