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. 

You must modify the following two files on the Infrastructure Management Server when dealing with a NAT-enabled firewall (Ensure that you make a backup of each file before modifying):

• (Linux) In /usr/pw/apache/conf/httpd.conf or (Windows) in \usr\pw\apache\conf\httpd.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.

• (Linux) In /usr/pw/custom/conf/pronet.conf or (Windows) \usr\pw\custom\conf\pronet.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 host name must resolve to the proper address on both sides of the firewall. If DNS service cannot resolve the name, then an entry must be made in the hosts file of Infrastructure Management Server and every computer that runs the administrator client. On Solaris, the hosts file is located in /etc/hosts and on Microsoft Windows in \WINNT\SYSTEM32\drivers\etc\hosts.

After making these changes, restart the Infrastructure Management Server using the pw system start command.

Related topic

Troubleshooting the deployment of packages