I am running Vagrant for our local web development sites, they all work fine on Chrome, Firefox and even Internet Explorer 11. However when using the Microsfot Edge browser I always get the following message:
Can't reach this page
Obviously this is something unique to Edge, can anyone guess to why this is happening?
I am running the following:
Vagrant 1.9.2
VirtualBox 5.1.2
Windows 10 Home
This happens if I enter the IP or the hostname
Had this problem, Vagrant site wouldnt load on Edge (site not found), but worked on Chrome, IE, Firefox, etc.
The workaround for me was changing the VirtualBox Host-Only Ethernet Adapter’s "*NdisDeviceType" from 1 to 0 and rebooting:
open regedit
navigate to Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class{4d36e972-e325-11ce-bfc1-08002be10318}\00XX.
For me, the path to the registry key "*NdisDeviceType" ended with \0016
set "*NdisDeviceType" to 0
reboot
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.
https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/10142843/#comment-8
Related
I was following this new edx course on Big data on Apache spark. For setting up environment I was told to install virtual-box and vagrant. After installing box and vagrant I restarted my laptop. My modem was working fine, Windows was showing Ethernet connection active but when I try to open any browser and search it was reported that can't connect to internet. I tried uninstalling both box and vagrant but no use. I even restored my system to state when these both applications were not installed but still I can't access internet. What should I do? I'm using Windows 8.1
Just googled a bit and found this:
http://thomascgreen.com/tech/?p=26
Seems to be a working solution.
In any case this is how I got it working again. First go to:
Control Panel > Network and Sharing Center > Change Adapter Settings
Right click on the connection you are having a problem with. In my
case it was “Wireless Network Connection”. On this menu select
“Properties”.
Notice there is a line here that says “Virtual Box Bridged Networking
Driver”. This is Vagrant watching the connection, is my guess.
When I unchecked the box in front of “Virtual Box Bridged Networking
Driver” my internet connection started working again.
Now at this point I started using Google to find out what was going
on. I never found a solution or reason. After searching I rechecked
the box. And everything started working again.
I would also advice to disable/enable all network cards, from the "network connections" panel. (right click on the networks, open the "Network center" and then go to to "update parameters" (I don't have the exact english labels, my Windows isn't in English). It may fix the issue.
I have installed IIS 7 in my PC which runs windows 7. When I and type http://localhost:8080 I am not getting the IIS home page. I tried in IE, Google Chrome and mozilla firefox. In all the browsers I am getting a page 404 error. I don't know what to do.
I have tried the following steps for resolution:
Removed the # symbol from the host file under the system 32 directory
Stopped and restarted the IIS
When I type inetmgr in the run command, the IIS window opens up but I am not getting the default website node.
When I navigate to c:\windows\inetpub\wwwroot, I am not able to see the default website directory.
That's because when you install IIS on your machine it doesn't listen on 8080, it listens on 80
edit
The default site is located in c:\inetpub\wwwroot, never in the windows directory
OK, at first I thought it was a Norton 360 problem so I deleted Norton 360. The Windows firewall is no longer being controlled by it.
Windows firewall is turned off, it's a public location, printer and file sharing is turned on, discovery is on, I reloaded the default settings for the firewall, the owner is administrator which my login is set for. Didn't matter if the Windows firewall was turned on or off, I still got the error message above.
I used to have D shared but took it off. Now when I try to create the share I get the error message above.
I have another Win 7 Pro computer with the same settings as above and I can share everything just fine.
Any ideas on how I can fix this would be greatly appreciated.
I found something nice that fixed my problem...
See solution on: Firewall and sharing folders
I did what he recommend:
export firewall polices from a Windows 7 computer that does not have this problem. (Option on the right most panel of the 3 panel screen for Windows Firewall - advanced)
Copy the .wfw file you exported to your bad firewall computer.
Use the "import Policy" option in Windows Firewall to replace the firewall policy on the bad computer.
It fixed my issue. Firewall is working - so are home groups.
Chrome can be run to support remote debugging by starting it via the command line with a prompt such as chrome.exe --remote-debugging-port=9222 --user-data-dir=C:/foo. This is often used to debug on android or iOs using a Browser on a Desktop Device but I would like to debug chrome running on a desktop PC. from a "client browser" on the same machine one can call localhost:9222 and see the server browser, calling localhost:9222/json will result in a json representation of the tabs open in the "server browser". This works just fine.
However, when I try to use another device in the same (wifi) network by calling [local IP]:9222 or [local IP]:9222/json (local IP is the IP of the server browser) I get a connection timeout. Is it possible to use remote debugging in such way? Are any other switches needed when starting the browser?
Edit I have found some use of forward tcp for the debugging of mobile devices, but there does not seem to be such a switch for chrome.
Edit 2 This seems to be a bit of a duplicate of the questions here and here however, as of yet I have not gotten the solutions presented there to work.
So, apparently this comes down to forwarding a port to localhost:9222. However, at least on windows machines I have no luck with SSH tunnels. Are there any other ways to forward on the machine?
As you've mentioned it, the solution is to forward the port 9222. Below you find approaches for Linux and Windows.
Linux
After having started chrome with
chrome --remote-debugging-port=9222
Forward the port
ssh -L 0.0.0.0:9223:localhost:9222 localhost -N
This way you can access the debuggin interface from an external device on port 9223 using a Chrome browser.
Windows
As seen in this answer, on windows (tested on 7,8) the easiest way to do portforwarding without 3rd party apps is via netsh
I've created a batch file with the following content. It has to be ran as administrator, and with no previous chrome windows open:
netsh interface portproxy delete v4tov4 listenport=9222 listenaddress=0.0.0.0
start /b cmd /c call "\program files\google\chrome\application\chrome.exe" -remote-debugging-port=9222
timeout 5
netsh interface portproxy add v4tov4 listenport=9222 connectaddress=127.0.0.1 connectport=9222 listenaddress=0.0.0.0
This way you can access the debuggin interface from an external device on port 9222.
Make also sure that no firewall is blocking the corresponding port.
You can achieve the same behaviour by adding the argument
--remote-debugging-address=[YOUR_EXTERNAL_IP_ADDRESS] as reported here, without any additional software other than Chrome itself.
I've successfully used RInetD for easy port-forwarding in Windows 7, tried this and it worked like a charm, externally debugging a Chrome browser in Windows from a Chrome in Mac/Ubuntu.
You can download rinetd from:
http://www.boutell.com/rinetd/
Unzip the file, create an empty file with any name (I used rinetd.conf), with this content:
0.0.0.0 9223 127.0.0.1 9222
The in Windows console run it with:
rinetd.exe -c rinetd.conf
And voila!
Im developing a website using VS2008 on Windows 7. I am running a VM with IE6 on it and want to test that the site works ok on IE6. On the VM IE6 browser I type http://192.168.0.100/default.aspx since my router gave the windows host that ip address but the browser errors with : Cannot find server or DNS Error
I can ping the host though through a command window.
Could this be a firewall issue on Windows7 and how can I open it up to allow VM browsing of the host website?
The most dangerouse but simplest way to test this theory:
Open the "Network and Sharing Center". If you look at the left panel at the button there should be a "Windows Firewall" under the "See also" section.
On the left again there should now appear a "Turn Windows Firewall on or off"
So you can now quickly test and see if it is in fact your firewall blocking it.
I would not keep the firewall off, and would consider plugging out the network cable before I do this.
Hope it helps
Rihan