ivan.perez 0 Posted December 17, 2019 Posted December 17, 2019 We have a PDQ deploy server that is not able to deploy to laptops after ESET is installed. I cannot ping or push software to laptops after ESET is installed. What ESET policy could be blocking this?
Most Valued Members ewong 8 Posted December 18, 2019 Most Valued Members Posted December 18, 2019 Most likely those policies that affect the firewalls (either ESET Security or Windows). Methinks you'll need to check whether or not any of the ports are blocked as mentioned in here. Edmund
Administrators Marcos 5,466 Posted December 18, 2019 Administrators Posted December 18, 2019 Does temporarily pausing the firewall make a difference? If so, what about switching it to learning mode for a while, let it create the necessary rules and then review the rules prior to applying them to other machines via a policy? Is the IP address of the PDQ deploy server in the trusted zone?
ivan.perez 0 Posted December 18, 2019 Author Posted December 18, 2019 5 hours ago, Marcos said: Does temporarily pausing the firewall make a difference? If so, what about switching it to learning mode for a while, let it create the necessary rules and then review the rules prior to applying them to other machines via a policy? Is the IP address of the PDQ deploy server in the trusted zone? The PDQ IP and ports were whitelisted last week. We can't pause because of another issue existing with override policy, opened a thread here: 5 hours ago, ewong said: Most likely those policies that affect the firewalls (either ESET Security or Windows). Methinks you'll need to check whether or not any of the ports are blocked as mentioned in here. Edmund Thanks Edmund, we already whitelisted actually and when removing ESET PDQ works fine.
Recommended Posts