The eG Installation Guide - eG Innovations

Configuring eG Enterprise to Work in NATed Environments
6.2 Agent on a Public IP
Figure 6.1: Manager behind a NAT
Suppose an agent with a public IP address, say 209.15.2.3 (see Figure 6.1), has to communicate with
the eG manager. In this case, when installing the agent, the externally visible IP address of the
manager (i.e., 209.15.165.127) has to be specified as the manager's IP address (see Figure 6.1). Only
then can the agent communicate with the manager. The dashed lines (--) in Figure 6.1represent the
flow of information from the eG agent on 209.15.2.3 to the eG manager on 10.5.20.12. In this case,
the server/applications on 209.15.2.3 must be managed via the eG admin interface for the manager
to respond to the agent.
6.3 Agent behind a NAT
Yet another scenario involving NATed environments is when the system on which the agent is installed
is also behind a network address translator (see Figure 6.2). Suppose that the agent is being installed
on a server with a private IP address 192.168.10.7, and that this agent has to be configured to
communicate with the manager on 10.5.20.12 (which is accessible over the Internet as
209.15.165.127). Suppose that the private IP 192.168.10.7 is translated into the public IP address
209.15.2.3 via a NAT (see Figure 6.2).
424