When the computer that the Agent is installed on has multiple IP addresses, TA can't be bound to report a specific IP address.
The Agent binds to all available interfaces with regard to the port that it's listening on. But, when reporting the IP address in the property set that the Agent sends to ePO, the Agent selects the first IP address of the Agent Handler that it can successfully establish a connection with. The IP address and interface are sent to ePO in it's property package.
NOTE: Any IP addresses other than the one assigned to the primary Network Interface Card (NIC) on a computer is detected as separate Rogue Computers by RSD sensors.
On some operating systems, you can force the computer to report the NIC with the external IP address
first (Lan1) and the other as the second (Lan2). This action resolves the problem because the Agent automatically tries to connect to an Agent Handler using whichever the operating system reports as the first interface. For more information about which operating systems this action can be applied to,
see the Microsoft article
Configure the Order of Network Interfaces.
You see the sequence of events below on the ePO server when a client system restarts and a different IP address is bound first and used by the
Agent Sequence of events:
-
The server first tries to connect to the client using the last known IP address.
-
The server tries to communicate using
Domain Name Services (DNS).
-
A
NetBIOS broadcast is sent to locate the client and resume communications.
Problems incurred when TA reports on a new IP address in its property package are as follows:
- ePO reports can contain erroneous data and show TA using an incorrect IP address.
- For a new computer, the computer might be assigned to the wrong part of the ePO directory if system tree sorting is used based on IP.