Thread Info
  • State Not Answered
  • +3 person also asked this people also asked this
  • Locked Locked
  • Replies 29 replies
  • Subscribers 12 subscribers
  • Views 68316 views
  • Users 0 members are here
Options
Suggested
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

MatthewEllis

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
  • 0

    We're also seeing this issue on our domain machines but only those that have 1709+ installed. Had a 2 hour webex with a developer last week in order to try and move things forward. Whitelisting the IP address of one site seems to mean that users can visit any site after visiting that one site. 

  • 0 in reply to MrSoapsud

    Does it help to add the URLs in IE to the trusted site list?


    Also, given the information here:
    https://blogs.msdn.microsoft.com/ieinternals/2012/06/05/the-intranet-zone/

    about how IE classifies the intranet zone.  If the problematic site is a.b.c.com for example, which resolves to 10.1.1.1, then you might expect that both:
    http://a.b.c.com and http://10.1.1.1 would both fail.  However to resolve the site without any '.' (dot) then a hosts file mapping of say:

    10.1.1.1 test

    Would then http://test work if it is then classified as local intranet.

    Regards,
    Jak

  • 0 in reply to jak

    I've been experiencing the same issues.  Randomly thought it was a TLS Edge issue since it was all fine in Chrome/IE.  However, I did notice that the Edge DevTools showed the connection as Pending.  This suggested to me that the connection was blocked before it even got going and wireshark seemed to agree.  I didn't realise at that point that Web Control installed a local proxy.

    Having disabled Web Control, Edge starts working again fine.  One of my developers also noted that when she moved to the guest WiFi instead of our domain network, any website she was having a problem with magically started working.

Reply
  • 0 in reply to jak

    I've been experiencing the same issues.  Randomly thought it was a TLS Edge issue since it was all fine in Chrome/IE.  However, I did notice that the Edge DevTools showed the connection as Pending.  This suggested to me that the connection was blocked before it even got going and wireshark seemed to agree.  I didn't realise at that point that Web Control installed a local proxy.

    Having disabled Web Control, Edge starts working again fine.  One of my developers also noted that when she moved to the guest WiFi instead of our domain network, any website she was having a problem with magically started working.

Children
No Data
Unfiltered HTML