Forum / General Discussions / NoMachine shows remote desktop, but login failed
Tagged: but login failed, show remote desktop
- This topic has 4 replies, 2 voices, and was last updated 3 years, 8 months ago by eh2006re.
-
AuthorPosts
-
February 24, 2021 at 18:22 #32137eh2006reParticipant
Hello,
I recently installed NoMachine 7.1.3 on my Windows 10 laptop, also installed on one of my Linux (Elementary OS 5.1 Hera) machine with
sudo dpkg -i ./nomachine_7.1.3_1_amd64.deb
. From my laptop, I can get my remote Linux login screen, also can type my password and hit return, but the login just gets me nowhere, see attached screenshots.Use the same user password from [removed], I can easily log in to my Linux machine.
Does anyone have some suggestion? Welcome and appreciate your input.
Thanks
Attachments:
February 26, 2021 at 15:23 #32172CatoParticipantHello eh2006re,
Does your password contain any non-latin characters? Do you use any other than QWERTY keyboard layout? Can you find anything relevant in system’s authentication logs after failed authentication attempt? Authentication logs are usually written to /var/log/auth.log or /var/log/secure files, depending on Linux distribution.
March 1, 2021 at 09:23 #32180eh2006reParticipantHello, Cato
My password has # as one special character, nothing else.
My keyboard is standard UK layout ( Dell keyboard KB212-B ). Search /var/log/auth.log, around the time of 2021/02/24/12:45, I found some authentication failure. See below.
Any suggestion?
I do noticed that if I try to login into my home Linux PC, NoMachine works. I can log in from remote login screen.
vlt2016xg1 is a Linux machine within my organization’s firewall and I have VPN started.
Thanks for your time.
>>>>>>>>>>>>>>>>
Feb 24 12:44:28 vlt2016xg1 systemd-logind[544]: New session c6 of user xg.
Feb 24 12:45:39 vlt2016xg1 lightdm: pam_unix(lightdm:auth): authentication failure; logname= uid=0 euid=0 tty=:0 ruser= rhost= user=xg
Feb 24 12:45:42 vlt2016xg1 lightdm: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory
Feb 24 12:45:42 vlt2016xg1 lightdm: PAM adding faulty module: pam_kwallet.so
Feb 24 12:45:42 vlt2016xg1 lightdm: PAM unable to dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.so: cannot open shared object file: No such file or directory
Feb 24 12:45:42 vlt2016xg1 lightdm: PAM adding faulty module: pam_kwallet5.so
Feb 24 12:45:42 vlt2016xg1 lightdm: pam_succeed_if(lightdm:auth): requirement "user ingroup nopasswdlogin" not met by user "xg"
Feb 24 12:46:55 vlt2016xg1 lightdm: pam_unix(lightdm:auth): authentication failure; logname= uid=0 euid=0 tty=:0 ruser= rhost= user=xg
Feb 24 12:46:57 vlt2016xg1 lightdm: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory
Feb 24 12:46:57 vlt2016xg1 lightdm: PAM adding faulty module: pam_kwallet.so>>>>>>>>>>>>>
March 4, 2021 at 18:39 #32252CatoParticipantHello eh2006re,
Does the server-side keyboard layout match the one on the client-side? The most likely scenario is some kind of input mismatch between characters you type in your client and what is printed to the password field on the server. This could be due to the different mappings of keyboard keys between hosts. To verify if this is the case: start NoMachine connection to your Elementary server and type your password to some field in which cleartext input is printed. This can be a username field or password field with the option of visible characters enabled. Check if the password is printed correctly.
March 5, 2021 at 15:41 #32258eh2006reParticipantHello, Cato
thanks for the hint. I have changed the login password without any special characters and remote login works.
Many thanks. Very appreciated.
PS.
Once I log in to my Elementary server, type in a x-terminal, I can not see any difference between my local keyboard and the special characters printed on the terminal. -
AuthorPosts
This topic was marked as solved, you can't post.