ePO server using wrong NIC Ethernet interface IP address

[kylekat]

This has happened to me a few times and the answer to the problem was never on McAfee's KB or the forum. Tought of putting it down here jsut so its avaialble down the road for anybody that experiences.

If the ePO server has multiple NIC cards configured on it, there is a chance that ePO will utilize the wrong IP for itself. This will be reflected in a couple places:

*in ePO GUI under "Server Settings" - "Server Information"

*In ePo server [Install path]\McAfee\ePolicy Orchestrator\DB\Server.Ini

*In ePo server [Install path]\McAfee\ePolicy Orchestrator\DB\SiteInfo.ini

I was able to fix this by adding a line in Server.ini:

[SERVER]

 Add a line at the bottom

ServerIPAddress=10.0.0.x

change 10.0.0.x for your server Ip Address 

Restart ePO services.

After doing this, all 3 locations mentioned above should reflect the IP address set manually on the INI file.

[Hawkmoon]

Hi kylekat,

Good post, nice information, thank you!

Just wanted to mention for completeness that there is an official article that covers this!

How to use ePolicy Orchestrator and Remote Agent Handlers on servers that have multiple NICs
Technical Articles ID: KB56281

[kylekat · Accepted solution]

That Article is a nice addition @Hawkmoon but not really the same situation i described. My settings in the Agent Handler settings were the right ones but the wrong IP was being used everywhere else. The Manual addition on the server.ini file quickly fixed it. I honestly propose having a separate article for "Wrong IP address used by ePO servers on when multiple NIC cards are present".

[Hawkmoon]

d'oh!

Sorry, the mistake is mine, I've supplied the wrong article, put simply I had to many open windows. 

What I should have offered was this one:

Some computers listed in the directory are unable to be managed on an ePolicy Orchestrator server that has two NICs installed
Technical Articles ID: KB56308

[kylekat]

That looks more like it, thanks so much @Hawkmoon

I can add that i had no communication errors at all whatsoever from my endpoints' agents and ePO. But the IP was the wrong nonedeless and i was troubleshooting other issues that did not present itself as an "Inability to be managed"