Windows administration, finally simplified Manage, migrate and deploy across your Windows environment from a single suite

How to use the RustDesk remote control tool in IDEAL ADMINISTRATION?

How can I check that a computer is using the secure Pointdev RustDesk server?

I have configured the secure Pointdev RustDesk server in IDEAL ADMINISTRATION.

How can I check that a client computer is actually using this server, and not the public RustDesk server?

➡️ How can I check that a computer is using the secure Pointdev RustDesk server?

When you configure RustDesk from IDEAL ADMINISTRATION, it is important to check that the client computer is actually using the secure Pointdev RustDesk server, and not the public RustDesk server or an old local configuration.

This check ensures that RustDesk connections use the infrastructure defined in your configuration, especially for remote control over the Internet or for computers located outside the local network.

➡️ Check the RustDesk configuration in IDEAL ADMINISTRATION

The first check consists in verifying the RustDesk server mode selected in IDEAL ADMINISTRATION.

In the RustDesk configuration, make sure the following mode is selected:

• Secure Pointdev RustDesk server

The server information must correspond to the Pointdev infrastructure, especially the ID server and, if required, the relay server.

If the computer was previously configured with the public RustDesk server or with a custom server, it is recommended to reapply the configuration from IDEAL ADMINISTRATION.

➡️ Check the RustDesk configuration file on the client computer

On the client computer, RustDesk stores its configuration in the system folder used by the RustDesk service.

The configuration file may be located in the following folder:

• C:\ProgramData\RustDesk\config\

In this folder, the RustDesk configuration files may contain the information related to the ID server, the relay server, and the RustDesk key used.

You can check that the settings no longer refer to the public RustDesk server, but to the secure Pointdev server.

The presence of the following server is an important indicator:

• rustdesk.pointdev.net

➡️ Test network access to the Pointdev RustDesk server

From the client computer, you can also test whether the Pointdev RustDesk server can be reached on the port used by RustDesk.

From a PowerShell console, you can use the following command, for example:

• Test-NetConnection rustdesk.pointdev.net -Port 21116

If the test succeeds, this indicates that the computer can reach the Pointdev RustDesk server on the tested port.

If the test fails, the issue may be caused by network filtering, a firewall, a proxy, a security rule, or a DNS restriction preventing the computer from contacting the server.

➡️ Restart the RustDesk service after a configuration change

After changing the RustDesk configuration, it may be necessary to restart the RustDesk service so that the new settings are correctly applied.

From IDEAL ADMINISTRATION, you can manage the RustDesk service remotely when the workstation administration prerequisites are available.

You can also restart the service locally on the client computer if required.

This step is important if the computer still appears to be using an old RustDesk configuration despite the changes made.

➡️ Identify an incorrect configuration

Some error messages may indicate that the computer is not using the expected server.

For example, if an error message refers to the public RustDesk server, it usually means that the Pointdev configuration has not been applied or that the old configuration is still being used.

A message containing a reference such as the following should therefore attract your attention:

• rs-ny.rustdesk.com

Conversely, an error message referring to rustdesk.pointdev.net indicates that the computer is trying to use the Pointdev RustDesk server, but that a network issue is probably preventing the connection.

➡️ Points to check in case of doubt

If you are not sure that the computer is actually using the secure Pointdev RustDesk server, check the following points:

• the Secure Pointdev RustDesk server mode is selected in IDEAL ADMINISTRATION
• the RustDesk configuration has been applied to the client computer
• the RustDesk service has been restarted after the configuration change
• the client computer can reach rustdesk.pointdev.net
• no old configuration still refers to the public RustDesk server
• the company firewall, proxy, or DNS filtering does not block the outgoing connection

In practice, if the computer’s RustDesk configuration correctly refers to rustdesk.pointdev.net and the network test to this server succeeds, the computer is correctly configured to use the secure Pointdev RustDesk server.

If the computer still mentions the public RustDesk server, or if the connection to rustdesk.pointdev.net fails, you should reapply the RustDesk configuration from IDEAL ADMINISTRATION, restart the RustDesk service, and check the organization’s network restrictions.