May 11, 2022 at 12:22 #38596OilingaParticipant
I connected to a remote device (Linux Mint Client) via NoMachine from my Windows 10 client
It is a bit magic and not clear for me, why NoMachine logged in automatically on the Linux client, with my correct user but not without any password credential? That’s happen always when I performed a restart on my Linux client. I always have to log out and log in again, then everything is fine.
I wish that I can log in on the Linux client with my correct user and password, direct during the first login after an Linux restart. I expect that I come always to the Linux client login screen. I have only created one user on the Linux client. I also log in with this user via NoMachine.
I know it’s a bit difficult to explain but maybe someone knows the phenomenon!
Thanks a lot for your hints!
I use NoMachine rel. 7.9.2May 11, 2022 at 15:25 #38599BritgirlKeymaster
When connecting to a Linux desktop and after having inserted the login details in the NoMachine’s authentication dialog, NoMachine does one of the following two things.
1) it detects that a physical display is running on the Linux computer and it connects you to its login window. The display manager dialog requires you to insert your username and password and you are then connected.
2) it DOESN’T detect a display running (e.g it might be headless) and NoMachine then asks “Cannot detect any display running. Do you want NoMachine to create a new display and proceed to connect to the desktop?”. You then click “yes” and you are connected to a virtual desktop which does NOT require further authentication.
In your case you are experiencing both these cases. After a restart NoMachine is not detecting the display and therefore if you have saved your username and password in the NoMachine login dialog, you won’t be prompted to insert them again i.e the display manager does not issue a login dialog. Other times you connect, NoMachine detects that a physical display exists and therefore connects you to it. You are presented with a login dialog by your Linux Mint system.
That’s the explanation and it is happening because your local Linux session is probably still starting when you try to connect with NoMachine 🙂
Perhaps you could give a few more seconds to your system after a reboot before connecting with NoMachine? For example, when NoMachine tells you “Cannot detect any display running. Do you want NoMachine to create a new display and proceed to connect to the desktop?”, select ‘No’ and try connecting again.
You must be logged in to reply to this topic.