FreeNX running failed

Chris Peterman c.peterman at gmail.com
Thu Nov 3 04:17:39 UTC 2005


Why not use the debpack?

wiki.ubuntu.com/FreeNX

~Chris

On Thu, 2005-11-03 at 03:32 +0000, Soo-Hyun Choi wrote:
> Hi,
> 
> I have built FreeNX from the source as directed by
> http://stateless.geek.nz/2005/06/27/building-freenx-04-on-ubuntu-hoary/.
> 
> After installation, I ran 'sudo nxsetup' and got the following error message.
> 
> soohyunc at quokka:~ $ sudo nxsetup
> ------> You did select no action.
>         FreeNX guesses that you want to _install_ the server.
>         Type "y" to abort the installation at this point in time.
>         "N" is the default and continues installation.
>         Use "/usr/sbin/nxsetup --help" to get more detailed help hints.
> 
>  Do you want to abort now? [y/N] n
> ------> It is recommended that you use the NoMachine key for
>         easier setup. If you answer "y", FreeNX creates a custom
>         KeyPair and expects you to setup your clients manually.
>         "N" is default and uses the NoMachine key for installation.
> 
>  Do you want to use your own custom KeyPair? [y/N] ySetting up
> /etc/nxserver ...done
> Setting up /var/lib/nxserver/db ...done
> Setting up /var/log/nxserver.log ...done
> Setting up known_hosts and authorized_keys2 ...done
> Setting up permissions ...done
> 
> ----> Testing your nxserver configuration ...
> Warning: Could not find nxdesktop in /usr/lib/nx. RDP sessions won't work.
> Warning: Invalid value "DEFAULT_X_SESSION=/etc/X11/xdm/Xsession"
>          Users might not be able to request a default X session.
> Warning: Invalid value "COMMAND_START_KDE=startkde"
>          Users will not be able to request a KDE session.
> Warning: Invalid value "COMMAND_START_CDE=cdwm"
>          Users will not be able to request a CDE session.
> Warning: Invalid value "COMMAND_SMBMOUNT=smbmount". You'll not be able
> to use SAMBA.
> Warning: Invalid value "COMMAND_SMBUMOUNT=smbumount". You'll not be
> able to use SAMBA.
> 
>   Warnings occured during config check.
>   To enable these features please correct the configuration file.
> 
> <---- done
> 
> ----> Testing your nxserver connection ...
> The authenticity of host '127.0.0.1 (127.0.0.1)' can't be established.
> RSA key fingerprint is c9:2b:61:84:29:1d:df:ec:a7:5c:d4:9b:3a:56:87:d5.
> Are you sure you want to continue connecting (yes/no)? Fatal error:
> Could not connect to NX Server.
> 
> Please check your ssh setup:
> 
>         - Make sure "nx" is one of the AllowUsers in sshd_config.
>         - Make sure your sshd allows public key authentication.
>         - Make sure your sshd is really running on port 22.
>         - Make sure your sshd_config AuthorizedKeysFile in sshd_config
> is set to authorized_keys2.
> soohyunc at quokka:~ $ Host key verification failed.
> 
> 
> What would be the problem in this case? I have checked that my sshd
> allows Public Key authentication running on Port 22, and
> AuthorizedKeysFile is set to authorized_keys2.
> 
> Thanks,
> 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
URL: <https://lists.ubuntu.com/archives/ubuntu-users/attachments/20051102/5f295bc4/attachment.sig>


More information about the ubuntu-users mailing list