Configuring for use with a NAT firewall

When Infrastructure Management Server and a user are on opposite sides of a NAT-enabled firewall, it can create difficulties when trying to access the server, either with the Administration or Operations Console. These difficulties can be overcome by making two configuration changes. 

The macro unmigrated-inline-wiki-markup from Confluence is no longer available.

  • (Solaris) or (Linux) In /usr/pw/apache/conf/httpd.conf or (Windows) in \pw\ApacheGroup\Apache\conf , modify the ServerName entry to use the host name of the Proactive system rather than the private IP address (note that there are two of these entries). By default, this entry uses the private IP address of Infrastructure Management Server.

  • (Solaris) or (Linux) In /usr/pw/pronto/conf/pronet.conf or (Windows) \pw\ApacheGroup\Apache\conf, modify the pronet.rmi.server.hostname entry to use the host name of Infrastructure Management Server. By default, this value is not assigned and defaults to the private IP address of Infrastructure Management Server (to make this change permanent and to ensure that the change is preserved during upgrade, copy the entire line to /usr/pw/custom/conf/pronet.conf).

    Note

    Ensure that you do not insert any extra spaces or tabs within the line or at the end of line as it can cause problems.

The macro unmigrated-inline-wiki-markup from Confluence is no longer available.


The macro unmigrated-inline-wiki-markup from Confluence is no longer available.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*