Can’t login “Authentication failed, please try again.”

Forums / NoMachine for Linux / Can’t login “Authentication failed, please try again.”

Viewing 15 posts - 31 through 45 (of 60 total)
  • Author
    Posts
  • #26330
    AvatarZenith
    Participant

    So I DO need to change the SessionLogLevel to 7 in the server.cfg and node.cfg files and SessionLogClean 0 in the node.cfg file?

    Also, since the update tab is under ‘Server preferences’ this still represents the player version (as well)? In that case it’s indeed version 6.9.2

    #26333
    AvatarBritgirl
    Keymaster

    So I DO need to change the SessionLogLevel to 7 in the server.cfg and node.cfg files and SessionLogClean 0 in the node.cfg file?

    Yes – remember you need to do this on the Linux server host.

    Also, since the update tab is under ‘Server preferences’ this still represents the player version (as well)? In that case it’s indeed version 6.9.2

    Yes

    #26397
    Avatardanietech
    Participant

    Hi all,

    I don’t wish to intrude, I have been searching through to get a solve for what seems to be a possible lack of understanding on my part, however I came across this wonderful to and fro, regarding what seems to be a problem I am finding a little perplexing myself and after reading through a very simpler issue.

    NoMachine seems like a simple way of installing on Linux in my case Linux MX and the host or server for want of a better word and my client machine Windows 10.

    On both VM’s i have updated, strangely enough it did not occur to me to monitor the logs upon install as it seems all to easy, after the install just like (removed) rdp or (removed), I imagined I would have to enter the appropriate user names  passwords not the case, NoMachine does a search and populates the program with the available connected devices on the locate network, well I was pleased as punch, I clicked on the user and enter the correct details for my user and password and well nothing the failed login on about oh more than whats seems to be 100 times clearly my definition of madness.

    I clearly need some direction on this, but it does sound to be a comment problem, to which i am very curious to get to the bottom off with a little help, any help would be much appreciated….

     

     

    #26458
    Avatarfisherman
    Moderator

    Hello,

    Please can you try with following information:

    1. Check with terminal SSH.
    2. Check with nxplayer + SSH.
    3. Check what happens when /etc/pam.d/sshd is reused for /etc/pam.d/nx (backup of nx file first).
    4. What’s inside /var/log/auth.log (run as root grep -r "nxexec" /var/log/auth.log and share the output).
    5. If nothing helps, send us new set of NoMachine server logs with debug enabled, /var/log/auth.log (or at least nxexec lines), and content of /etc/pam.d
    #26881
    Avatarwsilva32
    Participant

    I had this same issue and realized I was installing the wrong architecture package for Linux. My machine was amd64 but I had installed the i386 package. No errors were detected by installation so took me a while to figure out.

    #26939
    AvatarZenith
    Participant

    Hey wsilva32,

    Thanks for your reply. I’m a Linux newbie, so I might have done the same. How did you install NoMachine on your Linux machine? That way I can check and compare if I did something wrong as well 🙂

    Thanks in advance!

    #26953
    AvatarZenith
    Participant

    To be more precise, I did it like this:

    $ cd /usr
    $ sudo tar xvzf nomachine_4.0.369_1_x86_64.tar.gz
    $ sudo /usr/NX/nxserver –install

    I have a i5-2400 and run Linux Mint 19.2 Tina Cinnamon (64 bit). So that tar.gz seems to cover both 32 and 64 bit packages it seems. Please let me know if I used the right version 🙂

    #26964
    Avatarwsilva32
    Participant

    Ah I’m running Ubuntu so I used the debian package like so,

    $ sudo dpkg -i nomachine_6.9.2_1_amd64.deb

    Any reason you’re installing an older version?

    #26965
    AvatarBritgirl
    Keymaster
    $ cd /usr
    $ sudo tar xvzf nomachine_4.0.369_1_x86_64.tar.gz
    $ sudo /usr/NX/nxserver --install

    Looks like you’re installing an old version there Zenith. Version 4 is no longer supported.

    Just to clarify:
    for 32 bit systems install this on the server or client side: https://www.nomachine.com/download/download&id=2

    for 64 bit systems install this on the server or client side: https://www.nomachine.com/download/download&id=3

    If you install a 32-bit on 64-bit hardware, the installation can complete with warnings and there will be errors in the logs.

    Zenith, if you are still having problems with authentication and you have indeed the latest version installed on both the client and server sides, can you submit the logs like I requested the other week? Enable debug, reproduce the problem and gather the logs and send them as you did before.

    Otherwise, if you no longer have problems authenticating, I will close this topic.

    #26973
    AvatarZenith
    Participant

    I had no clue I installed an old version. Tomorrow I will try the new version and see if the authenticating works now. If so, I will obviously mention that here.

    #26986
    AvatarZenith
    Participant

    It still doesn’t work, so I’ll send the log and debug files. I ran these two commands:

    sudo /etc/NX/nxserver –debug –collect
    sudo tar cvfz NoMachine-log.tar.gz /usr/NX/var/log

    With the sessionloglevel set to 7 and sessionlogclean to 0 (zero). If you need any more information, please let me know.

     

    #26988
    AvatarBritgirl
    Keymaster

    Logs show that you are now logging in with a username oem@Zenith which doesn’t exist.

    2020-04-23 15:03:05 047.001 20656 NXSERVER WARNING! User oem@Zenith doesn't exist in system.
    2020-04-23 15:03:05 047.172 20656 NXSERVER WARNING! NXLogin: Cannot retrieve absolute username for user: oem@Zenith.
    2020-04-23 15:03:05 047.419 20656 NXSERVER WARNING! User oem@Zenith doesn't exist in system.
    2020-04-23 15:03:05 047.715 20656 NXSERVER Previous message repeated 1 time
    2020-04-23 15:03:05 047.792 20656 NXSERVER WARNING! NXLogin: Cannot retrieve absolute username for user: oem@Zenith.
    2020-04-23 15:03:05 048.033 20656 NXSERVER WARNING! User oem@Zenith doesn't exist in system.
    2020-04-23 15:03:05 048.149 20656 NXSERVER WARNING! NXLogin: Cannot retrieve absolute username for user: oem@Zenith.
    2020-04-23 15:03:05 048.366 20656 NXSERVER WARNING! User oem@Zenith doesn't exist in system.
    2020-04-23 15:03:05 048.838 20656 NXSERVER Previous message repeated 1 time
    2020-04-23 15:03:05 048.913 20656 NXSERVER WARNING! NXLogin: Cannot retrieve absolute username for user: oem@Zenith.
    2020-04-23 15:03:05 049.183 20656 NXSERVER ERROR! Authentication with 'NX-password' from host '192.168.1.15' failed. Error is 'Wrong password or login'.
    2020-04-23 15:03:14 110.278 20688 NXSERVER ERROR! Authentication with 'NX-password' from host '192.168.1.15' failed. Error is 'Wrong password or login'

    The best way to proceed is to do the following:

    1) in a shell/terminal on the Linux server host, find the username using the command (run it in the terminal):
    whoami

    2) test the username and password in command line on the Linux host:

    $ /usr/NX/bin/nxexec --auth
    Username:  your_username
    Password: your_password

    The best way to check is to use the same credentials you are using to login to that Linux host.
    If you are using oem@zenith then try zenith\oem (format DOMAIN\username). If it’s ‘oem’, then use that.

    If nxexec --auth is successful, it will provide system groups where the user belongs.
    Then you can use these same credentials in the connection GUI to start the connection.

    If nxexec reports an error it means that user username and password are wrong.

    #26999
    AvatarZenith
    Participant

    I also tried ‘oem’ and ‘Zenith’. Last is the machine name I suppose. I will try the other things as soon as I can, thanks!

    #27001
    AvatarZenith
    Participant

    Here are the results:

    oem@Zenith:~$ whoami
    oem
    oem@Zenith:~$ /usr/NX/bin/nxexec --auth
    Username:oem
    Password:
    *********
    User authorized, is member of: oem,adm,cdrom,sudo,dip,plugdev,lpadmin,sambashare.
    oem@Zenith:~$

    I hid my password, but it’s correct. These are the credentials I used from the beginning. So chances are it’s a problem with the client side (my Windows PC)!?

    And strange that the log only mentions ‘oem@Zenith’, because like I said. I tried: oem, oem@Zenith, Zenith, Zenith\oem

    All with the same password, but it all results in the same authentication error.

    I also checked again with a fairly new laptop with a fairly clean install and same error with the correct credentials.

    #27059
    Avatarbrotech
    Participant

    Hello Zenith, can you enable debug on server side using a command executed on your linux host (nxserver side) by root:

    /etc/NX/nxserver --debug --enable server

    or using sudo:
    sudo /etc/NX/nxserver --debug --enable server

    After enabling debug, please connect and login from your connecting client and with user ‘oem’.

    When the problem appears again please share nxserver.log, nxerror.log files from /usr/NX/var/log/ directory and additionally /var/log/auth.log file,
    and attach also server configuration file (/usr/NX/etc/server.cfg).

    All those files please send to forum[at]nomachine[dot]com with subject:
    “cant-login-authentication-failed-please-try-again”

    Reproducing problem with enabled debug should allow us to find a reason for problem.

    Regards

     

     

Viewing 15 posts - 31 through 45 (of 60 total)

You must be logged in to reply to this topic.