[FreeNX-kNX] ESCALATION: Problem Connecting to FreeNX 1.5 Server

[Tyler Ellis]

David Parish wrote:
> If it is really this urgent, why not buy the commercial product and
> get commercial support? Who on this list would you be escalating to?
>   
Actually i read it, it felt important i hope noone ever does this again. 
that was psychologically embarrassing.
> You can download a free version off the comercial version of the
> product.  If it doesn't work, you can call them and they can help you
> through it.
>
> -Dave
>
> On 9/5/06, Clive Eisen <clive at hildebrand.co.uk> wrote:
>   
>> Kaplan, Andrew H. wrote:
>>     
>>> Hi there –
>>>
>>>
>>>
>>> I really need to get this issue resolved within the next few days or I
>>> will be forced to abandon my attempts
>>>
>>> to get FreeNX running on our systems. Here is the current situation:
>>>
>>>
>>>
>>> I have upgraded the nx and freenx packages on our server that in turn
>>> was upgraded from Fedora Core 4
>>>
>>> to Core 5. The versions of nx and freenx respectively that are now
>>> running are 2.0.0 and 1.5.0-50. The nx
>>>
>>> user account has been added to the wheel group on the server.
>>>
>>>
>>>
>>> I have run the nxserver –adduser and –passwd commands on the server to
>>> create the user account and
>>>
>>> its associated password. I also ran the ./nxserver –status command to
>>> confirm the server is indeed running.
>>>
>>>
>>>
>>> The server in question has had Bastille-Linux installed to harden the
>>> system against hack attacks.
>>>
>>>
>>>
>>> I have downloaded and installed the Windows client version 2.0.0-98 onto
>>> several of our workstations and have
>>>
>>> gone through the motions of trying to connect to the remote server. The
>>> connection appears to succeed, but then
>>>
>>> suddenly fails with the following output appearing in the Details screen:
>>>
>>>
>>>
>>> NX> 203 NXSSH running with pid: 3672
>>>
>>> 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: 132.183.12.206 on port: 22
>>>
>>> NX> 202 Authenticating user: nx
>>>
>>> NX> 208 Using auth method: publickey
>>>
>>> NX> 204 Authentication failed.
>>>
>>>
>>>       
>> Surely this is quite clear - you have the wrong ssh key
>>
>> Perhaps you had created you own keys ( therefore in both the client and
>> server) , but with the upgrades they have reverted at the server end to
>> the 'nx' default keys
>> ________________________________________________________________
>>      Were you helped on this list with your FreeNX problem?
>>     Then please write up the solution in the FreeNX Wiki/FAQ:
>>   http://openfacts.berlios.de/index-en.phtml?title=FreeNX_FAQ
>>          Don't forget to check the NX Knowledge Base:
>>                  http://www.nomachine.com/kb/
>>
>> ________________________________________________________________
>>        FreeNX-kNX mailing list --- FreeNX-kNX at kde.org
>>       https://mail.kde.org/mailman/listinfo/freenx-knx
>> ________________________________________________________________
>>
>>     
> ________________________________________________________________
>      Were you helped on this list with your FreeNX problem?
>     Then please write up the solution in the FreeNX Wiki/FAQ:
>   http://openfacts.berlios.de/index-en.phtml?title=FreeNX_FAQ
>          Don't forget to check the NX Knowledge Base:
>                  http://www.nomachine.com/kb/ 
>
> ________________________________________________________________
>        FreeNX-kNX mailing list --- FreeNX-kNX at kde.org
>       https://mail.kde.org/mailman/listinfo/freenx-knx
> ________________________________________________________________
>