jcyrus

Yes. If I disable the ssl/tls protocol filtering I don't get the message from ESET just from my browser. ITMAN- We run a seperate 3rd party firewall so we do not have the ESET firewall enabled and can't therefore add any network to the trusted zones list.

Oh btw. This only started after an upgrade to Eset v6. The clients still running v5 do not have this issue. This is why I believe it to be a setting that we need to adjust.

I appreciate the reply, but this is not what I am looking to do. These webpages/servers are only available internally. I just want to whitelist them so that ESET doesn't flag them. I don't really care about the browsers flagging them. I sent an email to support directly as well as this post and they said to add them to the "url address management" list. I have done this, but I am not seeing any change in behavior. I'll just have to keep looking.

Here is a screenshot of the message. This is what happens whenever we go to any internal server. I am just wondering how to "whitelist" these servers on our network so we do not receive these messages.

I was wondering if there was a way to allow/trust all webpages that are internal. We are have internal webpages have block messages pop up when trying to navigate to the page. I have modified the Endpoint for Windows policy to allow specific ip addresses, but the blocked messages are still showing. Any ideas on how to stop these messages would be greatly appreciated. Thank you all.