I need help solving a default by-the-book installation of NoMachine NX client and server.
On my client (nxclient on a Mac) when I attempt to connect I am told
The NX service is not available or the NX access was disabled on host 192.168.1.10
In the runlog all is fine up to
Received line from nxssh process [NX> 204 Authentication failed.] with code 
As root I installed client, node, server, and manager using
rpm -iv filename.rpm
And the following was the only serious warning, which occurred during installation of nxserver:
NX> 700 WARNING: Error when trying to connect to NX server, error is:
NX> 700 WARNING: nxsetup cannot validate the sanity of the current installation:
NX> 700 WARNING: the current system or NX configuration could be broken.
Brilliant feedback, isn’t it?
I think the problem is either in alterations I made to sshd_config or in the public/private keys negotiated by nxserver and nxclient, even though they should have default values. (Or, darn, it could be something much deeper.)
I’m posting this here rather than at NoMachine because I’m interested in the probable, unique issues found with SuSE. Any help would be appreciated.
The error is shown just after the session is started:
Session: Session started at ‘Thu Aug 14 01:16:41 2008’.
Info: Established X server connection.
Warning: Can’t create the shared memory segment. Error is 12 ‘Cannot allocate memory’.
Info: Using shared memory parameters 0/0K.
Error: Failure reading from the peer proxy.
Error: Connection with remote peer broken.
Error: Please check the state of your network and retry.
Session: Terminating session at ‘Thu Aug 14 01:16:45 2008’.
Session: Session terminated at ‘Thu Aug 14 01:16:45 2008’.