Tjyylli

I have a local IIS running, with a binding like www.dev.mydomain.com, the hostname is listed in an external DNS server and name resolution works fine.

When opening the site http://www.dev.mydomain.com in Microsoft Edge I get this message:

Hmm, we can't reach this page.

Make sure that you’ve got the right web address: http://www.dev.mydomain.com

The F12 Network Tab doesn't show anything.

What does work:

• Using Firefox, Chrome, IE-11 and Command Line tools on the local machine


• Using Edge from another machine on the local network


• Using Edge on the same machine but with a different user


• Using Edge with my user but using localhost or an IP address either 127.0.0.1 or 192.168.x.x
  

What I tried but not solving the problem:

• Restarting the Network List Service and the Network Location Awareness service.


• adding www.dev.mydomain.com to the hosts file.


• using TLS and https://www.dev.mydomain.com
  


• Using the same Windows Proxy settings as for the user which doesn't have the problem.

So this is a problem specific to one user and Edge, other programs or users don't have this problem.

Any ideas what else I can do to diagnose this?

Windows 10 - 1607 (14393.105)

Have you tried updating "Hosts" file?

127.0.0.1 www.dev.mydomain.com 

I'm running the latest win 10 V 1809 build 17763.253.

I found a workaround on another thread, by adding the local IP range to the trusted sites, it works for me.

Second workaround is using the server name instead of the IP address.

Example: http://Computer-name/ which gets resolved to IP version 6 address.

Since this is bug only happens with MS EDGE and works fine with all other browsers, where is the official MS solution ?

Finally build 17763.316 fixed the bug, I removed the workaround and MS Edge can access all my local IP addresses 192.168.1.1 through 192.168.1.254 .

enter image description here

This is a Windows security policy: applications in Windows Runtime (aka. UWP, including Edge) cannot access localhost by default.

Here are more details:
https://blogs.msdn.microsoft.com/fiddler/2011/12/10/revisiting-fiddler-and-win8-immersive-applications/

Immersive applications run inside isolated processes known as “AppContainers.” By default, AppContainers are forbidden from sending network traffic to the local computer (loopback). This is, of course, problematic when debugging with Fiddler, as Fiddler is a proxy server which runs on the local computer. The post went on to explain how the CheckNetIsolation tool can be used to permit an AppContainer to send traffic to the local computer. However, using CheckNetIsolation is pretty cumbersome—it requires that you know the AppContainer’s name or security ID, and you must configure each AppContainer individually. To resolve those difficulties, I have built a GUI tool that allows you to very easily reconfigure an AppContainer to enable loopback traffic. This tool requires Windows 8 and runs on the .NET Framework v4. When launched, the utility scans your computer’s AppContainers and displays them in a list view. Each entry has a checkbox to the left of it, indicating whether the AppContainer may send loopback traffic. You can toggle these checkboxes individually, or use the buttons at the top to set all of the checkboxes at once. Click Save Changes to commit the configuration changes you’ve made, or click Refresh to reload the current configuration settings.

You can got a GUI tool (written by others but with the same feature) here:
https://github.com/tiagonmas/Windows-Loopback-Exemption-Manager

FIX #1

Go to services.msc and start the "DNS client service" and the problem should be fixed.

FIX #2

IF that isn't the solution, try this:

run regedit and go to

HK local machine>software>microsoft>windows nt>current version>network list>profiles>{GUID}"Category"

Find the profile for the network you are interested in and change the category value to 1 from 0.

FIX #2 EXPLANATION

Let me explain what it does: The fix seems to be making sure your network is private rather than public. For some reason this works and i cant explain it.
I would also, like to point out, that if you are using a VPN this is the issue that may have caused it as there are reports of VPN software messing up settings in windows 10. Mostly, i am sure my first fix will help you in this case.