Ports used by Remote Utilities
Overview
Remote Utilities uses different ports depending on whether a direct connection or Internet-ID connection is being used.
Direct connection ports
In order to access a remote Host through direct (point-to-point) connection you need to allow the inbound TCP port 5650 on the Host PC and the same outbound port on the Viewer PC:
| Module | Port | Direction |
|---|---|---|
| Host | TCP 5650 |
Inbound |
| Viewer | TCP 5650 |
Outbound |
During Host installation the program automatically adds an "allow" rule to your Windows firewall on the Host PC. However, if you use different firewall software, you need to manually allow this port in the firewall settings.
Remember
If port 5650 cannot be used for some reason, you can change it to a different value in the Host settings. If you changed the port on the Host side, remember to also update the port in the corresponding connection properties on the Viewer side.
Internet-ID connection ports
Public server
When you enable Internet-ID connection type, the program connects through our company-hosted server by default. Ports that need to be open vary depending on which version of Remote Utilities you use.
Starting with version 6.5, Remote Utilities uses a single outbound TCP port 5655 to communicate with our public server. If this port is blocked, the program automatically attempts to use outbound TCP port 443.
| Module | Port | Direction |
|---|---|---|
| Viewer | TCP 5655, 443 |
Outbound |
| Host | TCP 5655, 443 |
Outbound |
| Module | Port | Direction |
|---|---|---|
| Viewer | TCP 443, 563, 5655 and 5656 |
Outbound |
| Host | TCP 443, 563, 5655 and 5656 |
Outbound |
Self-hosted server
With a bit of configuration you can replace our public server with a self-hosted RU Server by which to route your Internet-ID connections. This makes your remote support solution completely autonomous and no longer dependent on our company infrastructure.
For information on RU Server ports, see Ports used by RU Server.
