[FreeNX-kNX] first contact, FreeNX

[Terje Andersen]

   ----- Melding fra 7th_sign at soy-geek.com ---------
    Dato: Wed, 30 Jul 2008 13:31:18 -0500
     Fra: 7th Sign <7th_sign at soy-geek.com>
Svar-til: User Support for FreeNX Server and kNX Client <freenx-knx at kde.org>
    Emne: Re: [FreeNX-kNX] first contact, FreeNX
     Til: User Support for FreeNX Server and kNX Client <freenx-knx at kde.org>

> Thanks
>   I followed the wiki and the FreeNX is installed on my Red Hat EL, but when
> I try to connect I get this message:
>
> NX> 203 NXSSH running with pid: 10645
> 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: 192.168.1.247 on port: 22
> NX> 202 Authenticating user: nx
> NX> 208 Using auth method: publickey
> NX> 204 Authentication failed.
>
> any ideas?
>

   Please take a look at the FAQ (look at the bottom of this mail) for  
potential solution(s).

   Qouted from this FAQ:

WHY IS IT TRYING TO AUTHENTICATE USER 'NX' (WHILE I'M TRYING TO  
CONNECT WITH USER 'FRANK') AND WHY DOES THE AUTHENTICATION FAIL?

  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, 'Frank'. 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. So for a connection to server  
192.168.1.6:

   # ssh -i /usr/NX/share/client.id_dsa.key nx at 192.168.1.6If 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. Try running:

   # nxsetup --install --setup-nomachine-key --clean --purge

   Regards,

   Terje


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/freenx-knx/attachments/20080731/9131c7e0/attachment.html>