NoMachine Support

Your questions answered

Knowledge Base

Searching in: Feature Requests
Filter the search results
Target version:
Last update:
Searching in: Feature Requests
ID: FR06Q03839
Added on:  2019-06-13
Last update: 2019-09-17
Priority: Low
Products: NoMachine Server
Implemented in: 6.8.1
Status:  Implemented
Forwarding NoMachine authentication to the RDP server when the xfreerdp client is used

NoMachine RDP sessions are encapsulated in a virtual desktop and rely on the RDP client installed on the remote Linux host where the virtual desktop is started.

Command to start the RDP client is defined in the node configuration file (/usr/NX/etc/node.cfg) in the CommandStartRDP key. The default client is rdesktop (, but  also the xfreerdp client ( is supported by setting the appropriate command:

CommandStartRDP "/usr/bin/xfreerdp -f -k pl --sec rdp"

When using the xfreerdp client, however, NoMachine credentials are not passed to the RDP server.  I.e. even if the user chooses 'Use the NoMachine user's credentials' as Authentication method for RDP sessions in the client UI, he/she still has to provide them manually.

In order to pass user's credentials to the RDP server, NoMachine needs to add support for the -u (username) and -p (password) options provided by the xfreerdp client.