Ssrini,
No, that's not what I was meaning. Basically, the client seemed to be starting a session, then barfing, so that when I tried the client again, I would get a list of current "running" sessions to connect to, but the resume button was greyed out.
I've now made some progress (I think) by enabling PAM on my sshd and setting ChallengeResponseAuthentication=no, but I still get the remote proxy killing the session.
Code:
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 '3200'.
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.
I've looked about a bit regarding the cookie authentication, but that seems to be a feature issue with FreeNX vs NoMachine.
