After screwing around with this for two days and creating many variations of both the FreeNX server and the NX Server, Node and Client I finally came with the fix.
Don’t use the latest NX 4.0 client … it stinks. I went back and got the NX Client 3.5.0.9 which I’m using on all my windows machines…it works just fine, don’t need any to that fancy juke the NX people came up with.
Looks like their latest mato is “Let me make this more difficult so you will understand it”.
I’m using the FreeNX Server on my CentOS 6.4 machine.
So, go to the following URL and do exactly what they are saying and you are done.
Suggestion; Clean up all the old NX client code on the Windows Machine first…delete it all and edit the Windows registry and delete all NX* and NoMachine* items. Reboot and then download the NX Client 3.5.0.9 version.
Do exactly what they say in this URL and you should be a happy person.
***********************************************************************************
http://blog.code-head.com/the-nx-ser...isabled-centos
If you follow the instruction here:
http://wiki.centos.org/HowTos/FreeNX
You will get an error message from NX client:
The nx service is not available or the nx access was disabled
To fix this, connect to your SSH and type:
cat /var/lib/nxserver/home/.ssh/client.id_dsa.key
Copy the text you get and in your NX client, on your login dialog box go to:
Configure… > General Tab > Key
And paste the text there and you will be fine
On the Cut & Paste be sure to copy the entire key from the very top to the very bottom.