Getting Ready
This guide will walk you through setting up and troubleshooting the Cloudamize Agentless Data Collector.
...
- TCP port 445 open inbound
- TCP ports 443 and a proxy server port if a proxy is being used (e.g., 8080,80) open outbound to our servers at the following addresses:
- For assessments on app.cloudamize.com: 104.197.11.97 for US
- and 35.198.133.35 for
- EU
- For assessments on console.cloudamize.com: am.cloudamize.com (US) or am-de.cloudamize.com (EU). If your firewall does not support FDNQ, you can instead add 35.171.170.26 (US) or 18.194.12.63 (EU).
Each Windows endpoint
- TCP ports 135 and the range 1025-65535 open inbound
- TCP port 445 open outbound to the machine with the Agentless Data Collector installed
...
The table below lists the relevant ports for machine discovery and communication to the Cloudamize servers:
Protocol | Port | Usage |
TCP | 22 | SSH to access Linux servers |
TCP | 135 | Windows RPC |
TCP | 445 | Microsoft-DS Active Directory and SMB, Windows shares |
TCP | 1025 - 65535 | RPC dynamic port range |
TCP | 443 | SSL to communicate with the Cloudamize servers |
Ports relevant to the Cloudamize Agentless Data Collector
...
- The host [IP Address] is down
- The account name and password are incorrect or the account does not have sufficient privileges
- If the server is domain joined the domain controller itself may not be running
- The Active Directory administrator group may not include the domain administrator group.
- The user account provided may not be in the domain admin group or it may not be the local administrator account
- A local account on the server in use and it is a member of the administrators group but not the administrator account itself.
...