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?

Which ports and domains should be allowed to use RustDesk with IDEAL ADMINISTRATION?

I want to use RustDesk with IDEAL ADMINISTRATION.

Which domains, servers and ports should I allow in my company firewall, proxy or DNS filtering system?

➡️ Which ports and domains should be allowed to use RustDesk with IDEAL ADMINISTRATION?

To use RustDesk with IDEAL ADMINISTRATION, it may be necessary to allow specific domains and network ports, especially when connections are made over the Internet or through a RustDesk ID and relay server.

The permissions to configure depend on the RustDesk mode used: local network connection, public RustDesk server, secure Pointdev RustDesk server, or custom RustDesk server.

➡️ RustDesk connection over the local network

When the RustDesk connection is established directly over the local network, no external RustDesk server is required to establish the connection between the administrator computer and the remote computer.

In this case, the computers simply need to be able to communicate with each other on the internal network.

This mode should be preferred when:

• the administrator computer and the remote computer are on the same local network
• the computers are reachable through a company VPN
• the company wants to limit or block connections to external servers

In local mode, the main point is to check that internal communications are not blocked by a local firewall, network segmentation, or an overly restrictive security policy.

➡️ Secure Pointdev RustDesk server

If you use the secure Pointdev RustDesk server, the computers must be able to reach the following server:

• rustdesk.pointdev.net

This domain must be allowed in the firewall, proxy, DNS filtering system, or any network security solution that may block outgoing connections.

The RustDesk ports to allow may include:

In most cases, these are the most important ports for RustDesk connections using an ID and relay server.

If the organization applies strict outbound traffic filtering, it is recommended to explicitly allow the rustdesk.pointdev.net domain on the required RustDesk ports.

➡️ Public RustDesk server

If you use the public RustDesk server, the computers must be able to contact the public servers used by RustDesk.

Depending on the configuration, a public RustDesk server may appear as follows:

• rs-ny.rustdesk.com

If an error message mentions this server, it usually means that the computer is trying to use the public RustDesk server rather than the secure Pointdev server or a custom RustDesk server.

For business use, the public RustDesk server may be suitable for tests or quick validation, but it provides less control over the infrastructure used.

➡️ Custom RustDesk server

If you use your own custom RustDesk server, client computers must be able to reach the DNS name or IP address of this server.

In this case, the ports to allow depend on the RustDesk server configuration, but the standard ports are generally the following:

Ports 21118 and 21119 are not always required for standard RustDesk client use, but they may be needed in some scenarios, especially with web features or a specific server configuration.

If you host your own RustDesk server, these ports must be allowed on the server firewall, but also on any firewalls or proxies filtering outgoing connections from client computers.

➡️ Do incoming ports need to be opened on client computers?

When using RustDesk over the Internet through an ID and relay server, it is generally not necessary to open incoming ports on client computers.

The computers mainly need to be allowed to establish outgoing connections to the RustDesk server being used.

This is an important point: in most environments, the blockage comes from outbound filtering, the proxy, DNS, or a network security solution, not from a missing incoming port on the user computer.

➡️ Recommended connectivity tests

From a client computer, you can test access to the RustDesk server with PowerShell.

For the secure Pointdev RustDesk server, you can use the following command, for example:

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

For a custom RustDesk server, simply adapt the server name:

• Test-NetConnection your-rustdesk-server.example.com -Port 21116

You can also test the relay port if necessary:

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

If these tests fail, the computer probably cannot correctly reach the RustDesk server. You should then check the firewall, proxy, DNS filtering, security rules, or the organization’s network restrictions.

➡️ Summary of recommended permissions

For reliable use of RustDesk with IDEAL ADMINISTRATION, the following permissions are recommended depending on the selected mode:

• Local network mode: allow internal communications between the relevant computers
• Pointdev RustDesk server: allow rustdesk.pointdev.net on the required RustDesk ports
• Public RustDesk server: allow the public RustDesk servers used by the client
• Custom server: allow the domain or IP address of your RustDesk server on the configured ports

In practice, for professional use with the secure Pointdev RustDesk server, the essential point is to allow outgoing connections to rustdesk.pointdev.net, especially on the RustDesk ports used for identification and relay.

If your company uses a strict firewall, filtering proxy, or DNS filtering, these permissions must be validated with the network team before deploying RustDesk on client computers.