[FreeNX-kNX] FreeNX & SuSE 9.3 (SOLVED)

[Art Fore]

On Sat, 2005-08-06 at 08:29 -0700, Art Fore wrote:
> On Sat, 2005-08-06 at 09:15 +0200, Fabian Franz wrote:
> > -----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-----
> > 
> 
> done an unstall with -clean and --puge, installed the new rpms with
> YaST. Still no /usr/share and have not been able to find the
> client.id_dsa.key. It did update the authorized_keys2 file in ~/.ssh
> though. Do get a different message with the nomachine client
> 
> NXPROXY - Version 1.5.0
> 
> Copyright (C) 2001, 2005 NoMachine.
> See http://www.nomachine.com/ for more information.
> 
> Info: Proxy running in client mode with pid '3318'.
> Info: Synchronizing local and remote caches.
> Info: Handshaking with remote proxy completed.
> Info: Not using NX delta compression.
> Info: Using lan link parameters 16384/8/0/0.
> Info: Using pack method '16m-jpeg-9' with session 'unix-kde'.
> Info: Not using ZLIB stream compression.
> Info: Not using remote ZLIB stream compression.
> Info: Not using persistent cache.
> Info: Starting X protocol compression.
> Warning: Cookie mismatch in the authentication data.
> Info: End of session requested by remote proxy.
> Info: Shutting down the link and exiting.
> 
> The Cookie mismatch error make no sense to me though. Where did cookies
> all of a sudden come into the picture. Have seen nothing mentioning
> cookies at all on this. I thought cookies were for web browsers.
> 
> Tried KNX and I get that it authenticated, session started, then
> nothing.
> 
> Art
> 
> _______________________________________________
> FreeNX-kNX mailing list
> FreeNX-kNX at kde.org
> https://mail.kde.org/mailman/listinfo/freenx-knx

After trying two versions 1.4 & 1.5, of FreeNX, spending two weekends
trying to get it to work, going through hundreeds of pages on the
subject on the internet and email archives, I give up.

I have VNC working but wanted a more secure system. Will give it another
try in a year or so. Hopefully by then, the documentation will be
upgraded to match the version. Had it almost working one time, but
followed a howto which set me back again even after doing a new
installation. 

NOTE TO THE DEVELOPERS: You need to have much more clearer instructions
or, better yet, an installation script for installing the keys with
better explanations for non-programmer people. I would have written one
for Suse 9.3 if I had gotten it to operate, but am so confused right
now, I could not do it.

I am sure it is a nice program once you get it working. Best of luck in
the future.

Art