GrantLui

Reactions

0 Promote 0 Like 0 Boom 0 LOL 0 Spam 0 Abuse

Comments

  • Hi Bruce, Thank you, I confirm we do have an internal DNS and client PCs are using it for resolving external domains. In such case, what can we do? Does it mean we can't use WebBlocker for such purpose at all? Many thanks!
    in Settings to deny ESET EndPoint updates from client PCs Comment by GrantLui June 21
  • Hi Bruce, Thanks for the response! Yes, on HostWatch, for instance, I can see one of the IPs, 91.228.167.25 is established with HTTP. I did a reverse lookup showing this DNS name is h3-repository02-v.eset.com; this is one of the IPs listed on ESET's website above. I really have no clue what I missed as I added deny action…
    in Settings to deny ESET EndPoint updates from client PCs Comment by GrantLui June 19
  • Hi Bruce, The below are the exhausive list of domain names from ESET, which we added all of them into the "URL Path > deny list" and "WebBlocker Exception > deny action for mattern match" for both HTTP & HTTPS proxy action.…
    in Settings to deny ESET EndPoint updates from client PCs Comment by GrantLui June 6