If you have a server that has more than one network card in it, it is probably going to have more than one IP address—a scenario described as multi-homed servers. You could have problems connecting to the AdminServer and other OpenEdge servers in this instance.
An example of a multi-homed server is shown in the following figure.
Figure 20. Multi-homed server
The clients on the 10.x.x.x subnet will not be able to access services on the host unless they use the correct IP address 10.1.1.1. Likewise, the 192.168.x.x subnet must use 192.168.123.1. To make all these clients connect to a single AppServer on the host, set up the hosts file on the machines in the 10.x.x.x subnet to read as follows:
127.0.0.1 localhost
10.1.1.1 hydra
And, on the 192.168.x.x subnet to read as follows:
127.0.0.1 localhost
192.168.123.1 hydra
All AppServer and WebSpeed instances running on hydra must have their Register with NameServer settings changed so that they do not register with an IP address, but instead with a host name. You can set these properties in OpenEdge Management or OpenEdge Explorer from within the configuration of each AppServer broker or WebSpeed broker. For more information, see OpenEdge Management and OpenEdge Explorer: Configuration or the OpenEdge Management or OpenEdge Explorer online help.
This enables the NameServer to tell the clients, regardless of what subnet they are on, to connect to the machine called hydra. It is then up to the client machine to decide what the appropriate IP address is.
