I'm trying to access my CentOS 6.4 Linux Server from my Windows-XP and my Windows 7
machines and having the issues indicated below. (Not both at the same time).

The NOMachine Client on the Windows machines is:
NX Client For Windows Ver. 3.4.0.7.

I'm running CentOS 6.4 and installed the FreeNX software, setup my user ID and it
appears that everything on the server is working. CentOS has all the latest updates
applied.

When I issue the 'nxserver --status' command the reply states that the server
is up and running.

I can ping the 192.168.1.90 address from anywhere on my LAN.

I can use TightVnc to access the Linux machine on port 22 and I can use Putty to
also access the Linux machine via port 22 so I know that SSH on port 22 is open
and active in CentOS.

On the Windows machines I see the following:

The NX Service is not available or the NX Access was Disabled on Host
192.168.1.90

The details of the message is:

NX> 203 NXSSH running with pid: 3468
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
NX> 204 Authentication failed.

I have no idea where the user ID of NX is coming from as there isn't any such user
specified in the system.

Can anyone help me resolve this issue. Thanks

Update: I used the hostname in the configuration section of the logon and got the following:

NX> 203 NXSSH running with pid: 3368
NX> 285 Enabling check on switch command
NX> 285 Enabling skip of SSH config files
NX> 285 Setting the preferred NX options
nxssh: centos63.vuquest.com: no address associated with name

I got further then before but don't understand what this is indicating? Where can I enter an address?

Thanks

You better have an "nx" userid on your CentOS system. It most certainly will not work without this. That userid should have been created during the installation of the NX server.

Did you distribute the nx private key from your CentOS system to your Windows client? Judging by the error message above, it looks like you might have failed to do that. There is a default key that comes distributed with the NoMachine server and client. However, I do not remember if FreeNX includes this default key. For security reasons, you should not use the default key anyway. The documentation (from NoMachine) tells you how to create and distribute a new key.

I used to use FreeNX years ago. But now that NoMachine supplies free servers (they used to only supply free clients), I see no reason to use FreeNX anymore. I would recommend using NoMachine NX for both the server and the client. Does FreeNX create the nx userid automatically during installation of its server? I know that NoMachine server does this, as well as supplying a default key that works out of the box with their client, but I can't remember if FreeNX does so. It may be a seperate step you have to do manually with FreeNX.

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.

Yes, NX 4 is totally different than NX 3. I don't know if NoMachine advertises backwards compatibility, but I wouldn't expect it. FreeNX definitely imitates the version 3 server. 3 is NoMachines free version. I believe their goal is for 4 to be a paid product, and they were just giving out beta tests or free samples of it right now. But I just went to their website and it is completely different than it was a few weeks ago. So maybe 4 is officially out now. I just glanced around the website briefly and I didn't see where they defined if 4 as free or paid. But I thought I remembered from the old website that 4 was going to be paid. Maybe I'm wrong about that though.

This is exactly what I was referring to when in my first reply I said, "Did you distribute the nx private key from your CentOS system to your Windows client? Judging by the error message above, it looks like you might have failed to do that."

This step is covered in the NoMachine instructions. Probably in the FreeNX instructions as well, but I haven't used FreeNX in so long that I don't remember.

Glad you got it working. NX is really quite awesome. It's very stable and very fast.