McAfee Agent does not communicate with the ePO server

[anonn]

McAfee Agent does not communicate with the ePO server after reboot

[shridharsr]

check if the firewall is up?

try to ping and telnet from client to ePO server

[anonn]

Hi Shridharsr

The nothing has been changed from the firewall side, and I can ping the ePO server from the client machine

[shridharsr]

try to telnet on port 443 and 80

[anonn]

Hi, I could not telnet from the client to the ePO server using both ports

[shridharsr]

these are the ports used for communication. check in firewall if its diabled/blocked

[wrobeld]

Check and make sure the McAfee Agent service is running.  We have multiple systems that after a reboot the service, even though its set to automatic, will not start.  If you manually start it, it runs fine.  Very frustrating.  (This happens with agents 5.0.5.739 and 5.0.6.220)

[hausi]

Me too, I have the same problem - is this behaviour known by McAfee? Will there be a fix available?

[cdinet]

What version of the agent?  The agent logs will log the communication attempt to the server or agent handler.  Then when you get a failure, you need to check the server logs for same time frame of the connection attempt for any errors.  There are many reasons for communication failures and without knowing the specific errors, there is no way to give a solution.  If you are using the 5.x agent, please read the known issues KB83895. 

There are basically 2 kinds of failures:

1. Agent attempts to connect and the server rejects it for some reason or another

2. Agent is not able to reach epo server or agent handler at all

Only the logs will say for sure what the real problem is.  There is a log reference guide for epo that is helpful (pd24809) and the 5.x product guide will have log locations for the agent logs.

[hausi]

Agent Version 5.0.6.220

"McAfee Agent Service" dies, it will not synchronize MDE-Users and will not update the DAT-Files.

After starting masvc, it will work again.

The Agent Logs: https://1drv.ms/u/s!AvdVHF4RAwA2wBz26NflilP7O_vw

My Workaround:

EEDK -> CMD -> net start masvc

-> Client Task every 15 minutes.