Exception Code in NX Server
 

Below is the output of trying to log in to the Nomachine NX server.

I can't find the exception code listed below anywhere in the logs on my system or a google search didn't bring up anything with that exception ID.

Can anyone help out with this problem it would be appreciated. Thanks

NX> 203 NXSSH running with pid: 4812
NX> 285 Enabling check on switch command
NX> 285 Enabling skip of SSH config files
NX> 285 Setting the preferred NX options
NX> 200 Connected to address: 192.168.1.90 on port: 22
NX> 202 Authenticating user: nx
NX> 208 Using auth method: publickey
HELLO NXSERVER - Version 3.5.0-11 - LEDS Evaluation
NX> 105 Hello NXCLIENT - Version 3.5.0
NX> 134 Accepted protocol: 3.5.0
NX> 105 Set shell_mode: shell
NX> 105 Set auth_mode: password
NX> 105 Login
NX> 101 User: hrifkind
NX> 102 Password: ********
NX> 103 Welcome to: centos63.vuquest.com user: hrifkind
NX> 105 Listsession --user="hrifkind" --status="suspended\054running" --geometry="1280x800x32+render" --type="unix-kde"
NX> 127 Available sessions:

Display Type Session ID Options Depth Screen Status Session Name
------- ---------------- -------------------------------- -------- ----- -------------- ----------- ------------------------------

NX> 148 Server capacity: not reached for user: hrifkind
NX> 105 Start session with: --link="adsl" --backingstore="1" --encryption="1" --cache="16M" --images="64M" --shmem="1" --shpix="1" --strict="0" --composite="1" --media="0" --session="VuQuest\04520LLC\04520CentOS" --type="unix-kde" --geometry="640x480+320+115" --client="macosx" --keyboard="query" --screeninfo="640x480x32+render"
NX> 595 ERROR: A fatal error occurred in NX Server.
NX> 595 ERROR: The exception id is: D269D960. To get detailed information about
NX> 595 ERROR: the error search for the string D269D960 in the system log
NX> 595 ERROR: file (usually '/var/log/messages').
NX> 500 ERROR: Last operation failed.
NX> 280 Exiting on signal: 15

We are having big problems on RHEL 6.3/4 with NX4.
Is simply will not work.

We have opened a case to get the nx-guys to fix if. They have not succeeded yet.

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.