Proper documentation is missing about neatx

[GoogleCodeExporter]

a) afaik you need to add your own ssh key to the authorized_keys
b) get nxagent from the freenx ppa deb 
http://ppa.launchpad.net/freenx-team/ubuntu
jaunty main

And where's the documentation? the protocol ident code is broken and i'm digging
through the code to file a proper bug.

Original comment by [email protected] on 8 Jul 2009 at 1:23

[GoogleCodeExporter]

Ouch re: autogen being missing from the tarball - you are correct. I screwed 
that up
somehow. I've marked the tarball as deprecated for now, no point in having it
available for download if it's missing critical files.

Original comment by kormat on 8 Jul 2009 at 7:06

[GoogleCodeExporter]

Regarding the authentication issue you're having, what you've described sounds
correct to me. Robert's point about nxagent is spot on (i have a patch out for 
review
to update INSTALL to mention that now). 

Re: authorized_keys, by default NoMachine's nxclient will use NoMachine's ssh 
key,
which is what you have, so that's correct.

Try this, maybe it'll help:
- On your client machine, delete ~/.nx/temp/*
- Try connect again to the server
- A dir will be created in ~/.nx/temp containing a file called sshlog

It will show you exactly what nxclient received from the server, it's possible 
that
it's getting confused somehow. It's also worth checking /var/log/auth.log for 
any
mention of the nx user.

Original comment by kormat on 8 Jul 2009 at 7:10

[GoogleCodeExporter]

On ubuntu, I had to mess around with /etc/ssh/sshd_config , i.e. add nx to 
AllowUsers.

But now the client produces the following timeout:

NX> 203 NXSSH running with pid: 17926
NX> 285 Enabling check on switch command
NX> 285 Enabling skip of SSH config files
NX> 285 Setting the preferred NX options
NX> 200 Connected to address: 127.0.0.1 on port: 22
NX> 202 Authenticating user: nx
NX> 208 Using auth method: publickey
/usr/bin/X11/xauth:  timeout in locking authority file
/usr/local/lib/neatx/home/.Xauthority
NX> 280 Exiting on signal: 15

and /usr/local/lib/neatx/home/ was owned by root, so I did:
chown -R nx /usr/local/lib/neatx/home/
But, is this OK?  maybe we should only chmod instead?

Now I get:
NX> 203 NXSSH running with pid: 18040
NX> 285 Enabling check on switch command
NX> 285 Enabling skip of SSH config files
NX> 285 Setting the preferred NX options
NX> 200 Connected to address: 127.0.0.1 on port: 22
NX> 202 Authenticating user: nx
NX> 208 Using auth method: publickey
/usr/bin/X11/xauth:  creating new authority file 
/usr/local/lib/neatx/home/.Xauthority
NX> 280 Exiting on signal: 15

Any help?

P.S.
The fact that you need to download the nxclient to test the server should be 
added to
README with a link, probably to: 
http://www.nomachine.com/select-package-client.php

Thanks!

Original comment by [email protected] on 13 Jul 2009 at 6:04

[GoogleCodeExporter]

OK, note to self: RTFM.
I didn't have the config file at the correct place ( /usr/local/etc/neatx.conf 
).

Original comment by [email protected] on 13 Jul 2009 at 6:20

[GoogleCodeExporter]

As this issue is on documentation ill add the following patch for the 
documentation.

build-essential was missing from the list of packages thats needed.


--- OLD_INSTALL 2009-07-14 11:37:14.000000000 +0200
+++ INSTALL     2009-07-14 11:35:31.000000000 +0200
@@ -29,7 +29,7 @@ installed:
     http://netcat.sourceforge.net/

 On debian/ubuntu, these (except NX Agent) can be satisfied using:
-  sudo apt-get install openssh-server python python-pexpect python-simplejson \
+  sudo apt-get build-essential install openssh-server python python-pexpect
python-simplejson \
        python-gtk2 python-gobject gcc autoconf automake python-docutils netcat

 Nx Agent is not currently included in debian or ubuntu. Ubuntu packages can be



Mikael Ljunglöf

Original comment by [email protected] on 14 Jul 2009 at 9:39

Attachments:

• INSTALL.patch

[GoogleCodeExporter]

Well..build-essential is not needed...But make is and make will get installed 
with
build-essential..

Original comment by [email protected] on 14 Jul 2009 at 9:45

[GoogleCodeExporter]

I had the same problem as the OP after following the install instructions.  I 
fixed
it by assigning the 'nx' user a password.  By default, users added with useradd 
have
their password set to '!!' in /etc/shadow.  sshd takes this to mean that the 
account
has been locked, and disallows logins as that user.

Original comment by [email protected] on 14 Jul 2009 at 2:42

[GoogleCodeExporter]

@mikael.ljunglof - i've added make to the list of packages in install, thanks.

@rhysjeffs - that's down to the distro's default configuration. What distro was 
this 
on? 

Original comment by kormat on 20 Jul 2009 at 5:05

[GoogleCodeExporter]

Do neatx  provide support of 'shadow' desktop - connect to existing local X 
session?
Im try to check it  - button "Attach" in nxclient session list unactive.
Standart kde session works great.

Original comment by [email protected] on 21 Jul 2009 at 6:59

[GoogleCodeExporter]

@flyaaway - I'm afraid not. I've added that to the "what doesn't work" list. 
The work
involved isn't that large iirc, it's just a matter of someone doing it.

Original comment by kormat on 22 Jul 2009 at 4:27

[GoogleCodeExporter]

After following the INSTALL directions nxclcient failed to authenticate. I 
figured
out that this was because I use kerberos for ssh here, and had disabled pubkey 
auths.
The manual should mention that the key negotiation should be enabled.

Original comment by joruffin on 8 Aug 2009 at 9:20

[GoogleCodeExporter]

@joruffin
Good point, i'll add that, thanks.

Original comment by kormat on 23 Aug 2009 at 3:33

[GoogleCodeExporter]

If you're using a recent version of Ubuntu (Karmic or later), just do this:

$ sudo add-apt-repository ppa:freenx-team
$ sudo apt-get update
$ sudo apt-get install neatx-server

For more info, see:
https://launchpad.net/~freenx-team/+archive/ppa

Original comment by [email protected] on 27 Apr 2010 at 1:36