On Thu, Jun 25, 2009 at 10:33 AM, Helmut Jarausch<jarau...@igpm.rwth-aachen.de> wrote: > On 25 Jun, Paul Hartman wrote: >> On Thu, Jun 25, 2009 at 2:18 AM, Helmut >> Jarausch<jarau...@igpm.rwth-aachen.de> wrote: >>> I have been using net-misc/nxserver-freeedition / nxclient for quite >>> some time and it was working great (over an DSL line) >>> >>> But, some time ago, all of a sudden, it stopped working (some task died) >> >> Check in your user ~/.nx/ directory and delete old sessions... I had >> the problem where NX would connect and then timeout before ever >> loading a desktop environment. Deleting all of the old sessions fixed >> it for me. > > Thanks, but on one machine, at least, I get those errors messages which > are driving me nuts > > NX> 203 NXSSH running with pid: 14256 > 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: 134.130.161.252 on port: 22 > NX> 202 Authenticating user: nx > NX> 208 Using auth method: publickey > NX> 204 Authentication failed. > > (I did nxsetup --clean --install --setup-nomachine-key --purge > and with nxclient I've set the key to 'Default' > I'm stuck.
Hi Helmut, Be sure the "nx" user has a password set. Any password. It doesn't matter what, as long as it has one. (it actually uses publickey so the password is irrelevant, but sometimes it won't connect without one) Otherwise I would double-check that your keys match. Check /usr/NX/share/keys/default.id_dsa.key on the server and compare it to the key you have in your nxclient. Furthermore, if you have PAM authentication disabled in your sshd, you need to use the internal user and password database and explicitly add users and passwords to it. At least on my system that's what I had to do.
