LinuxQuestions.org
LinuxAnswers - the LQ Linux tutorial section.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Software
User Name
Password
Linux - Software This forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.

Notices

Reply
 
Search this Thread
Old 02-28-2009, 02:15 PM   #1
libox
LQ Newbie
 
Registered: Feb 2009
Posts: 3

Rep: Reputation: 0
Nomachine NX server Auth problems


Hi, please help to solve:

I am using Fedora 10

installed !M NxServer 3.3.0-15 LFE, but i cant connect to it.

I can ssh to my linux box from the client machine (Windows).

when I do (as root) nxserver --useradd adminos

I get:


[root@libox keys]# nxserver --useradd adminos
NX> 801 User: adminos uses SSHD authentication.
NX> 900 Adding public key for user: adminos to the authorized keys file.
NX> 900 Verifying public key authentication for NX user: adminos.
NXSERVER - Version 3.3.0-15 - LFE
Sat Feb 28 21:11:51 2009 running as user: 'root' (uid: 0, pid: 5591) on 'libox'
Info: selected user 'adminos' is authenticated (NXNodeExec)
Info: password for selected user is in 'unknown' mode (NXNodeExec)
Info: preferred auth method is '' (NXNodeExec)
Info: selected NX Node with host name '127.0.0.1', port '22' (NXNodeExec)
Info: selected su to access NX Node (NXNodeExec)
Info: nxssh command line is 'su adminos -c /usr/NX/bin/nxnode' (NXNodeExec)
Info: nxssh child pid is: 5624 (NXNodeExec)
Info: received data in out channel from NX Node: 'NX> 1000 NXNODE - Version 3.3.0-12
' (NXNodeExec)
Info: received message 'CONNECTED' from NX Node (NXNodeExec)
Info: sent request for service 'setkey' to NX Node (NXNodeExec)
Info: no parameter to send to NX Node (NXNodeExec)
Info: received data in out channel from NX Node: 'NX> 716 Public key is already present in: /home/adminos/.ssh/authorized_keys2.
' (NXNodeExec)
Info: received data in out channel from NX Node: 'NX> 1001 Bye.
' (NXNodeExec)
Info: received message 'BYE' from NX Node (NXNodeExec)
Info: closing nxssh's in, out, err FDs (flagfinished is: 1) (NXNodeExec)
Info: connection to NX Node finished correctly (NXNodeExec)
Info: selected user 'adminos' is not authenticated no password available (NXNodeExec)
Info: preferred auth method is 'publickey' (NXNodeExec)
Info: selected NX Node with host name '127.0.0.1', port '22' (NXNodeExec)
Info: selected publickey method to login NX Node (NXNodeExec)
Info: nxssh command line is '/usr/NX/bin/nxssh -nxservermode -l adminos 127.0.0.1 -p 22 -x -2 -i /usr/NX/etc/keys/node.localhost.id_dsa -o 'PubkeyAuthentication yes' -o 'RSAAuthentication yes' -o 'RhostsAuthentication no' -o 'PasswordAuthentication no' -o 'RhostsRSAAuthentication no' -o 'StrictHostKeyChecking no' /usr/NX/bin/nxnode' (NXNodeExec)
Info: nxssh child pid is: 5651 (NXNodeExec)
Info: received data in err channel from NX Node: 'ssh: connect to host 127.0.0.1 port 22: Connection refused
' (NXNodeExec)
Info: NX Node out channel was closed (NXNodeExec)
Info: NX Node err channel was closed (NXNodeExec)
Info: closing nxssh's in, out, err FDs (flagfinished is: 0) (NXNodeExec)
Error: no 'CONNECTED' message from NX Node (NXNodeExec)
NX> 595 ERROR: A fatal error occurred in NX Server.
NX> 595 ERROR: The exception id is: F7D4C5A0. To get detailed information about
NX> 595 ERROR: the error search for the string F7D4C5A0 in the system log
NX> 595 ERROR: file (usually '/var/log/messages').
NX> 500 ERROR: Last operation failed.


system log entries:

