System requirements for Dameware Remote Everywhere 7.0
Hardware and software requirements
|Hardware and software||Requirements|
Ability to make direct outgoing TCP connections, or availability of an HTTP proxy or SOCKS server
|Hard drive space||20 MB|
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 Everywherecan 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.
|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|
|TCP||-||Outbound||Failover port where DPI is enabled|
When using Dameware Remote Everywhere, the SolarWinds N-central server must be able to resolve the following domain names: