This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Web filtering issues using Microsoft Edge

Have run into a weird issue and wonder if anyone has seen this.

 

On our domain joined machines (only domain joined, issue does not present if not domain joined), we have been having issues accessing corporate URLs when using Edge.

 

The pages fail to load with the generic "Hmmm...can't reach this page" error from Edge.

 

After a long search it was discovered that the sites would load if the Sophos Web Filter service was stopped.  If you stopped this service, loaded any of the sites, you could then start the service and all would be well, even following reboot.

This led us to the discovery that stopping the service allowed for the writing of this reg key:

 

[HKEY_CURRENT_USER\Software\Classes\Local Settings\Software\Microsoft\Windows\CurrentVersion\AppContainer\Storage\microsoft.microsoftedge_8wekyb3d8bbwe\MicrosoftEdge\TabProcConfig]

"corporatedomain.com=dword:00000179

 

This works within Windows 10, but not Windows 7.

 

Any ideas how to resolve this issue?



This thread was automatically locked due to age.
Parents
  • Hi,

    There is no EDGE browser for the Microsft Windows 7 platform. 

    Create a new web category and add your domain to the newly created category. 

     

    Regards,

    Deepak Kumar

    Regards,

    Deepak Kumar

    Sophos Architect | NSE 4 | CCNP | CISE 

  • I am afraid I do not follow your solution.

     

    I am using an on-premise SEC version 5.5.0 to manage the endpoints.

     

    Under web control, I have options for category blocking, or to assign website exceptions (allow/block).  Is that what you are referencing?

  • Hi,

    Yes, I am talking about website exceptions as you can do it. There are multiple possibilities to do the same as a tag on a website, add customized category etc. 

     

    Regards,

    Deepak Kumar

    Regards,

    Deepak Kumar

    Sophos Architect | NSE 4 | CCNP | CISE 

  • This doesn't seem like best practice, as I do not want to whitelist our entire web domain space.  Given the size and distributed nature of our organization, it is possible that some sites within our domain might become compromised.

     

    Is this the only option?  Also, why does this issue only affect Edge and not other browsers?

Reply
  • This doesn't seem like best practice, as I do not want to whitelist our entire web domain space.  Given the size and distributed nature of our organization, it is possible that some sites within our domain might become compromised.

     

    Is this the only option?  Also, why does this issue only affect Edge and not other browsers?

Children