[FreeNX-kNX] Server setup; no logging & command not found

[Lucky0106]

I don't know what the deal was, but I removed NoMachine's client 
(apparently an update had been released at some point since I had 
installed it, bumping up the version number by one), and I replaced it 
with OpenNX.

I can actually log in now, and see my desktop! It's beautiful! This 
thing is leagues better than VNC, I can't believe what I was missing out on.

I think this closes the case then. So the solution in the end may have 
been several-fold: I was likely using an incorrect key (not the one 
generated by the server), and I suppose that whatever version of 
NoMachine's client I was using was not compatible with the version of 
freenx I was using as a server.

Thanks for all of your help chris, and for the help of everyone else who 
pitched in.

On 2/24/2014 8:47 AM, chris at ccburton.com wrote:
>
> freenx-knx-bounces at kde.org wrote on 23/02/2014 20:28:58:
>
> > Sorry, I just have one other question that came to mind: Is it ok
> > that I'm using NoMachine's Version 4 free software? I've been doing
> > some googling, and it looks like nomachine removed some important
> > functionality between major releases.
>
> If you are using an older version of a v4 you may have problems.
> ( backward compatibility to v3 wasn't implemented at first )
> also
> you should have a patched FreeNX ( session list )
> see
> http://mail.kde.org/pipermail/freenx-knx/2012-July/009694.html
>
>
> [SNIP]
>
> > Alright: Here's a new test. This time, I logged in over SFTP and
> > copied the file just to be sure they were the same (it seems like I
> > may have actually had a different key file!). With the new file in
> > hand, I fire up NoMachine again, and started the log in process.
> > Now, it just seems to indefinitely sit at the screen saying
> > Connecting to glenux. I looked through my auth.log, and found this bit:
>
> > Feb 23 15:05:51 glenux sshd[2489]: Accepted publickey for nx from
> > 192.168.1.121 port 49976 ssh2
> > Feb 23 15:05:51 glenux sshd[2489]: pam_unix(sshd:session): session
> > opened for user nx by (uid=0)
> >
> > So it must have authed with SSH at this point? The only problem,
> > though, is that it appears nxserver is not creating a new log file
> > in the /var/log directory.
>
> [SNIP]
>
> > Ok, I gave that a try:
>
> > HELLO NXSERVER - Version 3.2.0-74-SVN OS (GPL, using backend: 3.5.0)
> > NX> 105 login
> > login
> > NX> 101 User: glen
> > glen
> > NX> 102 Password:
> > NX> 103 Welcome to: glenux user: glen
> > NX> 105
> > quit
> > Quit
> > NX> 999 Bye
> > /usr/bin/nxserver: line 580: kill: (3426) - No such process
> > Connection to 192.168.1.133 closed.
> > Well, so far so good (I think...).
>
>
> OK, your server is working fine up to this point, (userlogin)
> ( this would normally appear in the server log with logging set to
>          6 debug )
> so
> you need to look at client issues until you see this appearing
> in your log at attempted connections.
>
> [SNIP]
>
> > Ok, I may have forgotten this, but I guess I have to create the log
> > file for nxserver if it doesn't exist :P I did that and confirmed
>
> user nx can't create files in /var/log . . .
>
>
> > everything was working by running the test log in, and it seemed
> > like it was logging ok at that point.
> >
> > Now, I try logging in with NoMachine again, and here is the result:
>
> > glen at glenux:/var/log$ cat nxserver.log
> >
> > -- NX SERVER START:  - ORIG_COMMAND=
> > -- NX SERVER START:  - ORIG_COMMAND=
> > Info: Using fds #4 and #3 for communication with nxnode.
> > HELLO NXSERVER - Version 3.2.0-74-SVN OS (GPL, using backend: 3.5.0)
> > NX> 105 hello NXCLIENT - Version 3.2.0
> > NX> 134 Accepted protocol: 3.2.0
> > NX> 105 SET SHELL_MODE SHELL
> > NX> 105 SET AUTH_MODE PASSWORD
> > NX> 105 login
> > NX> 101 User: glen
> > NX> 102 Password: glen at glenux:/var/log$
> >
> > So either it's waiting for a password (and the client hasn't picked
> > up on that), or the password was entered and it just doesn't know
> > what to do now. Just for kicks and grins, I tried clearing all saved
> > passwords in the client, then I tried logging in again. Same result.
>
> Which client are you using - an old one ??
>
>
>
> ________________________________________________________________
>       Were you helped on this list with your FreeNX problem?
>      Then please write up the solution in the FreeNX Wiki/FAQ:
>
> http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ
>
>           Don't forget to check the NX Knowledge Base:
>                   http://www.nomachine.com/kb/
>
> ________________________________________________________________
>         FreeNX-kNX mailing list --- FreeNX-kNX at kde.org
>        https://mail.kde.org/mailman/listinfo/freenx-knx
> ________________________________________________________________
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/freenx-knx/attachments/20140224/44e4cd5b/attachment.html>