Skip to content
computledocs

Network Requirements

Testing your network

This page is for IT teams confirming their firewall, proxy and web-filter rules. Run the test from a device on each network your users work from.

Testing from a device

Section titled “Testing from a device”

  1. Open Computle (Remotle) on a Windows, Mac or Linux device on the network, and sign in.

  2. Open Settings, Diagnostics and click Run Test.

    Remotle checks every service the device needs and groups the results. Every line should show a time in milliseconds.

    The Diagnostics tab of the Remotle app after a test in which every check passed: services, both connection services, three relays and STUN all answer with a time in milliseconds.

  3. Read any failures against the table below.

    A network that blocks outbound UDP looks like this:

    The Diagnostics tab after a test on a network that blocks UDP: the services and the connection service pass, every relay and STUN show No reply, with the note UDP blocked or relay down.

  4. Click Copy Diagnostics to put the results on the clipboard for a ticket. See Diagnostics.

GroupWhat it checksA failure means
This deviceVersion, sign-in state, support code, log fileInformation only
Servicesauth.computle.com, asmgr.computle.com, portal.computle.com, updates.computle.com over TCP 443TCP 443 to that domain is blocked, or a proxy or inspection device is interfering
RendezvousEach connection service over TCP 443Connection set-up is blocked. Sign-in works, sessions do not.
RelaysEach relay on UDP 4443Outbound UDP 4443 is blocked. Sessions cannot use a relay.
STUN / Your networkstun.cloudflare.com on UDP 3478, and the device’s public addressOutbound UDP 3478 is blocked. Direct paths cannot be tried; relays still work if they pass.

The list of services to check is downloaded from softwaredownloads.oncomputle.com each time, so a new relay is tested as soon as Computle adds it.

Without Remotle installed

Section titled “Without Remotle installed”

Before Remotle is deployed, confirm the TCP paths from PowerShell on any Windows device. TcpTestSucceeded : True means the port is open; the UDP paths can only be confirmed with Diagnostics in the app.

A PowerShell window running Test-NetConnection against the two connection services on ports 443 and 9443, each ending with TcpTestSucceeded : True

Test-NetConnection rdv-ths-1.prod.computle.com -Port 443
Test-NetConnection rdv-uka-1.prod.computle.com -Port 9443
Section titled “Related”

Questions

Section titled “Questions”

Users can sign in and see their workstations, and Connect never completes

Section titled “Users can sign in and see their workstations, and Connect never completes”

The session is UDP. Check the Relays and STUN groups in Diagnostics. If they show No reply, outbound UDP 4443 and 3478 are blocked.

Test-NetConnection succeeds but Diagnostics shows the connection service failing

Section titled “Test-NetConnection succeeds but Diagnostics shows the connection service failing”

A TLS-inspecting device is answering the TCP connection and presenting its own certificate. Exclude the connection services from inspection, or trust the inspecting root on the device. See Proxies and TLS inspection.