Microsoft wireless network report
Collecting information related to interpreting the Microsoft WLANREPORT
netsh wlan show wlanreport
Microsoft: Answers to common questions about NCSI (Network Connectivity Status Indicator)
Reasons for network probe failure
| Output | Description |
|---|---|
| ActiveDnsProbeFailed | The DNS probe failed. Verify via a packet capture. |
| ActiveHttpProbeFailed | The DNS name for the probe server wasn’t resolved. NSCI failed before attempting to send the web probe request. This could be due to DNS failure, failure to connect to the proxy server, etc. Verify via a packet capture. |
| ActiveHttpProbeFailedButDnsSucceeded | The probe server DNS name was resolved but the HTTP probe to that resolved IP address failed. Use a packet capture application and verify the data capture. |
| ActiveHttpProbeFailedHotspotDetected | The HTTP probe didn’t get past a hotspot or captive portal. This is typically determined when an HTTP response 200 is received, but the response payload doesn’t contain the text file connecttest.txt. Alternatively, a non-200 HTTP status code, such as 302 or 304, might be received. This status code will normally be observed when handling issues where the wireless connection cannot be established. Verify via a packet capture. The user may need to authenticate the hotspot or the hotspot configuration may need to be modified. |
| NoAddress | The target adapter has no preferred IP address assigned. There is a bigger issue involved that can't be resolved through NSCI. |
| NoGlobalAddress | Same as NoAddress but specific to IPV6 interfaces. |
| NoRoute | The interface that the probe is being sent on has no route to the internet in the routing table. Some scenarios where this can happen is when a newly connected VPN hasn’t yet changed the routing table with new routes, or in forced tunnel VPN scenarios in which after the VPN interface is connected, the physical interface drops to local connectivity as the route table was modified. |
| PassivePacketHops | Not a failure. Received packets indicate some level of connectivity. This change reason is used when capability is being raised, not lowered. |
-end