Nxserver
NeatX
Open Source Alternative: NeatX (Google)
http://code.google.com/p/neatx/
Authentication Issues
This can be a real pain sometimes.
If using ssh keys, ensure the settings match between NX and sshd, and that permissions are correct on authorized_keys[2] file. NX appears to insert a key into user's authorized_keys[2] file (if present).
For example, ensure that authorized_keys or authorized_keys2 is the same in both:
/etc/ssh/sshd_config /usr/NX/etc/node.cfg
Test a user connection locally with
nxserver --usercheck userName
You can also verify the nx user can connect with its ssh key, which is required for user connections.
ssh -i /usr/NX/share/keys/default.id_dsa.key nx@localhost [for nxserver 3.5] ssh -i /usr/NX/home/nx/.nx/ssh/server.id_dsa.key nx@localhost [for nxserver 4]
Also ensure sshd_config contains:
PubkeyAuthentication yes AuthorizedKeysFile .ssh/authorized_keys2 AllowUsers nx user1 user2 . . . userN
Lastly ensure the SSH key in the client matches that being used on the server - it should unless you have manually created new keys.
http://en.gentoo-wiki.com/wiki/Nxserver#If_Authentication_doesn.27t_work
http://www.nomachine.com/ar/view.php?ar_id=AR02E00444
SSH Tunneling
$ssh -X -c blowfish -o 'compression=no' -L 9000:localhost:22 remote@workstation.com
As NX already performs its own compression, and blowfish is a bit faster.
NXClient
Client Config Options:
http://www.nomachine.com/documents/configuration/client-guide.php
http://www.nomachine.com/ar/view.php?ar_id=AR02C00151
http://www.nomachine.com/documents/configuration/client-guide.php
http://www.nomachine.com/documentation/NX-XProtocolCompression.php
http://www.nomachine.com/ar/view.php?ar_id=AR01C00137
PAM Auth
If using PAM and /etc/scurity/access ensure user nx is allowed
Hung Sessions
If a user is disconnected, and are not able to reconnect, you may have to clear their session file in:
/var/lib/neatx/sessions/
Edit /etc/rc.local to do this automatically on boot:
# Delete all NX sessions after a reboot, they're dead anyway rm -rf /var/lib/neatx/sessions/*
Client Crashes
If the user selects KDE when connecting to a Gnome session the client will silently crash. On the server you can look in the users session directory and see what options were passed, and see if type=kde, etc. E.g:
[root@nxserver]# cat /var/lib/neatx/sessions/9A342F017477253F278538CEF880F1C3/options \ nx/nx,fullscreen=0,product=Neatx-GPL,shpix=1,clipboard=both,render=1,composite=1,cache=16M,geometry=3360x1022,accept \ =127.0.0.1,client=linux,strict=0,cleanup=0,cookie=5B145C38596C6946F47E1AAF2C887100,resize=0,keyboard=pc102/us,images=64M \ ,link=adsl,type=kde,id=nxserver.my.com-856-9A342F017477253F278538CEF880F1C3,backingstore=1,shmem=1:856
Logging
http://www.nomachine.com/documentation/supp-request-3.x.php
