November 19, 2019 at 17:36 #24526
The NoMachine FAQ says it is possible on Linux to share a local/phyiscal desktop session with a remote user using the free NoMachine edition.
I installed free NoMachine on two KDE Neon systems and I am able to access the remote system by entering a user name and a password. A new session seems to be created for that user, like for a terminal server.
But what if a local user sits in front of the PC and I want to support the user by accessing his existing desktop session? I do not know his password, so I can not enter a username and a password.
How can a local user share the existing desktop session with a remote user using the NoMachine free edition?November 20, 2019 at 09:42 #24529
See the FAQ here:
How do I share my desktop with another user if I have the free version installed?
https://www.nomachine.com/AR10K00703November 22, 2019 at 09:02 #24539
I have read that before. Forgive me, but I do not understand that FAQ entry.
It says “free version”. Somewhere else I have read that I need a non-free Enterprise Server software on the local machine. Is that other information outdated? Will physical desktop sharing actually work with free versions installed on both, local and remote PC?
It says “…you will need to create an account for them on your computer”. What kind of “account”? There is no such thing as an account management in the free version of NoMachine. I do not understand this term.
Apart from that, the FAQ describes the normal procedure of connecting one PC to another PC using IP and port. As I wrote, this always results in a new virtual desktop session (like a terminal server). I was not able to share an existing physical desktop (for support purpose) and I have not seen anything in the GUI that would allow me to select between creating a new virtual desktop or sharing a physical desktop.
When connecting, it always asks me for username and password, which makes it impossible to access the desktop of another user sitting in front of the remote PC since I do not know the password of that user.November 22, 2019 at 09:52 #24554
To be able to connect to a remote computer using NoMachine, you must have a user account on that computer. If the computer is not yours, the person in charge of that computer must create a system account for you and provide you with the credentials (username and password). Once NoMachine is installed, you use those credentials to access the remote desktop. This might be useful: https://www.nomachine.com/getting-started-with-nomachine
The local user can control what level of control is possible and what notifications they prefer to receive by setting the appropriate security settings. This document indicates the default settings: https://www.nomachine.com/DT10O00154&dn=quick%20guide#3.2.November 25, 2019 at 09:31 #24559
So I can’t access a desktop if I don’t know the credentials of the corresponding Linux account? This means I can’t use (free) NoMachine for support sessions. I am not allowed to know other users’ credentials and the users can not create a additional account for support since they need support with their normal account.
Is this different for NoMachine variants with costs?November 25, 2019 at 12:41 #24576
If the user on the other end has Enterprise Desktop installed you will be able to access as a guest user (they will still need to authorize you). This is available as evaluation software if you are interested in trying it out.
If you don’t want to explore that route, NoMachine Network will be useful to you. This is coming soon. More about this feature is available here: https://www.nomachine.com/FR07J02731December 9, 2019 at 08:38 #24714
The Network feature actually sounds interesting. What is the current release roadmap? Will there be priority support for early adopters?
You must be logged in to reply to this topic.