English
Русский
NX setup in SoHo
1. FreeNX - RHEL
obtain nxclient (x64), nxnode (x64), nxserver (x64) from nomachine.com and install
rpm -Uvh nxclient-*.rpm nxnode-*.rpm nxserver-*.rpm
These instructions are obsolete: fedoranews.org, nomachine.comAlso see: FreeNX server in CentOS 4
2. FreeNX - Ubuntu
Topic was discussed here1, and here2.
- create /etc/apt/source.list.d/freenx.list
deb http://ppa.launchpad.net/freenx-team/ubuntu hardy main deb-src http://ppa.launchpad.net/freenx-team/ubuntu hardy main
- install
apt-get update aptitude install freenx
GNOME conf daemon fails to start if multimedia streaming is enabled in client, see here. This is because FreeNX uses very old esd daemon for sound, and many apps ignore it. For now disable multimedia in client.
Also check out a great ubuntu thread or debian howto.
If you don't care about 2 sessions per machine limit or deadly need sound,use the official NXfree packages from nomachine.com and install
dpkg -i nx*.deb
3. FreeNX - Windows
Now lets follow a good howto.
After installing the NX server as shown above, copy the following file from your linux colocated server box
/var/lib/nxserver/home/.ssh/client.id_dsa.key
over to your Microsoft Windows client machine.
This is the "key" you'll need to gain access to the nxserver you installed in section 1., above.
Obtain and install nxclient-setup.exe from nomachine. Install it as usual, then start it up.
Click on Configure, and under the General tab, click on the [Key...] button: Here, click on Import to read in the contents of the client.id_dsa.key we mentioned above.
For Host, enter the name of your linux colocated server box. For Port, enter 22.
For Desktop, choose Unix and GNOME.
Make sure to select GNOME as the window manager, the default (KDE) is missing the KDE panel, making it awkward to use KDE. Looks like a bug, but the GNOME window manager is preferred by Red Hat, so it is fine for now.
For the network speed setting, the default ADSL is suitable if you're working from home, but for working from the office WAN might be better.
Choose the Display setting to suit your needs, depending on your client machine's current desktop resolution. Start with 1024x768. Once things are working properly, you can go back and choose Custom and enter 1280x1024, as this will give you a larger desktop.
On the Advanced tab, make sure to select the option
[x] Enable SSL encryption on all traffic
It's important to select this option, because not only is the traffic encrypted, but the NX client-server connection uses only the Port you configured above on the server. No ports need to be open on your client box (or on any intervening firewall).
In the Services tab, printing and audio (multimedia) support can be configured, but that is somewhat more involved to explain.
Click [OK] once you've finished configuration. It will prompt you whether to save, click [Yes].
Now enter your regular username and password that you use to log in to your linux colocated server box.
Unlike in VNC where you use the F8 key to pop up a menu to disconnect your client, when using NXclient click the "X" in the top-right-corner of the window (to "kill" the NXclient window), to be able to reconnect to your desktop session later on.
A dialog box will pop up within the desktop session as follows:
Press the suspend button to disconnect the running session.
You will be able to resume the session at later time. Press the
terminate button to exit the session and close all the running
programs.
(Suspend) (Terminate) (Cancel)
Click on "Suspend". The next time you log in using the NXclient, you will see the message:
Resuming the suspended session
and your desktop will be just where you left it earlier.
Note that cut-and-paste works properly between the nxclient environment and your Microsoft desktop, so it is a much cleaner working experience than what you get when using VNC viewer to remotely control your linux colocated server box.
Bookmark this post on:
Comments
Post new comment