sanjay mehta 6 Posted July 26, 2023 Share Posted July 26, 2023 installed bridge on a win 10 PC, using standalone installer, few days back. applied bridge policy. checked client PCs, and all computers were able to connect through the proxy. this bridge works fine till now. installed another bridge for another department yesterday on a similar win 10 PC. the installation was successful, bridge policy was applied. but client PCs not able to connect to proxy. only by disabling the firewall of eset endpoint on the bridge computer, the client was able to find the proxy. what exactly is needed to be allowed in eset endpoint firewall to let the bridge work as proxy ? what app/service/port/protocol/direction ? Link to comment Share on other sites More sharing options...
sanjay mehta 6 Posted July 26, 2023 Author Share Posted July 26, 2023 also please note that since yesterday, when i tried creating a firewall rule & tried to set the precedence of the created rule over pre-existing rules, the cloud sw throws up error (SS attached) Link to comment Share on other sites More sharing options...
ESET Staff IggyPop 20 Posted July 26, 2023 ESET Staff Share Posted July 26, 2023 Hi @sanjay mehta, In regards to the allowed ports I could advise you to review this part of the documentation. However, maybe @Marcos will see something else there which is problematic. Thanks, Iggy Link to comment Share on other sites More sharing options...
Recommended Posts