[MIODude]

darn server.cfg.... there are 2 places to change the port.. got it working now

[MIODude]

removed old.. installed the one from nomachine..

when going to connect, got the message about saying my keys.. then got "Unable to authenticate user" right after that.. so still not working..

I don't understand how i can login via ssh, but not NX? what does NX use ?


edit: Ok.. i think i might know the cause.. i changed my ssh port as well... so.. i've modified the nxnode.conf.. and restarted nxserver.. but still getting "unable to authenticate"

[m0z]

Uninstall the FreeNX that comes with the Ubuntu Desktop and install NX Free from nomachine.com

http://www.nomachine.com/select-pack...?os=linux&id=1

apt-get remove freenx-server or something like that

[MIODude]

Auth.log doesn't give me many answers

Aug 22 14:36:10 stock sshd[29126]: Accepted publickey for nx from xx.xx.xxx.xxx port 60094 ssh2
Aug 22 14:36:10 stock sshd[29129]: pam_unix(sshd:session): session opened for user nx by (uid=0)
Aug 22 14:36:12 stock sshd[29129]: pam_unix(sshd:session): session closed for user nx
Aug 22 14:36:33 stock gnome-keyring-daemon[6344]: failed to initialize a HAL context: (null) 
Aug 22 14:36:33 stock gnome-keyring-daemon[6344]: Scheduling hal init retry
Aug 22 14:36:40 stock sshd[29205]: Accepted publickey for nx from xx.xx.xxx.xxx port 60095 ssh2
Aug 22 14:36:40 stock sshd[29208]: pam_unix(sshd:session): session opened for user nx by (uid=0)
Aug 22 14:36:42 stock sshd[29208]: pam_unix(sshd:session): session closed for user nx
Aug 22 14:37:01 stock CRON[29284]: pam_unix(cron:session): session opened for user root by (uid=0)
Aug 22 14:37:01 stock CRON[29284]: pam_unix(cron:session): session closed for user root
Aug 22 14:37:03 stock gnome-keyring-daemon[6344]: failed to initialize a HAL context: (null) 
Aug 22 14:37:03 stock gnome-keyring-daemon[6344]: Scheduling hal init retry

I don't know if the HAL errors are related, as I see them all through my log

Aug 22 14:56:33 stock gnome-keyring-daemon[6344]: failed to initialize a HAL context: (null)
Aug 22 14:56:33 stock gnome-keyring-daemon[6344]: Scheduling hal init retry
Aug 22 14:57:03 stock gnome-keyring-daemon[6344]: failed to initialize a HAL context: (null)
Aug 22 14:57:03 stock gnome-keyring-daemon[6344]: Scheduling hal init retry

Every 30 seconds.. i tried googling it, but found nothing but bug reports.. i removed a bunch of things on the server that are useless for a server (or so I though!)... like bluetooth.. (i don't think my bluetooth devices are going to work this far away).. I thought the OVH ready ubuntu image would have these things removed.
Now.. i removed ACPID as well.... because i kept getting errors about it, and figured it was power management (like i want the server suspending anyways!)

[Myatu]

NX runs over SSH, yes. But it shouldn't require the authorized keys. Check /var/logs/auth.log

[MIODude]

I just installed Ubuntu 8.04. connected fine, successfully setup everything after a new reimage ...
i disconnect then 10 minutes later i go to reconnect, and now i get the error "Unable to authenticate user)..

I can log in fine through putty.... I have a feeling it was me.. i removed the authorized keys in the .ssh folder.. is that what NX Client uses? Please tell me I dont have to reimage yet again!!