How BMC ProactiveNet interfaces interact with  firewalls

Firewalls block a wide range of TCP ports required by one or more BMC ProactiveNet components. Usually, this only affects the BMC ProactiveNet Administration Console because it requires a wide range of TCP ports for efficient operation. The BMC ProactiveNet Operations Console has an HTML interface, so it is usually unaffected by port restrictions because most firewalls allow incoming connections on port 80, which is needed for HTTP (web browser) access.

If a firewall uses NAT (Network Address Translation) whose translation is one-to-one, it causes problems for both the Administration and Operations Consoles. To overcome this, certain configuration changes must be made on the server.

If BMC ProactiveNet Server is behind a firewall and the NAT translation is many-to-one (for example, the firewall uses IP masquerading), then the BMC ProactiveNet Server is inaccessible to both the Administration and Operations Consoles.

For information about using BMC ProactiveNet through a NAT-enabled firewall, see Configuring for use with a NAT firewall.