Panagiotis Karaberis

No , exactly the opposite eventhough on my FW I didn't get any notification that traffic was blocked, I opened specific access to ESET servers on port 53535 only, and everything was back to normal ! the strange thing I wanted to share is that I got NO indication that traffic was blocked ... BUT after opening the ports/url that ESET recommended, all was back to normal ! Hope it helped, Panagiotis

Hello to everyone, I have the same problem with lot of friends over here, with the newer ver of EEA (antivirus product) and EES (firewall) Got messages that indicated (a) Limited Direct Cloud Connectivity (b) The ESET LiveGrid servers cannot be reached Following the KB from ESET, https://support.eset.com/en/kb332-ports-and-addresses-required-to-use-your-eset-product-with-a-third-party-firewall?ref=esf I've tested /monitored my firewall and got no indication of blocked ports (especially on TCP/UDP 53535 ....) on any request coming from my clients !! BUT nevertheless, I create a new rule on my firewall (I'm using WatchGuard M470), allowing access to all *.eset.com and *.e5.sk servers, ONLY on those specific ports (TCP & UDP 53535), and by a magic way, everything was working again ! Really don't know how ESET is "controlling" the access to those services, and got no idea why they changed the previous behavior without prior notice ... Anyway, I just wanted to share my experience with everyone else that got same problem , and I hope you will find a similar way to overcome this, Regards Panagiotis