[FreeNX-kNX] FreeNX & SuSE 9.3

[Fabian Franz]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Am Samstag, 6. August 2005 08:10 schrieb Art Fore:
> I have been trying to get FreeNX going for about 16 hours with no
> success. I have a headless server running suse 9.3 with nx server from
> the suse DVD installed. I ran the nxsetup --install
> --setup-nomachine-key, 

That was good.

>setup the  keys with keygen and copied them to
> the appropriate file on the server. 

No no no. There is a nxkeygen utility for you and you have to copy the keys to 
the client. If you had not done that step you could have used the default 
keys, which for a basic test would have been enough.

> When I run nxserver --status on the
> server, I get
> NX>100 NXSERVER Version 1.4.0.03 OS (GPL)
> NX>110 NX Server is running
> NX>999 Bye
>
> I have tried the nomachine client and the KNX that comes with suse 9.3.
> With the nomachine client I get
>
> NX> 203 NXSSH running with pid: 24411
> NX> 285 Enabling check on switch command
> NX> 285 Enabling skip of SSH config files
> NX> 200 Connected to address: 192.168.0.4 on port: 22
> NX> 202 Authenticating user: nx
> NX> 208 Using auth method: publickey
> NX> 204 Authentication failed

What you did not do was to enable logging on the sshd on the server.

It would have told you that the private key you offered for the nx user was 
wrong.

So you have to copy the private key to all clients that want to use it, or you 
can just remove the key again on the server and rerun nxsetup:

nxsetup --setup-nomachine-key --install --clean --purge

Don't give up on it. Read the FAQs the concept of the nx user is explained 
there.

cu

Fabian
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFC9GObI0lSH7CXz7MRAmuFAJ9ykDzngBW9JV3Nky8qlhDNyxpLaQCeNPo5
cOIGbVRkpS0bT781rknBrZY=
=4zcP
-----END PGP SIGNATURE-----