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'.
Fig. 2 – Fill-in all server details and click on OK to continue
- By default, the remote NoMachine server you are adding accepts connections on its IP/host name. Select 'Disable direct connections to the server' to let users access it only through this Cloud Server.
- Click on OK to continue adding the server. Accept the certificate fingerprint verification when prompted (Fig. 3).
Fig. 3 – Verify server host authenticity
- Authenticate to the remote server by using a privileged account on that server (Fig. 4).
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).
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.
Fig. 6 – Edit the servers of your multi-server environment as needed
Fig. 7 – Configure extra details about forwarding of client connections