[root@libox keys]# tail -1000 /var/log/messages | grep F7D4C5A0
Feb 28 21:11:51 localhost NXSERVER-3.3.0-15[5591]: ERROR: (exception id F7D4C5A0) Error: no 'CONNECTED' message from NX Node
Feb 28 21:11:51 localhost NXSERVER-3.3.0-15[5591]: ERROR: (exception id F7D4C5A0) ssh: connect to host 127.0.0.1 port 22: Connection refused#015
Feb 28 21:11:51 localhost NXSERVER-3.3.0-15[5591]: ERROR: (exception id F7D4C5A0) NXNodeExec::exec('ping', '', 127.0.0.1, 22, 'adminos', 'publickey') called at handlers/nxserver.pl line 7419
Feb 28 21:11:51 localhost NXSERVER-3.3.0-15[5591]: ERROR: (exception id F7D4C5A0) NXShell::handler_user_checklogin('adminos') called at NXShell.pm line 373
Feb 28 21:11:51 localhost NXSERVER-3.3.0-15[5591]: ERROR: (exception id F7D4C5A0) NXShell::handle_command('checklogin', 'adminos') called at handlers/nxserver.pl line 7196
Feb 28 21:11:51 localhost NXSERVER-3.3.0-15[5591]: ERROR: (exception id F7D4C5A0) NXShell::handler_user_add('username', 'adminos', 'system', 0, 'administrator', undef, 'uid', undef, ...) called at NXShell.pm line 373
Feb 28 21:11:51 localhost NXSERVER-3.3.0-15[5591]: ERROR: (exception id F7D4C5A0) NXShell::handle_command('adduser', 'username', 'adminos', 'system', 0, 'administrator', undef, 'uid', ...) called at nxserver.pl line 5263
Feb 28 21:11:51 localhost NXSERVER-3.3.0-15[5591]: ERROR: (exception id F7D4C5A0) main:arse_args called at nxserver.pl line 4429
Feb 28 21:11:51 localhost NXSERVER-3.3.0-15[5591]: ERROR: (exception id F7D4C5A0) eval {...} called at nxserver.pl line 4426
[root@libox keys]#
 
Old 02-28-2009, 02:20 PM   #2
libox
LQ Newbie
 
Registered: Feb 2009
Posts: 3

Original Poster
Rep: Reputation: 0
nxserver --userlist - returns empty list.
nxserver --usercheck adminos - will post on request, but also finishes with exception.
 
Old 03-25-2009, 09:10 PM   #3
dshravankumar
LQ Newbie
 
Registered: Mar 2009
Posts: 1

Rep: Reputation: 0
Hello libox,

Were you able to resolve this issue ? I am also having the same problem. Could you please advice ?

Thanks,
SKD
 
Old 04-09-2009, 09:29 PM   #4
libox
LQ Newbie
 
Registered: Feb 2009
Posts: 3

Original Poster
Rep: Reputation: 0
hi,

I did solve the issue and as far as I can remember now, it was a messed up ssh configuration.
Sorry, can't really recall what was the problem.
 
Old 11-01-2011, 06:24 PM   #5
santizar
LQ Newbie
 
Registered: Nov 2011
Posts: 1

Rep: Reputation: Disabled
I know this is an old thread, however, I found this thread while trying to track down the answer. The issue I found was that the hostname was not added to the /etc/hosts file. Once I added the hostname, NX worked fine.
 
Old 10-08-2013, 01:47 PM   #6
gosu
LQ Newbie
 
Registered: Oct 2013
Posts: 1

Rep: Reputation: Disabled
Lightbulb

I got same problem but I found that my linux password has been expired, once I change my password, nomachine started working as usual. Hope this may help someone looking for answer.

Thanks,
 
  


Reply

Tags
fedora, nx


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
LXer: Xandros bundles NoMachine thin-client server LXer Syndicated Linux News 0 07-18-2007 01:01 PM
NoMachine NX Server not working Mepis 6.5 hexstar Linux - Software 4 06-29-2007 01:25 PM
Nomachine/freenx server netcrusher88 Debian 1 12-14-2005 03:53 AM
Server auth Drunkalot Linux - General 2 09-26-2005 11:05 AM
Central Auth. Server Data-Base Linux - Networking 2 06-17-2004 01:00 PM


All times are GMT -5. The time now is 01:34 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration