Jump to content

TomPark

ESET Staff
  • Content Count

    24
  • Joined

  • Last visited

Kudos

  1. Upvote
    TomPark received kudos from Aryeh Goretsky in Blocking IP address 34.102.136.180. Something to do with WPAD   
    Hi All,
    Thank you for the information, like has already been said I think the notification from ESET is a side affect of something else that is changing the domain suffix when connect to the VPN.
    Something that might be of consideration is disabling the 'Auto-Detect' proxy configuration in Chrome / IE which will then stop the browser from looking for these configurations as 'wpad.domain.com' is the default search browser use if this setting is enabled and the information is not provided via DHCP. This should fix the issue for anyone that is still seeing this on their machine. Please note to disable the setting a browser restart will be required.
    As @Marcos said the IP will be unblocked, if anyone is able to test the solution above that would be appreciated. 
    Regards,
  2. Upvote
    TomPark received kudos from Aryeh Goretsky in Blocking IP address 34.102.136.180. Something to do with WPAD   
    Hi Guys, 
    A quick question are all of these machines that are affected domain joined machines?
    Also is anyone using wpad to configure a proxy on the machines connecting to the VPN?
    Regards,
  3. Upvote
    TomPark received kudos from Peter Randziak in ESET Endpoint Security 7 is available for evaluation   
    Hi Peter,
    OK here is a few more updates;
    Install / Upgrade v4.5 to v7 worked but required 2 reboots after first reboot Firewall Module didn't start but second reboot the system started up without any issues. Will re run the test to see if the issue occurs again. Windows 7 Enterprise SP1 Test Environment. Web Control - Time Slots working Multiple configured times in one policy and for a single time slot set on a single group. I will continue testing and update again later.
×
×
  • Create New...