Jump to content

GRPC Error: Failed to resolve {hash-value}.a.ecaserver.eset.com:443

Go to solution Solved by Sysadmin_DF,

Recommended Posts

Hello,  I am a new ESET customer and I am seeing repeated errors on many of the end points management agents.  The errors appear to be DNS related, but, each of these PCs can access the Internet successfully, and each of the PCs enrolled in the Protect Cloud successfully.  However, they are not checking in successfully.  In the example provided in the attached screenshots of trace log and status.html, the agent checked in successfully approx. 24 hours ago.  But hasn't checked in successfully since then.

Any help on this would be greatly appreciated.  Thank you,





Link to comment
Share on other sites

  • Administrators

Are you able to resolve it by running "nslookup %hash%.a.ecaserver.eset.com:443" ?

Link to comment
Share on other sites

  • Solution

Hi Marcos, Thanks for the reply.

I continued troubleshooting and found that *none* of the PCs were on the Internet.  It appeared that they were due to cached DNS entries.  

Reviewing the blocked traffic on the PCs revealed that DNS was being blocked.

Adding the IP address of our local DNS server to the trusted zone ( Advanced Setup -> Network Protection -> Advanced -> Zones ) resolved the problem.

Now all the PCs are checking in successfully.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Recently Browsing   0 members

    No registered users viewing this page.

  • Create New...