Agent communication managed Endpoint

[rautenrunner]

Hi,
we are using ePolicy Orchestrator version 5.3.2. I can run client tasks from the system structure and install agents. It is working. The agents are displayed as managed on the client, but do not report their status back to ePo.

DNS resolution works. Ports (80, 443, 58081, 8443, 8444) are released and accessible.
A clean deinstallation did not help.
Other locations are not affected.

What could it be?

Thanks for help!

[cdinet]

I need to make sure you understand epo 5.3 is no longer supported.  That being said, for communication errors, you would first look at the masvc log on the client (c:\programdata\mcafee\agent\logs) and find the error for asci.  Then you would look at the server log on the epo server (in epo install directory - db\logs) for matching time frame for any possible errors on the server.  

There are 2 basic types of failures.  Either the agent can't reach the server at all and server never receives the connection attempt, or the client reaches the server and is rejected for one reason or another.  So you need to look at both sides of the traffic.

[rautenrunner]

Thank you for your help.

The problem seems to be with the client. The agent cant reach the server.

In the log I see the entry: ahclient.Debug: No relay found in the network, the last cb calls.

The server log is ok.

Do you know the error message and a possible solution?

[cdinet · Accepted solution]

You have to look for keyword "asci" and follow the communication attempt.  You should see an entry such as connecting to https://servername:443 and a failure response.  When did the issue start and what changed?  Are the clients external or internal on the network?  Make sure not to post any log entries that contain sensitive information, but we would need to know what error you are seeing.

[rautenrunner]

the webproxy blocked the traffic to the server. Thanks for help!

[cdinet]

Glad to assist!  You can configure proxy settings in the agent repository policy, if necessary.