Jump to content


  • Posts

  • Joined

  • Last visited

About paul.f

  • Rank

Profile Information

  • Location
  1. Thank you, the log was sent to you via PM. That did the trick! AnyDesk worked perfectly after narrowing down the ports to 443 only instead of "443, 0-65535".
  2. The firewall rules from my understanding are to block/unblock an specific app, the anydesk was not blocked there and adding an allow rule made no difference. From my understanding the purpose of the firewall rules is different than then white-list feature which takes precedence over it, in other words if the app can't go through the white-list then the app specific firewall rules are useless.
  3. Yeah the website loads fine, but the app doesn't, it won't connect to the servers thus rendering it useless.
  4. Thank you, that's what I was expecting to happen but instead I get the denied notifications, I tried browsing the IP addresses that get denied and all of them resolve to anydesk.com. I'll make a video do demonstrate it.
  5. I have a computer that I white list the domains the user is able to access, this has been working fine for hundreds of websites. Today I tried to white list *anydesk.com* and it didn't work, so I turned on the notification message on the blocked list (*.*) to see what was going on and I noticed that the domain anydesk.com resolves into many different IP addresses when the app anydesk is launched. Bottom line, I can't be white listing every single IP address instead of the domain, and these IPs may change in the future. I need to white list *anydesk.com and I need ESET Endpoint Security to understand that when I launch the app and let it go instead of blocking it. Is there a setting that has to be toggled in order to fix this?
  6. Web and email -> Protocol filtering -> SSL -> SSL protocol checking -> Always scan SSL protocol? Thanks
  7. We are running ESET Endpoint security in our offices to block employees from accessing urls that are not work related such as Facebook, etc and we have thought so far that the Web Access Protection feature was working for us when I realized today that if I add https on any url that is not on my Allowed Addresses list it will go through. www.facebook.com -> BLOCKED: OK https:www.facebook.com -> NOT BLOCKED! I use the allowed addresses list so whatever is not there should not work. How can this be fixed?
  • Create New...