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