Authentication Failure while Connecting to NXServer
Hello All,
I am having trouble connecting to a Fedora 16 Server using NX Client for Windows 7. It gives the following error:
Code:
NX> 203 NXSSH running with pid: 7124
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: 192.168.1.149 on port: 22
NX> 202 Authenticating user: nx
NX> 208 Using auth method: publickey
NX> 204 Authentication failed.
followed by this:
Code:
The NX service is not available or the NX access was disabled on host 192.168.1.149.
When I run the "nxserver -- status" command I get the following:
Code:
NX> 100 NXSERVER - Version 1.5.0-61
NX> 900 Connecting to server ..
NX> 204 Authentication to NX server failed.
NX> 110 NX Server is stopped
NX> 999 Bye
But when I try to start it, it says the service is already running!
Code:
NX> 100 NXSERVER - Version 1.5.0-61
NX> 500 ERROR: Service already running
NX> 999 Bye
This doesn't make a lot of sense. The two computers on the same local network. I used the instructions on CentWiki for setting up the NXServer.
Anyone know what the problem may be? I am guessing this is related to NX Authentication somehow.
Hi,
I am using gmake to compile a c program with a makefile. The make file runs ld. I get the following error
jsh1035c:/users/egate453/admegate/kapil/samples $ gmake -e -f GNUmakefile queue_c
gmake -f ./GNUmakefile queue_c in_objdir=1 build_root=/users/egate453/admegate/kapil/samples... (2 Replies)
I am new to being a Unix admin and have a question about replacing some hardware. I have a K class box using HP-UX 10.20 with three disks. Two of the drives are in one logical volume. Every 3 or 4 days, the syslog is showing that one of these drives is experiencing "POWERFAILED" and then recovering... (6 Replies)
I am using an ssh pub key on two remote servers to allow ssh session without authentication. Both servers have the same id_rsa.pub copied from the host into the remote servers ~user/.ssh/authorized_keys. There is no passphrase for this key either.
The problem is that I am able to ssh into one... (2 Replies)
My PAM module seems to work right but it fails in authentication. Althought it can't authenticate, the session module works and the software who uses it executes well.
For example, when I login through "gdm" using pam to authenticate against an ldap server
/var/log/auth.log shows
Any... (1 Reply)
Usually when su rejects an attempt to switch user it responds with "Sorry" but with a certain username on some unix servers the response is "Killed". I'm guessing the su accepted the username/password but refused to spawn child shell with the specified username. What's causing this and what has to... (8 Replies)
hi,
i´ve been the last 48 hours with this issue, this is my last resort....
after clone another system to a new one with lvm, the last step is mkinitrd.
i execute it and it finish, but some errors are sent to stderrr.
/sbin/mkinitrd: line380: gawk: command not found
Traceback (most... (2 Replies)
Ssh connections using shared public keys issue “authentication failure” messages, then succeed with “session opened”.
I have found a few other threads with similar issue, but no solutions offered. :wall:
How can I eliminate the failure messages?
Environment:
$ uname -a Linux... (0 Replies)
I was bogged with an error “Authentication Failure” for all of my cron jobs in Linux Ubunutu.
root@Test:~# tail -f /var/log/syslog | grep cron
Dec 11 16:38:01 Test cron: Authentication failure
Dec 11 16:38:01 Test cron: Authentication failure
Dec 11 16:38:09 Test cron: (CRON) INFO (pidfile... (1 Reply)
Dear all,
I noticed in syslog that i receive authentication failure from cron:
Mar 11 23:19:01 s1 CRON28789]: Authentication failure
Mar 11 23:19:01 s1 cron: Authentication failure
Mar 11 23:19:01 s1 cron: Authentication failure
Mar 11 23:19:01 s1 CRON: Authentication failure
Mar 11... (3 Replies)
Discussion started by: mydove
3 Replies
LEARN ABOUT SUSE
sasl_errors
sasl_errors(10 July 2001) sasl_errors(10 July 2001)
NAME
sasl_errors - SASL error codes
SYNOPSIS
#include <sasl/sasl.h>
DESCRIPTION
The following are the general error codes that may be returned by calls into the SASL library, and their meanings (that may vary slightly
based on context):
Common Result Codes
SASL_OK Success
SASL_CONTINUE
Another step is needed in authentication
SASL_FAIL
Generic Failure
SASL_NOMEM
Memory shortage failure
SASL_BUFOVER
Overflowed buffer
SASL_NOMECH
Mechanism not supported / No mechanisms matched requirements
SASL_BADPROT
Bad / Invalid Protocol or Protocol cancel
SASL_NOTDONE
Can't request information / Not applicable until later in exchange
SASL_BADPARAM
Invalid Parameter Supplied
SASL_TRYAGAIN
Transient Failure (e.g. weak key)
SASL_BADMAC
Integrity Check Failed
SASL_NOTINIT
SASL library not initialized
Client-only Result Codes
SASL_INTERACT
Needs user interaction
SASL_BADSERV
Server failed mutual authentication step
SASL_WRONGMECH
Mechanism does not support requested feature
Server-only Result Codes
SASL_BADAUTH
Authentication Failure
SASL_NOAUTHZ
Authorization Failure
SASL_TOOWEAK
Mechanism too weak for this user
SASL_ENCRYPT
Encryption needed to use mechanism
SASL_TRANS
One time use of a plaintext password will enable requested mechanism for user
SASL_EXPIRED
Passphrase expired, must be reset
SASL_DISABLED
Account Disabled
SASL_NOUSER
User Not Found
SASL_BADVERS
Version mismatch with plug-in
SASL_NOVERIFY
USer exists, but no verifier for user
Password Setting Result Codes
SASL_PWLOCK
Passphrase locked
SASL_NOCHANGE
Requested change was not needed
SASL_WEAKPASS
Passphrase is too week for security policy.
SASL_NOUSERPASS
User supplied passwords are not permitted
CONFORMING TO
RFC 2222
SEE ALSO sasl(3)SASL man pages SASL sasl_errors(10 July 2001)
06-17-2012
Authentication Failure while Connecting to NXServer