Forum / NoMachine for Mac / Clean install – “Authentication failed, please try again”
Tagged: authentication failed.
- This topic has 17 replies, 6 voices, and was last updated 8 years, 8 months ago by bakhtadze.
-
AuthorPosts
-
January 5, 2016 at 09:22 #9553jonbelangerParticipant
Updated to 5.0.58.
The entire error is “Authentication failed, please try again. When joining a domain, don’t forget to
specify the username as domain\user.”This is on a clean install of El Capitan. It prompts to add the SSH fingerprint then prompts for password. I give it the same user/passwd as I use to log into the system. I can use the NX client on the server to connect to other systems running NoMachine 5 with no problem, I can also use the NX client on the client sytem to connect to other systems.
What to check?
January 7, 2016 at 09:03 #9566CatoParticipantHello jonbelanger,
Please, answer the following questions:
1. Could you authenticate with the same account on troublesome host using previous NoMachine versions? If so, which version worked for you?
2. Are you using NX or SSH protocol? Does changing the protocol help?
3. Can you authenticate on El Captain server using other account?
4. Can you authenticate on El Captain host using other SSH client?
Logs will be also helpful. Reproduce the problem and gather logs according to https://www.nomachine.com/DT07M00098. Send them to forum[at]nomachine[dot]com.
January 8, 2016 at 09:31 #9586jonbelangerParticipant1. Could you authenticate with the same account on troublesome host using previous NoMachine versions? If so, which version worked for you?
I didn’t use Version 4 at all, but I WAS able to run version 5 everywhere on all of my Linux, OS X and Windows systems for a brief time, I couldn’t say which version.
One day it just stopped allowing me to login from Linux to OS X or from Windows to OS X. All other combinations are fine, and OS X can connect anywhere.
I figured I did something to the laptop, but not I’m starting on a brand new laptop with a default install. — actually it’s connected to the domain using Centrify so this is a domain user, but otherwise a local user in all other respects. I also tried a default local admin and that also does not work
2. Are you using NX or SSH protocol? Does changing the protocol help?
Definitely always NX — SSH does not work with the free version right?
3. Can you authenticate on El Captain server using other account?
I have a local admin that also does not work, but I can SSH.
4. Can you authenticate on El Captain host using other SSH client?
Yes, no problem with the same username and password I am using for both test accounts.
January 8, 2016 at 11:31 #9592CatoParticipantHi jonbelanger,
The direct reason of authentication failure is crash of nxexec process. Can you send us the crash report?
You should find it in ‘/Library/Logs/CrashReporter’.January 8, 2016 at 17:12 #9597jonbelangerParticipantI don’t see anything in /Library/Logs/CrashReporter with a recent enough date to correspond to the crashes in the NX logs. I believe it was crashing on the previous system as well, from what I remember when I looked at the logs. They were both MacBookPro systems (old one was mid-2010), new one is brand new. Old system had OS X 10.9 or 10.10, new system has OS X 10.11.2. Both have Centrify. I can’t think of any other difference with a normal default machine.
What should I do to generate a crash report log?
January 14, 2016 at 10:34 #9642jonbelangerParticipantIs there a way to generate a crash report log for NX? Thanks for the help.
January 22, 2016 at 19:10 #9742brotechParticipantHello,
please take a look at /LibraryLogs/DisagnosticReports directory for nxexec’s crash report, and send to us. If you’re not able to find the crash report, information about location of such report is stored in /var/log/system.log.
We’ve started an investigation regarding support for Centrify. This could be provoking this weird behaviour in nxexec.
February 17, 2016 at 09:58 #10097norbertParticipantHi there,
I have the same issue. Have you been able to find a solution?
February 22, 2016 at 10:12 #10167BritgirlKeymasterhttps://www.nomachine.com/TR01N06379
Please use the ‘notify me’ alert to know when a fix has been released.
March 11, 2016 at 09:29 #10521norbertParticipantWe installed 5.1.7 on OS X 10.11.2 and are still seeing this issue. Anything else we need to do? We can send over logs if that will help.
March 11, 2016 at 11:49 #10534BritgirlKeymasterThis could well be an error from something different. We would need to see the logs from nxerrors which is here: /Library/Application Support/NoMachine/var/log/. Can you send them to forum[at]nomachine[dot]com or attach them here if they are not too big.
March 14, 2016 at 11:22 #10549BritgirlKeymasterAlso, can you send us the crash report? You should find it in ‘/Library/Logs/CrashReporter’.
March 15, 2016 at 15:47 #10565norbertParticipantHi,
Thanks for the prompt reply. I’ve set notify me of followups so I can reply faster as well. The requested files are attached.
March 15, 2016 at 15:49 #10569March 16, 2016 at 12:36 #10575norbertParticipantdone
-
AuthorPosts
Closed because the user did not provide further feedback. Please notify us if you confirm that it is resolved or open a new topic if you have the same problem.