This is a specific scenario in which the client package has been installed as administrator and as normal user. Parallel installations of the client should not exist, to avoid conflicts with files used by both installations like the...
This problem has been reproduced with NoMachine GNOME-Wayland virtual desktop running on RHEL 10. The GNOME-Wayland is correctly started inside the NoMachine session, when the server is configured to use: DefaultDesktopCommand...
When the client is configured to use the proxy with 'Automatic proxy configuration' selected, it doesn't provide the form to insert username and password when the proxy requests authentication.
The rule to enable/disable nodes of a multinode environment is: 'nxserver --ruleadd --class feature --type enable-multiserver --value yes' which may be misleading. Option 'enable-multiserver' should be instead...
The output of the 'nxserver --resourcelist' doesn't list by default the state of the 'enable-profiles' rule. When profiles are explicitly enabled by means of 'nxserver -ruleadd --class feature --type enable-profiles...
The issue has been reproduced on a multi-GPU setup running Kubuntu 26.04. If 4 monitors are attached to each of the two NVIDIA RTX 2000 graphics cards (8 monitors total), monitors will appear as a black screen in the remote NoMachine...
When setting the rule on a per-node basis to disable access to all nodes for all users: nxserver --ruleadd --system --class node --type all --value no using the --system parameter raises an error: NX> 538 ERROR: User: __system__ is not...
Since the control to prevent the installation of two different products on Windows doesn't work as expected, the user is able to install a different NoMachine package over a previous installation of another package, e.g. install a...
When audit logging is fully enabled on the server, copy and paste operations performed between the local client and the remote session do not generate any entries in the audit.log file. The clipboard functionality itself works correctly,...
In v10.2, the audit configuration was moved from node.cfg to server.cfg which provides the new "AuditLogs" key. However, the old and deprecated "EnableAuditlogs" key is still present in the node.cfg file and could...