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

[Trevor Batley]

On Tue, 2005-08-09 at 17:40 -0700, Art Fore wrote:
> I will be back home Friday afternoon. Will run the uninstall script, 
> remove all of the rpms, and reinstall from Suse 9.3 DVD and give it one 
> last try.
> 
Art,

I've read your earlier posts (and some of the feedback).

I run the YAST available FreeNX quite comfortably on my Suse 9.3 box.

The YAST available version is 0.3.1-3 (quite old) and most of the
discussion in these forums is re: 0.4.2 or later (just be aware).

You stated that you installed with 
nxsetup --install --setup-nomachine-key 
but then tried to find keys etc. You don't need to with the
--setup-nomachine-key option. It uses the nomachine key and doesn't
generate special keys (the other option is avaiable if you don't use the
--setup-nomachine-key option). The nomachine key is included with the
1.4 client. So DON'T play with keys.

As Fabian stated earlier 1.5.0 isn't designed to connect to older
versions of FreeNX, so I'd stick to 1.4 of the client.

Trevor B

> Art
> 
> Fabian Franz wrote:
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> > 
> > Am Montag, 8. August 2005 17:14 schrieb Art Fore:
> > 
> >>>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.
> >>>
> > 
> > 
> > Dear Art,
> > 
> > You were trying to use the newest version of the software, which is not yet 
> > supported by SuSE 9.3.
> > 
> > The NX 1.5.0 backend is not yet to be used without having at least FreeNX 
> > 0.4.3 _and_ setting up, USE_1_5_0_BACKEND in config file.
> > 
> > I can understand your frustration, but I was on a conference and so had no 
> > real time to respond to your emails.
> > 
> > I had given you clear advice given, but you seemed to not have understood that 
> > the cookie issue had nothing todo with the key issue. You were almost running 
> > FreeNX.
> > 
> > Here is again some advice if you want to follow it:
> > 
> > - - Use NX-1.4.0 package
> > - - Use FreeNX 0.4.1 from supplementary X/NX
> > 
> > Install both packages, run:
> > 
> > nxsetup --install --setup-nomachine-key --clean --purge
> > 
> > Done.
> > 
> > Do nothing more.
> > 
> > Wait for advice given to you and do not try 100ndreds of pages on the 
> > internet.
> > 
> > Or just buy the commercial server.
> > 
> > cu
> > 
> > Fabian, who is now going to rewrite the whole mess of setup.
> > -----BEGIN PGP SIGNATURE-----
> > Version: GnuPG v1.2.4 (GNU/Linux)
> > 
> > iD8DBQFC+SdvI0lSH7CXz7MRAqWKAJ0Wx8+qs5HhP0Ce7hoPVsmxZKeeOwCcDUGx
> > YNMrm2B2kXxL8WPJNFZudpA=
> > =bHEt
> > -----END PGP SIGNATURE-----
> > 
> > 
> _______________________________________________
> FreeNX-kNX mailing list
> FreeNX-kNX at kde.org
> https://mail.kde.org/mailman/listinfo/freenx-knx