By default, RustDesk can use a public infrastructure to establish remote connections outside the local network.

For enterprise use, it is possible to install an internal RustDesk server in order to remotely control computers located outside the local network (remote work, mobile computers, remote sites), while keeping full control of the infrastructure.

Setting up an internal RustDesk server provides the following benefits :

• using RustDesk outside the local network without relying on a public cloud service
• centralizing connections and computer identifiers
• improving security and compliance with internal policies
• keeping all remote control traffic under the company’s control

The RustDesk server relies on two main components :

• hbbs (ID Server)
• hbbr (Relay Server)

These components can be installed on a Windows or Linux server within the company network.

Once the server is installed, it is necessary to :

• open and forward the required network ports on the company firewall
• assign a public DNS name to the RustDesk server (example : rustdesk.mydomain.com)
• configure RustDesk clients to use this internal server

Once this configuration is applied, computers located outside the local network can be reached using their RustDesk ID, even behind NAT or firewalls.

In IDEAL REMOTE, using an internal RustDesk server provides a remote control solution that is :

• compatible with both LAN and WAN environments
• secure and fully controlled
• well suited for professional and sensitive environments

For more details regarding port configuration and certificates, it is recommended to refer to the official RustDesk documentation.

---