NoMachine Support

Your questions answered

Knowledge Base

Searching in: Articles & FAQs
Filter the search results
Applies to:
Last update:
Searching in: Articles & FAQs
ID: AR02S01107
Applies to: NoMachine Server
Added on: 2021-02-23
Last update: 2021-02-23
The Cloud Server's default method for forwarding connections to its nodes starting from version 7.2

Starting from version 7.2 and with the implementation of the following Feature Request:

Changing the default forward methods for Cloud Server nodes

the default method for forwarding client connections via Cloud Server changes to 'tunnel' for both protocols.

In Cloud Server v. 6 and up to v. 7.1.3 the default methods for forwarding client connections to its nodes ('child servers') are: 'token,tunnel' for connections by NX protocol and 'system,tunnel' for connections by SSH protocol.

These settings optimistically assume that the Cloud Server can connect directly to its child nodes by using 'token' or 'system'. When nodes are not directly accessible, such as when the Cloud Server is in a DMZ zone, it switches to 'tunnel' method after having tried unsuccessfully to connect using the previous method first. This can potentially introduce up to 30 seconds delay in the time clients can connect to the requested nodes.

When Cloud Servers are installed as gateways to permit internal access to users located anywhere on a large LAN or on the Internet, 'Tunnel' must be the chosen forwarding method. For this reason it becomes the new default forwarding method and will guarantee, in normal conditions, a connection time in the order of a few hundred milliseconds. Before, these connections would have taken up to 10 or also 30 seconds to be successfully completed.

The new default settings from 7.2 are:

For client connections by NX protocol:
nxserver --serveredit <node:port> --forward-nx-methods tunnel

For client connections by SSH protocol:
nxserver --serveredit <node:port> --forward-ssh-methods  tunnel

Further details for Administrators and what commands to use in order to change the new default to their preferred forwarding methods are available in the Feature Request link above.