NX> 203 NXSSH running with pid: 2948
NX> 285 Enabling check on switch command
NX> 285 Enabling skip of SSH config files
NX> 200 Connected to address: 192.168.1.104 on port: 22
NX> 202 Authenticating user: nx
NX> 208 Using auth method: publickey
NX> 204 Authentication failed.

NX> 203 NXSSH running with pid: 3476
NX> 285 Enabling check on switch command
NX> 285 Enabling skip of SSH config files
ssh: connect to host 192.168.1.104 port 177: Connection refused

# nxserver --start
NX> 100 NXSERVER - Version 1.4.0-02 OS_(GPL)
mv: ne peut évaluer `/home/.nx//.ssh/authorized_keys2.disabled': Aucun fichier ou répertoire de ce type
NX> 122 Service started
NX> 999 Bye

http://doc.ubuntu-fr.org/serveur/freenx

Authentication failed.

Troubleshooting
 
Error message Server not installed or NX access disabled
 
If you see the following error message it means that the nx user’s public key was not accepted.:

NX> 203 NXSSH running with pid: 6721
NX> 285 Enabling check on switch command
NX> 285 Enabling skip of SSH config files
NX> 200 Connected to address: 192.168.2.21 on port: 22
NX> 202 Authenticating user: nx
NX> 208 Using auth method: publickey
NX> 204 Authentication failed.
 
This can be caused by a couple of things.
 
   1.
      the nx user’s authorized key file /var/lib/nxserver/nxhome/.ssh/authorized_keys2 is incorectly named.
      The Slackware sshd daemon is configured to look for an authorized key file named .ssh/authorized_keys not .ssh/authorized_keys2. You can rename the authorized_keys file but it might be better to reconfigure sshd_config, because the nxserver –stop command renames the .ssh/authorized_keys2 to .ssh/authorized_keys2.disabled to prevent access via an nxclient
   2.
      sshd is not running or is incorrectly configured.
      At minimum you need PubkeyAuthentication yes in the sshd_config file
   3.
      The server and client public keys might be different.
      At install the server and client use a default key which should be changed. You can open /var/lib/nxserver/nxhome/.ssh/authorized_keys and compare its contents to the key stored in the client by:
         1.
            Open the client tool
         2.
            Click the Configure button
         3.
            Click the Key button on the General Tab
         4.
            Ensure that the key matches the key found in /var/lib/nxserver/nxhome/.ssh/authorized_keys on the server
   4.
      This issue can also be caused by a locked user account for nx
         1.
            Check to see if the nx account is locked:
            passwd -S nx
         2.
            If the password is locked unlock it with:
            passwd -u nx