Jump to content

kingoftheworld

Members
  • Posts

    191
  • Joined

  • Days Won

    1

Everything posted by kingoftheworld

  1. This is the first time I am hearing about the end of sale for ESET Protect. Since we are an existing customer, I understand our console will continue to work. However, should we expect development of the on-prem offering to cease? If so, how long should we reasonably expect to be on-prem before being forced to the cloud?
  2. With the shift of priorities, is it expended that EEAv6 for macOS will be extended beyond Dec 23?
  3. Fair enough on the restarting of the service. Based on your statement of Microsoft needing to look at this would indicate that ESET is not investigating this on their end?
  4. I don't know that it is a question for Microsoft to determine. From the linked thread, only one other AV vendor was mentioned. A bigger question is why is ESET not attempting to restart itself given the settings for the service is to always attempt to restart itself?
  5. I understand that it is a bug tracking ID. I am asking what the specific problem is as I am tracking a couple that I haven't reported to support yet.
  6. Can you give some information on what this bug tracking ID is for? Didn't see anything listed on the known issues page.
  7. While I can't switch my entire environment to the pre-release, I did change my test machines and it resolved the issue. How long will it be the pre-release before going to the main channel?
  8. Judging by the number of posts in this page, is ESET planning on any fixes on their end to change the response from these servers to avoid this issue? As someone from ESET previously mentioned, there was a change in the LiveGrid components between versions 7 and 8 which is when this started becoming a problem.
  9. They emailed customers about it. You should probably verify you are on the mailing list for product updates.
  10. Indeed. I am trying to figure out when the uPCU update for server products will be released
  11. When should we expect a uPCU update for v8 to address the vulnerability in the release notes?
  12. Has there been any information on if clients that only use a mirror server will receive these updates in v8 and v9? I know the question was posted in another thread a while back, but I don't think there was ever a response. We have a number of clients that are not accessible to the Internet and only pull updates from an internal server and we would like for them to auto-update like the rest of our environment.
  13. Thank you for the response. In that case, do you know if Fortinet support was contacted for the issue?
  14. I have seen a noticeable declines as well. We are down maybe 300 from the 2000 we were seeing.
  15. Thank you. Just ran on one of my impacted machines and it successfully makes it to h1-c04-s.eset.com [91.228.165.44]. I am leaning back toward the problem being with this version as another machine with the issue running 8.1 was upgraded to v9 and the problem goes away.
  16. Thanks for posting. I am not seeing the same hops through Russia on my test machine that I previously saw. LiveGrid still isn't happy, but I will deal with it on Monday.
  17. Maybe ESET will bring up some servers in the US to handle some of this communication given their large number of customers in the States.
  18. Further testing says your theory may be correct. On some machines (working machines) the routes to the LiveGrid servers leave the US, go through Denmark and onto ESET. On the ones that aren't working, the route appears to leave the US, head through Russia and some other locations but don't appear to make it to ESET. Curious if anyone else is seeing similar.
  19. That is a good possibility. Given that most (or all) of the IPs go to Europe which is a long way for at least me in the US.
  20. Not for me. Nearly all of these machines are desktops with only a wired NIC.
  21. I think there is something more going on here with the LiveGrid issue that many seem to report. We had a large number of clients (1000+) running EEA 7.4.2041 for about 1 year without any issue. I upgraded everything to 8.1.2037.2 and most seem to be reporting that it is unable to connect to LiveGrid. I checked each of the domains listed on the KB to ensure they are reachable and that correct DNS resolutions are happening and everything was good. Going off of the knowledge shared on the forum of the communication change with 8.1, I went ahead and upgraded one of the clients with the issue to v9. This fixed the issue. Assuming v9 uses the same communication mechanism as v8.1, I lean toward there being something wrong with v8.1 rather than a local network issue. I have clients running v8.1 with the issue and without the issue that are running the exact same image, behind the same firewalls, configured exactly the same.
×
×
  • Create New...