The eG Installation Guide - eG Innovations

Configuring eG Enterprise to Work in NATed Environments
Configuring eG Enterprise to Work in
NATed Environments
It is straightforward to deploy the eG manager and agents for monitoring an Intranet where all the
managed systems are in the same IP address range, and there are no firewalls/address translators
between the managed devices/servers. In many large environments, there may be multiple
demilitarized zones, with firewalls between them. Furthermore, the monitored network can span
multiple geographical locations and can be connected via Virtual Private Networks. The
devices/servers in each location can be in a different, often private, IP address range. This section
covers how the eG manager and agents have to be configured to handle such environments.
There are various scenarios to be considered, depending on whether the manager and agents reside in
network address translated environments.
6.1 Manager behind a NAT
Consider the case where the eG manager and agents are in a private Intranet (see Figure 4.1). All the
agents can be configured to communicate with the manager using its private IP address. In this case,
if external access from the Internet is required for the eG manager, network address translation can
be setup, so the eG manager can be accessed using a public IP address from the Internet. In the
example in Figure 5.1, the manager is installed on a private address - 10.5.20.12. The agents are
installed on private addresses 10.5.20.4, 10.5.20.11, 10.5.20.19. The manager is accessible from the
Internet via a public address - 209.15.165.127. In this case, users inside the Intranet (eg., User A)
can use the URL http://10.5.20.12 to connect to the manager, while users on the Internet (eg., User
B) must use the URL http://209.15.165.127/ to connect to the manager (see Figure 6.1).
423
Chapter
6