Hi @MNE_DUDE ,
The systems usually show up on ePO with the actual IPs.
If you're seeing multiple systems with same IP, please raise a ticket with McAfee Agent Support.
Thanks
Was my reply helpful?
If you find this post useful, Please give it a Kudos! Also, Please don't forget to select "Accept as a solution" if this reply resolves your query!
Thanks @Pravas,
For instance:
There are three work stations in the system tree with the same IP address. For two of them last communication recorded is old several months, but third one is up and running. So, I am wondering how to force ePO to keep system updated according to actual state in network...
Thanks for advice but I have no subscription for ticketing... 😐
v/r
Hi @MNE_DUDE ,
I've moved this post to ePO Forum for better visibility.
Thanks
Was my reply helpful?
If you find this post useful, Please give it a Kudos! Also, Please don't forget to select "Accept as a solution" if this reply resolves your query!
Hello MNE_DUDE
Having the same IP should not be an issue as the ePO server works with the agent GUID which should be unique per Mcafee agent.
Are those systems names/ FQDNs or GUIDs duplicated or seen multiple times on the system tree?
Was my reply helpful?
If this information was helpful in any way or answered your question, will you please select Accept as Solution in my reply and together we can help other members?
HI @aguevara ,
I have just duplicated IPs.
It is good to know that the ePO communicates over the GUIDs, but what in case when the agent is not reachable for some reason?Then Administrator trying to wake up or to do some another action to establish visibility with the agent. In that case FQDN or IP is only what ePO can use to call the agent. Am I right?
In that case there is a chance that ePo is trying to reach right work station but with a wrong IP?
v/r,
when working with wake ups the the handlers will attempt to use: FQDN, NetBIOS and IP, all 3 if one of them fail, you can configure the order for this on the Server Settings > agent contact method.
Please note this is different from a regular agent to server communication where the GUID (among other things) is used
Was my reply helpful?
If this information was helpful in any way or answered your question, will you please select Accept as Solution in my reply and together we can help other members?
I just find interesting example:
One station from System Tree is responding to ping and wake up. I pushed the installation of the new Agent version. In order to be sure that wake-up reply comes from the right station and Agent is installed well, I have remoted to the host directly.
So, everything is fine, ePo actions are shown in Status Monitor, Agent is installed, IP is the same on both side, but the Host name doesn't correspond with Host name from the ePO. In this case I did some particular action but to the "wrong" station...
That's the my issue.. 🙄
Hi @aguevara,
I did it but I can not find any duplicates. I also check aforementioned case and the GUID numbers are different...
Corporate Headquarters
6220 America Center Drive
San Jose, CA 95002 USA