> Not allowing to gain contol over the machine locally while the remote user is connected was intended as it seemed the safest choice.
Well, you should ask for a password of course 😉
Seriously, it should always be possible to regain control on the host machine. And it should “just work”. How should I know, that I can connect with another NoMachine to disconnect the first session, leave alone the command line commands? What if I have no other machine around? And if it is “any” machine, then I’d most likely have to install NoMachine first. What if the network is broken? What if NoMachine got stuck in some weird state while locked? What if… there are plenty of reasons why one needs to be able to always (force) unlock locally.
Your suggestions how to unlock might probably work, but they are not exactly intuitive…
Unfortunately that is not possible with the NoMachine free version, since it only allows to share the physical desktop. In other words, it is not possible to show a login dialog to the local user and, at the same time, the desktop to the remote user.
What you would need is the Workstation for Linux. That way you can run a virtual Linux desktop session, so 1 ) no one will be able to see what you are doing and 2) you won’t need to blank the screen and worry about not having remembered to disconnect from the physical desktop.
This post has been closed to avoid confusion between numerous questions in one topic. Please follow the TR links if you have reported an issue that we have also been able to reproduce. If your question is about a separate issue, please submit a new topic.