Jump to content

Scene

Members
  • Posts

    4
  • Joined

  • Last visited

About Scene

  • Rank
    Newbie
    Newbie

Profile Information

  • Location
    U.K.
  1. I just saw the LiveGrid alert pop up again, and so decided to try pinging all the listed umXX.eset.com hostnames and the avcloud.e5.sk hostname. I was getting successful ping returns from the avcloud.e5.sk and the umxx.eset.com hostnames up until um14.eset.com, where upon it timed out a couple of times and then resolved on the 3rd attempt. As soon as it resolved the warning disappeared. Note that I was also using a remote VPN to connect to the company domain at the time.
  2. I have enabled it on my machine for the time being and will monitor. I did see the LiveGrid warning flag up for me even with the rules in place, so it will be interesting to see what the logs record if it happenes again.
  3. We're using Protect Cloud and are intermittently receiving these warnings randomly on user machines (who all work from home). I had to apply a firewall rule policy within Protect Cloud to stop the warning. The client machines are all running ESET Endpoint Security which takes over and disables Windows Defender Firewall. None of the servers have had the warning and the server client does not override the Windows firewall, which means ESET is blocking itself from acccessing LiveGrid.
  4. We're using Protect Cloud and have experienced the LiveGrid warning randomly across our client machines. ESET Endpoint Security is deployed out to all our client machines, which overrides Windows Defender Firewall. None of the servers have experienced the issue as Windows firewall doesn't get overridden by ESET. Applying the firewall rule policy within the Protect Cloud portal to deploy out to all clients resolved the LiveGrid issue, which means ESET Endpoint Security firewall is blocking itself from accessing LiveGrid.
×
×
  • Create New...