[FreeNX-kNX] Logs?
Paul D. Eden
peden at americanphysicians.net
Thu Sep 30 17:06:16 UTC 2004
Thank you. Great suggestions.
Paul
On Thu, 2004-09-30 at 10:03, Doug Burks wrote:
> That's a good question. I'm not aware of any way of selecting from
> the NoMachine client GUI which key you want to use when connecting.
>
> Here's a few options to consider:
>
> -The KNX client may have an option for selecting keys (I haven't tried
> it yet). If it doesn't have it yet, it may have it in the future.
>
> OR
>
> -Keep all the keys in the share directory like this:
> client.id_dsa.key-server1
> client.id_dsa.key-server2
> client.id_dsa.key-server3
> Then manually copy the key into place before connecting with nxclient:
> cp /usr/NX/share/client.id_dsa.key-server1 /usr/NX/share/client.id_dsa.key
>
> OR
>
> -After nxsetup completes, replace the key that it generated with a
> common key that will be used on all NX servers that you want your
> client to connect to. That way, the client only needs one key and can
> connect to multiple servers.
>
> Doug
>
>
> On Thu, 30 Sep 2004 09:43:28 -0700, Paul D. Eden
> <peden at americanphysicians.net> wrote:
> > Since one has to copy the client key from the server to the client does
> > that mean that each client can only connect to one server? There is not
> > an option to have multiple client keys to connect to different servers
> > from the same client?
> >
> > Thanks,
> >
> > Paul
> >
> >
> >
> > On Thu, 2004-09-30 at 09:40, Doug Burks wrote:
> > > My guess is that you ran "nxsetup" and forgot to copy the
> > > newly-generated client key to the client directory.
> > >
> > > When you run "nxsetup", it generates a key (different than the default
> > > NoMachine key) and saves it to:
> > > /home/.nx/.ssh/client.id_dsa.key
> > >
> > > This key must be copied to any client (which includes a client on the
> > > same machine) which wants to connect to this NX server. The Linux
> > > NoMachine client looks for the client key in the following directory:
> > > /usr/NX/share/
> > >
> > > So you can copy the key generated by nxsetup to the client key
> > > directory by doing the following (as root):
> > > cp /home/.nx/.ssh/client.id_dsa.key /usr/NX/share/
> > >
> > > Please try that and let us know whether or not that helps.
> > >
> > > Thanks,
> > > Doug
> > >
> > > On Thu, 30 Sep 2004 17:48:36 +0200, annonygmouse
> > > <annonygmouse at yahoo.co.uk> wrote:
> > > >
> > > > Hello, I've installed the freenx server to a debian unstable and I'm not
> > > > able to log in. I've doubled-checked the steps and I'm sure I'm missing
> > > > nothing, but...
> > > >
> > > > I'm testing the client and the server from the same machine.
> > > >
> > > > When I try to connect, the client says: NX Serv
> > > >
> > > > NX> 203 NXSSH running with pid: 6566
> > > > NX> 200 Connected to address: 127.0.0.1 on port: 22
> > > > NX> 202 Authenticating user: nx
> > > > NX> 208 Using auth method: publickey
> > > > NX> 204 Authentication failed.
> > > >
> > > > I'm trying to see what's going on, is there any way of seeing any logs
> > > > from the server part?
> > > >
> > > > Any hint?
> > > >
> > > > Thanks in advance.
> > > >
> > > > Sebastià.
> > > >
> > > > _______________________________________________
> > > > FreeNX-kNX mailing list
> > > > FreeNX-kNX at kde.org
> > > > https://mail.kde.org/mailman/listinfo/freenx-knx
> > > >
> > > _______________________________________________
> >
> >
> > > FreeNX-kNX mailing list
> > > FreeNX-kNX at kde.org
> > > https://mail.kde.org/mailman/listinfo/freenx-knx
> >
> >
More information about the FreeNX-kNX
mailing list