Fwd: Re: [FreeNX-kNX] Client works, server doesn't

[Fabian Franz]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

FYI.

- ----------  Weitergeleitete Nachricht  ----------

Subject: Re: [FreeNX-kNX] Client works, server doesn't
Date: Donnerstag, 3. März 2005 18:41
From: LROUFAIL at nc.rr.com
To: Frank Mulder <frank at kde.nl>
Cc: FabianFranz at gmx.de

I am copying Fabian.  He can explain better than me perhaps.

First of all, nxserver is not a service, so it does not show up in the
 process table.

The way it works is when you ssh to the server using a special user, it
 creates a special shell that communicates with the client and initiates the
 NX session.  This session is an instance of NX agent that responds to just
 that one session and then goes away when you are done.  So the NX agent
 process does not show up until you authenticate and request that a session
 is started.  You are not getting that far.

When it says it is already running, I think it means that it looked and found
 that the key file for the special user was already in place.  When you stop
 the server, it just hides the key file so the special user cannot log in.  I
 think that when you removed the original installation you may have left some
 things behind - or maybe it is started by default.

The nx user is the special user that the NX Client and Server use.  The SSH
 session is set up for that user.  Once it creates the ssh session and talks
 to the client, it spawns another session for your real user, 'Jack'.

Someone put it well - the nx user is used to set up a connection so you can
 get to a login prompt.  This nx session gets the login parameters and uses
 them to create the session for your user.  The key for the nx user that is
 distributed with the nomachine client must match the key that is installed
 with the server.  That's why it is simpler to use the --setup-nomachine-key
 option.  That way you do not have to change the key for the client.

So, what you can do is forget about the nx stuff and just try to create an
 ssh connection with the server for the nx user.

ssh -i /usr/NX/share/client.id_dsa.key nx at 192.168.1.6

If that doesn't work, then you probably have the keys messed up on the
 server.  It is either the old key from your last install, or maybe a
 permission problem.

 - L

- ----- Original Message -----
From: Frank Mulder <frank at kde.nl>
Date: Thursday, March 3, 2005 9:47 am
Subject: Re: [FreeNX-kNX] Client works, server doesn't

> Hi,
>
> Thanks for replying.
>
> I started over by removing all nx* packages and reinstalling them.
> Then I did
> the following:
>
> ===============
> mulder:/home# nxsetup --setup-nomachine-key
> Searching for nxserver binary...done
> Setting up /etc/nxserver/ ...done
> Setting up /var/lib/nxserver/ ...done
> Setting up known_hosts and .ssh/authorized_keys2 ...done
> Setting up permissions ...done
> Ok, nxserver is ready.
>
> PAM authentication enabled:
>  All users will be able to login with their
>  normal passwords.
>
> You can change this behaviour in the nxserver script.
> Have Fun!
> ===============
>
> To be sure, I executed "nxserver --start", but it said "NX> 500
> ERROR: Service
> already running".
>
> It _said_ it was running, but I can't find an nx process anywhere
> in my
> process table:
>
> mulder:/home# ps -e | grep nx
> mulder:/home#
> (no output)
>
> Also, connecting with nxclient gave the same output as before:
> ...
> NX> 202 Authenticating user: nx
> NX> 204 Authentication failed.
>
> (1) why is it trying to authenticate user 'nx' (while I'm trying
> to connect
> with user 'frank') and (2) how can I make this work...
>
> Again thanks,
>
> Frank
>
> Op tongersdei 3 maart 2005 02:17, schreef LROUFAIL at nc.rr.com:
> > I think it is --setup-nomachine-key.
> >
> > I made this mistake, and I had to remove and reinstall to get it
>
> to work.
>
> > - L
> >
> > ----- Original Message -----
> > From: Frank Mulder <frank at kde.nl>
> > Date: Wednesday, March 2, 2005 2:05 pm
> > Subject: [FreeNX-kNX] Client works, server doesn't
> >
> > > Hi all,
> > >
> > > I have installed the debian packages for freenx (nxserver,
> > > nxclient, knx), and
> > > the client works (I can do a test drive), but I can't connect to
> > > my own pc.
> > >
> > > I did set up nxserver with "nxsetup --setup-no-machine-key", and
> > > started the
> > > server with "nxserver --start". However, in my process list I
> > > can't find
> > > anything with "nx" in the name. Also, when I try to connect to
> > > myself, I get
> > > this:
> > >
> > > "Server not installed or NX remote access disabled"
> > >
> > > NX> 203 NXSSH running with pid: 14576
> > > NX> 285 Enabling check on switch command
> > > NX> 285 Enabling skip of SSH config files
> > > NX> 200 Connected to address: 192.168.1.6 on port: 22
> > > NX> 202 Authenticating user: nx
> > > NX> 204 Authentication failed.
> > >
> > >
> > > What to do? Thanks for your help
> > >
> > >
> > > Frank
> > > _______________________________________________
> > > FreeNX-kNX mailing list
> > > FreeNX-kNX at kde.org
> > > https://mail.kde.org/mailman/listinfo/freenx-knx

- -------------------------------------------------------
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFCJ1tDI0lSH7CXz7MRAro/AJwMySeySIgcaeaPe6LgvRIzW3BbHQCdE0OV
w/3Bk9g/LqqDYB0nKH5FuwE=
=Lut4
-----END PGP SIGNATURE-----