Documentation forDameware Remote Everywhere

System requirements for Dameware Remote Everywhere

Hardware and software requirements

Hardware and software Requirements
Operating System (Technician Console)
  • Windows 8 or later
  • macOS 10.12 or later
  • Android 4.0 or later
  • iOS 9.0 or later
Operating System (Agent)
  • Windows 8 or later
  • macOS 10.12 or later
  • Android 4.0 or later
  • iOS 9.0 or later
  • CentOS 7 and 8
  • Fedora 31 and 32
  • Debian 9 and 10
  • Ubuntu 18.04 and 20.04 (LTS variants)
Network

Ability to make direct outgoing TCP connections, or availability of an HTTP proxy or SOCKS server
Hard drive space 100 MB
CPU 450 MHz
RAM 256 MB

Domain inclusion requirements

Dameware Remote Everywhere must be able to resolve the following domain names:

  • *.beanywhere.com
  • *.mspa.n-able.com
  • *.pubnub.com
  • *.swi-tc.com - mandatory for using the Vaults feature and accessing the Admin Area
  • *.swi-rc.com
  • *.swi-dre.com
  • swi-rc.cdn-sw.net

Port requirements

The ports identified in the tables below must be accessible for Dameware Remote Everywhere remote control connections.

If the agent has a direct TCP port configured, the same port must be open at the agent's firewall and be accessible by the viewer.

macOS uses TCP Mode only

Dameware Remote Everywhere can use the UDP transmission model to connect to devices in addition to TCP.

Initially, the Dameware Remote Everywhere viewer requires access to port 1234. After the system administrator modifies the firewall to enable the identified IP addresses to communicate with the server, the ports can be random.

Port Protocol Service Direction Description
80 TCP - Outbound Required for HTTP connectivity
443 TCP - Outbound Required for HTTP connectivity
1234 UDP - Bidirectional Required for P2P connections
1235 UDP - Bidirectional Required for P2P connections

3377

 TCP - Outbound Failover port where DPI is enabled