Edge can't connect to virtualbox host-only ip, all other browsers (including IE) work fine

Issue #10142843 • Assigned to Scott L.

Details

Author
jorma d.
Created
Dec 9, 2016
Privacy
This issue is public.
Found in
  • Microsoft Edge
Found in build #
14.14393
Reports
Reported by 11 people

Sign in to watch or report this issue.

Steps to reproduce

  • run a virtualbox ubuntu image (as guest) on windows 10 pro (host) and setup NAT (for guest internet access) and host-only network with a static ip (for access from host machine)
  • all programs can access the guest through the static ip (for example 192.168.56.20)
  • except Edge
  • when I completely disable the windows firewall, Edge is able to connect to guest through the static ip
  • which interaction between Edge and the windows firewall is causing this…?!

Attachments

0 attachments

    Comments and activity

    • Microsoft Edge Team

      Changed Assigned To to “Brad E.”

    • The issue started after TP build 14986. Thought it might be temporary but it still is present. Other browsers all work fine. Would be nice if this is fixed. I did like some of the features on edge, but get by with IE and chrome.

    • Microsoft Edge Team

      Changed Assigned To to “Balaji B.”

    • I’m experiencing this issue as well, but disabling my firewall doesn’t resolve it, so I’m forced to use a different browser when testing sites I’m working on in Virtualbox.

    • I’ve got the same problem. At the moment I’m not taking edge with the initial development progress but will only test the site when at staging.

      I’m using Windows 10 Creative
      Virtualbox 5.1.18
      Vagrant 1.9.3
      Laravel/homestead (virtualbox, 2.1.0)

      Chrome and Firefox work perfectly.

    • Oh and btw, I tried the firewall trick, but that didn’t work.

    • Microsoft Edge Team

      Changed Assigned To from “Balaji B.” to “Scott L.”

    • For me disabling firewall does not work either.

      Windows 10 Pro
      Microsoft Edge 40.15063.0.0
      Microsoft EdgeHTML 15.15063
      VirtualBox 5.1.14 r112924 (Qt5.6.2)

    • I can confirm the issue. Disabling Firewall does not work.

    • I have the same issue, however turning off the firewall does not fix it for me.
      I’ve tried setting the localhost loopback setting - does not fix it for me.

      I’ve has to revert to using Progress Telerik Fiddler Web Debugger to give me some access, but this is not a perfect solution, and one I shouldn’t have to revert too.

      Please fix this issue, it’s making EDGE a nightmare to develop with.

    • I’m using Vagrant/VirtualBox to host dev sites on the local network (192.168.33.*).

      Every browser (including IE) can access the site but Edge states that the website can’t be found (throwing the error ‘INET_E_RESOURCE_NOT_FOUND’). It’s like this on every PC at my workplace, making development with Edge pretty much impossible.

      The firewall solution didn’t work for me, and Allow Loopback is checked but the problem persists. Whitelisting/adding to trusted sites/fiddling with intranet settings in Internet Options does not work either.

      We’re all running Windows 10 Pro, version 1703.
      Edge version 40.15063.0.0, EdgeHTML 15.15063.

    • You can workaround this issue by changing your VirtualBox Host-Only Ethernet Adapter’s "*NdisDeviceType" to 0 and rebooting. You can find the key in Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4d36e972-e325-11ce-bfc1-08002be10318}\00XX. The downside to this is that now you’ll have an “Unidentified Network” in your Network and Sharing Center. It’s also managed by Windows Firewall now and by default it is in the Public Profile and it can’t be really changed easily.

      Another way to do this is to add a loopback exempt and use stunnel to redirect the traffic from localhost to the virtual network adapter.

      The issue seems to have something to do with network isolation, but I’m not sure what. Adding a loopback exempt alone does not help the issue either. I guess at the moment you cannot access an adapter with "*NdisDeviceType" set to 1 from Modern Windows UWP Apps, which are protected by the network isolation feature. Please fix this also for other apps, not just Microsoft Edge.

    You need to sign in to your Microsoft account to add a comment.

    Sign in