qwerty 0 Posted September 18, 2017 Share Posted September 18, 2017 I have recently upgraded from ESET Endpoint 6.5.3x to ESET 6.6.2046.0, however I have an alert that Web and mail protocol filtering is non-functional, and due to that anti-phishing is also non functional. I realise this is not the advised product for the platform, but this is on Windows Server 2012 R2, and the same thing has happened to two of the servers that I have upgraded. It is not my choice to run this version of the product on this platform and I will try to move to the File Security product in future. However for now I need to troubleshoot what I have to work with. I have tried to reboot twice, but this did not resolve the issue. If I go to enable the module in setup, it only gives the option to disable which means it is enabled and non-functional. Please could you advise what I can try next? Link to comment Share on other sites More sharing options...
Administrators Marcos 5,069 Posted September 18, 2017 Administrators Share Posted September 18, 2017 Do you have protocol filtering and web access protection enabled in the advanced setup? Link to comment Share on other sites More sharing options...
qwerty 0 Posted September 18, 2017 Author Share Posted September 18, 2017 Hi Marcos. Yes I have checked and they are enabled. Link to comment Share on other sites More sharing options...
Administrators Marcos 5,069 Posted September 18, 2017 Administrators Share Posted September 18, 2017 What about this setting? Link to comment Share on other sites More sharing options...
Karmadyota 0 Posted September 18, 2017 Share Posted September 18, 2017 Sometimes This thing could happen if the modules are incorrectly configured and there may be some kind of trouble in your system during the installation process In many cases reinstalling fixes the issue but if you are lingering with your issue you could provide a screenshot of the settings section Link to comment Share on other sites More sharing options...
qwerty 0 Posted September 18, 2017 Author Share Posted September 18, 2017 19 minutes ago, Marcos said: What about this setting? Hi, yes this is enabled. There seems to be a further issue that this server can now no longer be pinged or it's shared cannot be access not the network either. I am investigating. Link to comment Share on other sites More sharing options...
qwerty 0 Posted September 22, 2017 Author Share Posted September 22, 2017 Hello, Just for anyone wanting to find out the solution to this problem. On one of the servers I just uninstalled and re-installed it, and it works fine. On the other server it would not uninstall, and parts of the installation such as one service were left behind. So I had to use an ESET uninstaller tool. All OK now. Link to comment Share on other sites More sharing options...
hungtt 1 Posted September 22, 2017 Share Posted September 22, 2017 HI qwerty, This is not best solution for site has about 300 clients. Link to comment Share on other sites More sharing options...
ESET Staff MichalJ 434 Posted September 22, 2017 ESET Staff Share Posted September 22, 2017 (edited) @qwerty Why are you installing ESET Endpoint Antivirus on a Server system? Why you are not using ESET File Security for Microsoft Windows Server? Is your license not valid for this product? EEA is not being tested on server systems, and ESET does not guarantee problems like this won´t happen. So It would be wise to upgrade to an officially supported application first. Edited September 22, 2017 by MichalJ Link to comment Share on other sites More sharing options...
qwerty 0 Posted September 25, 2017 Author Share Posted September 25, 2017 On 22/09/2017 at 1:42 PM, MichalJ said: @qwerty Why are you installing ESET Endpoint Antivirus on a Server system? Why you are not using ESET File Security for Microsoft Windows Server? Is your license not valid for this product? EEA is not being tested on server systems, and ESET does not guarantee problems like this won´t happen. So It would be wise to upgrade to an officially supported application first. Hi Michal, yes you are correct it is due to licensing. We will move to the file security product in future. Link to comment Share on other sites More sharing options...
Recommended Posts