NoMachine Support

Your questions answered

Knowledge Base

Searching in: Articles & FAQs
Filter the search results
Applies to:
Last update:
Searching in: Articles & FAQs
ID: AR04K00663
Applies to: NoMachine Server
Added on: 2013-04-02
Last update: 2019-10-15
How to authorize connections to remote desktop automatically or only upon owner's authorization with NoMachine

When connecting to the remote (physical or virtual) desktop of a machine (server), the default behavior is that the server asks for authorization to the remote desktop owner when this owner is different from the user who is requesting to connect. The connecting user must have a system account on the remote machine.

If you need to connect automatically to the remote desktop you have 2 options:

1) Run the connection as the same user of the remote desktop's account owner. If the connecting user is also the desktop owner, no authorization is necessary.

2) Configure the server on the remote machine to accept connection requests without asking for desktop owner's authorization.

To disable requesting for the owner's authorization before connecting to the desktop (either the physical desktop or the user's virtual desktop on Linux) , do the following on the server (the computer which will be accessed):

- Open the NoMachine User Interface from Programs menu or Applications.

- Access the Server preferences (or Connections preferences for NoMachine free)

- Open the Security panel.

- Unflag the 'Require permission to let remote users connect' checkbox. 

To re-enable request for owner's authorization before connecting to the desktop, just flag the 'Require permission to let remote users connect' checkbox.

 

Manual configuration

It's also possible to manage this configuration by editing the server configuration file (server.cfg) as described below.

The server configuration file is: 

- %PROGRAMFILES%/NoMachine/etc/server.cfg on Windows

- /Applications/NoMachine.app/Contents/Frameworks/etc/server.cfg on Mac

- /usr/NX/etc/server.cfg on Linux

To connect to the remote physical desktop without desktop owner's authorization, uncomment the key and set:

PhysicalDesktopAuthorization 0

To request for the desktop owner's authorization, uncomment the key and set:

PhysicalDesktopAuthorization 1


Connecting to Linux virtual desktops

In the case of a server supporting virtual desktops (available for Linux only such as Workstation, Terminal Server, Enterprise Server etc) it's also possible to configure the following.

To connect to the virtual desktop without desktop owner's authorization, uncomment the key and set:

VirtualDesktopAuthorization 0

To request for the virtual desktop owner's authorization, uncomment the key and set:

VirtualDesktopAuthorization 1

 

IMPORTANT:

1) In all cases it's not necessary to restart the server, the new configuration will be applied when starting a new session.

2) Note for multi-node environments: settings in server.cfg of the main server apply to all nodes. Different settings in server.cfg of a  remote node are overriden by settings in the main server.cfg file.

 

Creating a list of trusted users

For versions higher than 5.1.19, rather than allow all users to connect without desktop's owner authorization or click accept for every single user which would like to connect, it is possible to define in advance a group of trusted users who don't need the specific owner's permission. In order to create a list of trusted users, administrators should use the nxserver commands for creating and editing users and groups. These commands provide a new option, --trusted, to define if the user is trusted for connections to the physical or the virtual desktop or both.

For more detailed instructions, see the server's Administration guide at: https://www.nomachine.com/DT07M00090#10.8.