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.
Related
Doc I followed - https://coral.ai/docs/dev-board/get-started/#install-mdt
Python3 version: 3.9
What I have done
Flashed the board with a microSD card.
I have installed MDT and it is working fine.
Connected the dev board via USB, confirmed a new Network Adapter (Remote NDIS Compatible
Device) shows up in Device Manager
Ran mdt devices
What the docs said should happen
connected dev board should be listed
What actually happened
After waiting for some time nothing gets listed (mdt cannot see the
connected device)
Running mdt wait-for-device stalls in "Waiting for device..."
Running mdt shell gives the error, "Waiting for a device... Unable to find any devices on your local network segment."
This might not be the best way to do this, but this did the trick for me:
First connect your board to your PC.
Go to Control Panel > Network and Internet > Network and Sharing Center
Here you will see an Unidentified network click on it and go to Properties.
In properties, go to Sharing and check Allow other network users to connect through this computer's internet connection.
Now try running mdt shell command.
After you have successfully connected your board, make sure to uncheck the previous option in Network Sharing.
I did the above but it did not fix my problem. Here is what fixed it -
Apparently the dev board is seen as a unidentified network under public networks. My Windows Firewall settings blocked python.exe from writing to or reading to public networks. I did the following -
How to check if Windows Firewall is blocking a program
Press Windows Key + R to open Run.
Type control and press OK to open Control Panel.
Click on System and Security.
Click on Windows Defender Firewall.
From the left pane Allow an app or feature through Windows Defender Firewall.
In the allowed apps window, scroll through all the apps.
Locate the app you want to review and see if the app is checked.
(Here the python.exe was not checked. I changed the setting and voila, mdt devices finds the device and everything works on from here.)
If it is unchecked, the app is blocked on the Firewall.
If your program is blocked, simply check the app and click OK.
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
I am trying to install and run my Windows Store app on a real Surface RT device. I have installed the Remote Debugger for ARM and its running, with no authentication on 4018.
Visual Studio fails to see the device, fails to connect and deploy.
In Windows on the desktop, I cannot ping and my port-query tool says 4018 is down, the host is unreachable.
What can I do? Why didn't they just use USB like Windows Phone development?
Microsoft don't tell you this, but you need to configure some firewall rules for the device to become visible on the network. Of course, you won't find anything by searching for "firewall" from the Start screen, but it can be found as a Snap-in for MMC.
You could turn the firewall off for the Private Profile, i.e. your local, private home network, since your home router already has a firewall and the one in Windows is just there to annoy people; cause family members to call and interrupt your dinner while they struggle to get things working on their budget new Windows 8 laptops (with no touch screen), or you could set the right rules manually.
However there's an easier way, turn on the oh-so-discoverable - especially on a tablet that's not even supposed to even have a desktop - "Network discovery and file sharing" by opening Windows (file) Explorer and clicking on the Network node on the left. A bar will pop up to remind you that Windows is getting in the way and that you can click it to make stuff work again; this configures the firewall for you.
Note that turning on "Network discovery..." via the option under Control Panel > Network Sharing Blah > Instantly-forgettable Name doesn't work. No one knows why.
By now you should be able to ping you device and the port is open, just in time for your battery to have gone flat.
Important Edit
Today, its not working again and pop-up doesn't appear again so I cannot try the same trick. My port query tool says the port is not open (it was the other day).
So I tried this, but its not working for me.
# Elevated Command Prompt #
netsh advfirewall firewall add rule name="RemoteDebugger" dir=in action=allow protocol=TCP port=4018
That says 'Ok.' but the port isn't open.
So I went into MMC and added the Firewall snap-in and its enabled itself again for the Private profile.
Then I noticed that it doesn't turn off. If you flip it to Off and hit Apply, it does nothing!!
There are now two inbound rules for the Remote Debugger, the one I setup and another for the executable. Still, doesn't work.
This thread:
http://answers.microsoft.com/en-us/windows/forum/windows_rt-networking/possible-windows-firewall-bug-on-surface-rt-blocks/caa8b40c-dacc-4d19-a751-7a04f8ef00e4
There's an answer stating:
Open Control Panel -> Administrative Tools -> Windows Firewall with Advanced Security.
Click "Windows Firewall Properties" in the main frame
In each of the three tabs of Domain, Private and Public Profile:
1) Note that: If you change "Firewall state", or change "Inbound connections" to "Allow" (inbound connections that do not match a rule are allowed), it is not going to work. The change is immediately lost after you click "OK" or "Apply" to close the dialog box.
2) What you need to do is: click Protected network connections: "Customize", it will show another dialog box, in which you can deselect some network connections. In this case, you can uncheck "Wireless" and leave "Bluetooth" on.
Once you finish step 3, Action Center will pop up an alert, saying Windows Firewall is off or not using recommended settings. You can ignore this alert, or turn it off in "Change Action Center settings".
Though someone on that thread confirm it had worked, it hasn't for me.
Luke
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.
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