Remote agents are lightweight helper components you install in another network (for example a branch office, remote site, or isolated subnet) so monitoring can happen locally there and the results can be sent back to your main monitoring server. They solve common real-world problems like firewalls, NAT, and segmented networks—where your central monitoring server can’t directly reach every device, or where you want to avoid constant cross-site polling traffic.
Remote Network Agents in IPNetwork Monitor. IPNetwork Monitor uses the Remote Network Agent to monitor servers and devices inside remote networks from a central IPNetwork Monitor installation. You install the agent on a machine in the remote network, choose active or passive mode based on your security policy, and configure the IP address/hostname of the main IPNetwork Monitor server plus the communication port (default is 3459). Active vs passive determines which side initiates the connection and therefore which firewall rules you need (inbound/outbound) on the main server and the agent host. The agent runs as a Windows service and can be started/stopped/restarted, and it can be managed centrally from Settings > Remote Network Agents in the IPNetwork Monitor client (enable/disable, discovery settings, upgrades, and limits). For secure communication, the agent uses SSL with a certificate/key pair; you can keep the default self-signed pair or provide your own, and the certificate fingerprint is used as the agent’s Connection ID—which makes it easier to move an agent between hosts without rebuilding its monitors. Once enabled, IPNetwork Monitor creates a dedicated tree section (for example Monitored by “Agent name (Agent IP)”) and you can add hosts/monitors either manually or via network discovery, just like with local monitoring.
