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.
When running appengine tests with windows10 I continually get firewall popups. Since the origin path of the file making the call changes on every test I get popups everytime.
Is there a way to eliminate the firewall popups without fully disabling the firewall.
Yes, you can disable the popups. In the Windows Firewall control panel, go to Advanced Settings, then select Windows Firewall Properties.
For each relevant firewall profile, select Customize from the Settings box. Change the "Display a notification" option to "No".
(In a domain environment, you can also do this via group policy if you need to reconfigure many machines at once.)
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 this code in my WinJS default.html:
<x-ms-webview src="http://localhost/"></x-ms-webview>
<x-ms-webview src="http://display/"></x-ms-webview>
<x-ms-webview src="http://192.168.1.2/"></x-ms-webview>
display is defined in the hosts file:
127.0.0.1 display
and 192.168.1.2 -- the one that is successful -- is another computer on the network.
This is in my appx.manifest:
display and localhost successfully load in IE on the desktop and metro.
My OS is Windows 8.1 Enterprise. I have also completely disabled the Windows Firewall and this has had no effect.
What else can I do?
Microsoft blocks connections to the local machine except while running from the Visual Studio debugger.[1]
There is, however, a workaround tool. Quoting from this post on an MSDN blog:
Immersive applications (and IE11 on the Desktop) run inside isolated processes known as “AppContainers.” By default, AppContainers are forbidden from sending network traffic to the local computer (loopback).
[...]
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.
The aforementioned standalone tool is available from here.
When I try to run netsh wlan start hostednetwork, I get the following message:
C:\Windows\system32>netsh wlan start hostednetwork
The hosted network couldn't be started.
The group or resource is not in the correct state to perform the requested operation.
I'm running this with admin privileges, so it's not the notorious
C:\Users\Kevin>netsh wlan start hostednetwork
You must run this command from a command prompt with administrator privilege.
How do I get the hosted network "in the correct state"?
This happen after you disable via Control Panel -> network adapters -> right click button on the virtual connection -> disable
To fix that go to Device Manager (Windows-key + x + m on windows 8, Windows-key + x then m on windows 10), then open the network adapters tree , right click button on Microsoft Hosted Network Virtual Adapter and click on enable.
Try now with the command netsh wlan start hostednetwork with admin privileges. It should work.
Note: If you don't see the network adapter with name 'Microsoft Hosted Network Virtual Adapter' try on menu -> view -> show hidden devices in the Device Manager window.
Let alone enabling the network adapter under Device Manager may not help. The following helped me resolved the issue.
I tried Disabling and Enabling the Wifi Adapter (i.e. the actual Wifi device adapter not the virtual adapters) in Control Panel -> Network and Internet -> Network Connections altogether worked for me. The same can be done from the Device Manager too. This surely resets the adapter settings and for the Wifi Adapter and the Virtual Miniport adapters.
However, please make sure that the mode is set to allow as in the below example before you run the start command.
netsh wlan set hostednetwork mode=allow ssid=ssidOfUrChoice key=keyOfUrChoice
and after that run the command netsh wlan start hostednetwork.
Also once the usage is over with the Miniport adapter connection, it is a good practice to stop it using the following command.
netsh wlan stop hostednetwork
Hope it helps.
First off, when I went into cmd and typed "netsh wlan show drivers", I had a NO for hosted network support too. Doesn't matter, you can still do it. Just not in cmd.
I think this problem happens because they changed the way hosted networks work in windows 10. Don't use command line.
Just go on your pc to settings>Network>Mobile Hotspot and you should see all the necessary settings there. Turn it on, set up your network.
If it's still not working, go to Control panel>Network and Internet>Network and Sharing Center>Change Adapter Options> and then click on the properties of the network adapter that you want to share. Go to the sharing tab, and share that internet connection, selecting the name of the adapter you want to use to share it with.
I encountered this problem on my laptop. I found the solution for this problem.
Test this command in the command prompt "netsh wlan show driver".
See Hosted network supported.
If it is no,
Then do this
Go to device manager.
Click on view and press on "show hidden devices".
Go down to the list of devices and expand the node "Network Devices" .
Find an adapter with the name "Microsoft Hosted Network Virtual Adapter" and then right click on it.
Select Enable
This will enable the AdHoc created connection, it should appear in the network connections in Network and Sharing Center, if the AdHoc network connection is not appear then open elevated command prompt and apply this command "netsh wlan stop hostednetwork" without quotations.
After this, the connection should appear.
Then try starting your connection. It should work fine.
First check if your wlan card support hosted network and if no update the card driver. Follow this steps
1) open cmd with administrative rights
2) on the black screen type: netsh wlan show driver | findstr Hosted
3) See Hosted network supported, if No then update drivers
Symptoms
You install an application that uses Microsoft Virtual WiFi technology on a computer that is running Windows 7 or Windows Server 2008 R2. However, the application does not work after the computer restarts. Additionally, you receive an error message that resembles the following:
The hosted network couldn't be started. The group or resource is not in the correct state to perform the requested operation.
Cause
This issue occurs because the Virtual Wi-Fi filter driver does not create the Virtual Wi-Fi Adapter correctly when a PNP resource rebalance occurs during the startup process.
Notes
1.This issue may occur when a Plug and Play (PNP) resource rebalance occurs during the startup process. The PNP resource rebalance is usually triggered by a change to the hardware configuration.
2.If you open Device Manager when this issue occurs, you notice that the Virtual WiFi Adapter is not created.
If you can't restart your hostednetwork after rebooting the OS ,just Try this hotfix .It fixed my problem. Or try to figure it out by yourself according to the Symptoms and Cause mentioned at the start of my answer.
Often, I've found that the solution to this problem can be fixed by disabling and then enabling the Wifi hardware. I've made a script to do this automatically instead of doing it manually by going to the device manager. You can find it here
Some fixes I've used for this problem:
Check if the connection you want to share is shareable.
a. Press Win-key + r and run ncpa.cpl
b. Right click on the connection you want to share and go to properties
c. Go to sharing tab and check if sharing is enabled
Run devmgmt.msc from the run console.
a. Expand the network adapters list
b. Right click -> properties on the adapter of the connection you want to share
c. Go to power management tab and enable allow this computer to turn off this device to save power. Restart your laptop if you've made changes.
Check if airplane mode is disabled. You can enable airplane mode and then turn on the wi-fi, you can never know. Do disable airplane mode if it is on.
Use admin command prompt to run this command.
If none of the above answers worked for you, You can try the following solution which worked for me.
Go to Services manager(services.msc) and enable the below services and try again.
WLAN AutoConfig
Wi-Fi Direct Services Connection Manager Service
Hope this solved your problem.
The hosted network won't start if there are other active wifi adapters.
Disable the others whilst you're starting the hosted network.
Fixed by installing "Wifi Direct Access Point". HostedNetwork is not well supported by some Windows 10 drivers.