On my server I was unable to get the suspend/terminate dialog when trying to close a the nxclient window until I installed xdialog. That should be a dependency (serverside).
I vote that we remove tpowa's note since he hasn't edited the page since 2007. --Bostonvaulter 20:05, 4 September 2009 (EDT)
This page needs some explanatory information.--Misfit138 22:31, 9 April 2008 (EDT)
I second this comment, especially since a crucial part in the setup of the server (adduser) is compeltely missing.--Factory Sat Jul 26 01:21:47 EDT 2008
This page seems dreadfully inadequate. It assumes way too much prior knowledge by the end user.
This page doesn't mention the package in extra/nxserver, only freenx Bostonvaulter 20:17, 19 November 2008 (EST)
I'd like to edit this wiki 'cos as it stands it may have some good complementary info in it but is quite useless otherwise. Who to email and ask for permission? Is it being at all maintained (see first comment above from ten months ago...)? toad 30 January 2009
Sometimes, when the client starts and stops right away without explanation, it helps to delete the .Xauthority file in /home (on the server). Don't know why though. --Rataxes 13:48, 16 August 2009 (EDT)
Infromation about Edit /etc/ssh/sshd_config wrong.
ref. problem 
ref. wiki []
Corrected the custom keys generation and the service startup. --PeGa! 01:27, 16 January 2010 (EST)
It seems PasswordAuthentication needs to be allowed in /etc/ssh/sshd_config Without this I get 'authentication failed' when trying to log in.
Also, If you need it, yes or no, the text should match...
You need to allow RSAauthentication, Password Authentication, and you also need to include nx public keys to Authorizedkeysfile." If you do not want to allow password login globally, add match block at the end of file like below: /etc/ssh/sshd_config: RSAAuthentication yes PubkeyAuthentication yes PasswordAuthentication no