FRiC 9 Posted October 16, 2019 Share Posted October 16, 2019 Windows 10 Pro, ESET Endpoint Security, ESMC, all latest versions. I have some computers that have all websites blocked except for some necessary Windows update and ESET update sites whitelisted. They connect to the local ESMC server called simply "esmc". A few days ago I noticed they stopped connecting to ESMC and upon checking the logs I discover that https://esmc is blocked. Has there been a change to how ESET communicates with ESMC? Should I whitelist the local ESMC server? Link to comment Share on other sites More sharing options...
Administrators Marcos 5,074 Posted October 16, 2019 Administrators Share Posted October 16, 2019 There has been no intentional change in this regard. If you have all addresses blocked and want to allow http/https communication with specific addresses, then these must be added in allowed addresses. Link to comment Share on other sites More sharing options...
FRiC 9 Posted October 16, 2019 Author Share Posted October 16, 2019 (edited) Thanks for the quick response. I had these computers configured this way since we bought ESET early this year and this issue only started recently. Strangely enough they didn't all start happening on the same day and it didn't affect all computers. Anyway I've added https://esmc to the whitelist and temporarily disable EES... Update: and all is well now. I just find it somewhat strange that I've been running this for nine months, and now suddenly I have to whitelist https://emsc/ Edited October 16, 2019 by FRiC Link to comment Share on other sites More sharing options...
ESET Staff MartinK 378 Posted October 20, 2019 ESET Staff Share Posted October 20, 2019 I think this behavior has been already reported and probably fixed in the meantime. Maybe @Marcos will know more details of whether module responsible for scanning network has been updated in the meantime. It is also possible that update was canceled which might explain why only specific devices were affected. FRiC 1 Link to comment Share on other sites More sharing options...
ESET Staff Posolsvetla 15 Posted November 14, 2019 ESET Staff Share Posted November 14, 2019 This issue is fixed in the Internet protection module version 1382, which is currently in testing. You will be able to remove https://esmc from the whitelist when it's released for your product version(s). FRiC 1 Link to comment Share on other sites More sharing options...
FRiC 9 Posted November 14, 2019 Author Share Posted November 14, 2019 Not sure if related, but I'm upgrading to 7.2.2055 and suddenly the clients are trying to access ESMC by the IP address instead of the hostname and yeah, they blocked themselves again. I tried whitelisting *:2222/* and it seems to work so far. 🤞 Link to comment Share on other sites More sharing options...
Recommended Posts