Customer ID



NoMachine Support

Your questions answered

Adding servers to NoMachine Cloud Server via the User Interface

With NoMachine version 6, we introduced the possibility of creating a multi-server environment. Any server from the range (with the exception of the free version) can be easily added to a NoMachine Cloud Server in a couple of clicks, including servers without the NoMachine software installed ('Foreign X Servers'). Here is how you can add NoMachine servers to Cloud Server via the User Interface in just a couple of clicks. The steps below can also be applied when connecting to Cloud Server via web.

Enabling multi-server mode

  • In order to trigger the 'add server' functionality you need to either be a Windows administrator or 'root' on Mac and Linux of the host where NoMachine Cloud Server is installed or be a NoMachine administrator (how to make a NoMachine Administrator is explained here).
  • Open the NoMachine User Interface in the usual way and connect to the Cloud Server to which you want to add the node.
  • Make sure you log in using your administrator account.
  • The 'New server' button will be visible at the top (Fig. 1).
Creating a multi-server environment is quick and simple with NoMachine Cloud Server

Fig. 1 – 'New server' is activated once you're logged in as administrator

Adding the server

  • Click on the 'New server' button (Fig. 1). This starts the process for adding a NoMachine "child server".
  • Provide a name for the server, fill in the IP address/host name details, and if appropriate, set the protocol and port different from the default ones (Fig. 2). Note that to add child servers with NoMachine software installed, you need any of the following to be running on them: Workstation, Terminal Server, Enterprise Terminal Server, Enterprise Desktop or Cloud Server as well.
  • If the server you are adding doesn't have NoMachine software installed instead, check the box 'NoMachine is not installed on the server'. In this way you will be adding a 'Foreign X Servers'.
Adding a 'foreign' Linux host o a NoMachine Cloud Server

Fig. 2 – Fill-in all server details and click on OK to continue

  • By default, the server will not accept connections not originated from the parent server. Select whether you want it to be directly reachable or not.
  • Click on OK to continue adding the server. Accept the certificate fingerprint verification when prompted (Fig. 3).
Verify server host authenticity to connect to that server

Fig. 3 – Verify server host authenticity

  • Authenticate to the remote server by using a privileged account on that server (Fig. 4).
Provide server system administrative credentials to continue adding the server

Fig. 4 – Provide server system administrative credentials to continue adding the server

  • Wait a few seconds while the server is added.
  • Successfully added, you will see the new server in the list of available servers (Fig. 5).
The server will be added to the list of all servers federated under your Cloud Server

Fig. 5 – Once correctly authenticated the server will be added to the list of all servers federated under your Cloud Server

  • Once the server has been added, it can be edited from the NoMachine User Interface by right-clicking on the server. You will be able to edit the host (Fig 6.) and will have the option to allow or disable direct connections to the server.
The Ubuntu 'foreign' node is now visible in Administration GUI

Fig. 6 – Edit the servers of your multi-server environment as needed

  • It is possible for admins to configure extra details on how client connections will be forwarded to the selected server by clicking 'Advanced'. This allows admins to customize how connections are forwarded to the child server.
  • The available methods are Tunnel, System and Token. The default option for client connections by NX and SSH protocols is Tunnel. Host and Port allow forwarding of the connection to a different network interface of this server.

    TIP: Default settings will suffice for the majority of environments. Please consult the Cloud Server guide.

Configure additional details for client connections to the selected server

Fig. 7 – Configure extra details about forwarding of client connections