Forum / NoMachine for Linux / Authentication failed
Tagged: authentication, NIS
- This topic has 10 replies, 4 voices, and was last updated 11 years ago by iceback.
-
AuthorPosts
-
November 12, 2013 at 01:11 #656icebackParticipant
NoMachine – Version 4.0.352
Red Hat Enterprise Linux Server release 6.4 (Santiago)
Linux stability.med.utah.edu 2.6.32-358.23.2.el6.x86_64 #1 SMP Wed Oct 16 11:16:45 PDT 2013 x86_64 x86_64 x86_64 GNU/LinuxThe server appears to be installed correctly (all NX> 700 Result: OK in install log) and happily idleing along but I cannot connect from client on same machine. I’ve tried “localhost” and the actual ip of my machine. (I would like to start a session at work and be able to join that session at home. I’ve done this in the past with 3.5 (and earlier))
All I get in the client connect window is “Authentication failed, please try again.” I’m cannot locate the login failure in any log file.
sudo /usr/NX/bin/nxserver –userauth rob
NX> 139 NX user DB is: off
NX> 139 NX password DB is: off.
NX> 139 Authentication for user: rob is: system.And I’ve tried the password enough to be pretty sure it’s correct
Where to now?
November 12, 2013 at 18:41 #674icebackParticipantI should note that NIS (aka yp) is in play and answers login call for my machine. Home directory is on local physical disk
November 13, 2013 at 11:13 #682BritgirlKeymasterI should note that NIS (aka yp) is in play
Yes, indeed the auth method used can be a useful detail when having to investigate a login failure.
Our test team is re-checking NIS auth and will let you know.
November 13, 2013 at 17:40 #685icebackParticipantThanks for the update. If there are any other pertinent details I’ve neglected, please let me know. Otherwise, standing by.
November 18, 2013 at 06:36 #781VirtualNobodyParticipantI’m having the same problem on Fedora 19, local accounts only, no NIS. Sometimes I can log in, sometimes I can’t. Really intermittent.
Also, when I do manage to connect, it keeps asking me every time what I want to do about the audio device, pass through or not…
I think I’m going back to NM 3.5 until 4 stabilizes a bit more.
November 18, 2013 at 14:32 #790Dan25ParticipantIceback, is it possible for you to manually update the client side installation to -366? Tests show that NIS authentication works out of the box. -365 fixed a minor bug which could be what you are encountering https://www.nomachine.com/TR11K04017.
November 18, 2013 at 14:47 #793BritgirlKeymasterI’m having the same problem on Fedora 19, local accounts only, no NIS. Sometimes I can log in, sometimes I can’t. Really intermittent.
Also, when I do manage to connect, it keeps asking me every time what I want to do about the audio device, pass through or not.
VirtualNobody, this seems to be a different problem. I’ve opened a new topic: https://www.nomachine.com/forums/forums/topic/intermittent-login-on-fedora-19
November 18, 2013 at 21:04 #798icebackParticipantRoger that. Will update local installation and report back. Thanks.
November 19, 2013 at 00:13 #806icebackParticipantOK. That was exciting
I learned I was using “Oracle Linux” along the way, and just how precarious python setup scripts can be. But I can login. The problem now is that I get an infinite cascade of nx session windows (just one session). Keep in mind I’m connecting a client to a server on one physical machine.
Do we want a new ticket? What can I supply? Even a screen shot might be tricky…
November 19, 2013 at 20:50 #818icebackParticipantWell since it’s so cool I just had to share.
Attachments:
November 20, 2013 at 01:08 #822icebackParticipantClose this. RESOLVED. I didn’t realize that NX was now connecting to the root window. So my old habit of connecting to self at server then reconnecting from home is no longer necessary. Yippeeee.
So it’s now impossible to do what I used to do, but that’s probably a good thing.
Thanks. (I did need the new build for what ever reason..)
Cheers,
-
AuthorPosts
This topic was marked as solved, you can't post.