search cancel

Can not access Java Client when using NAT'ed IP addresses

book

Article ID: 227317

calendar_today

Updated On:

Products

CA Automic Applications Manager (AM)

Issue/Introduction

When using NAT'ed IP addresses, Users may have issues connecting accessing the Java Client.

For example, the IP address for a subnet is 192.43.xx.xx and is translated to NAT'ed subnet 192.259.xx.xx. 

The actual IP address for the AM master is some form of 192.43.xx.xx. 

The workstations are all using 192.259.xx.xx to connect. Pointing the Java client to the 192.259.xx.xx address works but upon connecting, the MASTER\Options.properties file on their workstations updates the workstations with the non NAT'ed 192.43.xx.xx address and fails.

Changing the client Options.properties file manually doesn't work as that file gets overwritten upon attempting to connect.

Environment

Release : 9.3

Component : APPLICATIONS MANAGER

Resolution

Find the options.properties file on the Master server. This is the file that is downloaded to the client and is located here:

%AW_HOME%\web\classes (Windows)

$AW_HOME/web/classes (Unix)

Change the entry in that file to the NAT'ed IP address of the Master. Now the corrected options.properties file is propagated to the client.