- This topic has 2 replies, 2 voices, and was last updated 7 years, 10 months ago by
.
-
Posts
-
After I setup a new AWS EC2 instance, install NoMachine and a desktop environment, then setup NX based private key authentication I am able to connect to my remote machine with NX and use it normally. I can close the window and re-open the session without any issues. However, once I restart the machine I have problems. After restarting when I try to connect it takes me to a lock screen which displays a list of users and if I click on one it prompts me for a password. Since we don’t allow password login for our remote users and instead require key based auth none of the users have passwords setup and I would like to continue using key based authentication on the NX protocol. I have included the required information below, I have also tried the same thing on Ubuntu 16.04 with the exact same results.
Local NoMachine: Version 5.1.62 (5.1.62)
Remote NoMachine: Free Debian Version 5.1.62-1
Remote OS: Debian Jessie 8.6 with Gnome desktop
Local OS: Mac OSX 10.12.2
NoMachine allows you to view the display server to which you are connecting. This makes it possible to connect to the desktop of another user. If you restart your PC you will see the login screen with user accounts created on this machine. NoMachine does not log on to the system as user, it checks the user privileges to show you the system display.
Do you want users to access a common desktop or should each user have access to only one virtual machine? If the latter, maybe a solution for you is to set “Automatic login” on this machine. Then after restarting, when you connect to this machine you will see the logged user’s desktop only.
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.