大网数据广告活动
网络与域名解析

Network Connectivity Status Indicator troubleshooting guide for Windows

· 52CE 我爱测

This guide demonstrates how to perform diagnostics using the Network Connectivity Status Indicator (NCSI) to troubleshoot and determine Internet connectivity.

Troubleshooting NCSI (Network Connectivity Status Indicator) issues are generally performed with packet capture data but NCSI event logs can also be a useful tool when correlated with the packet traffic. This guide serves to assist users on how diagnosing NCSI issues from common scenarios.

View NCSI data using Event Viewer

  1. To open the Event Viewer, right-click on Start > Event Viewer. Alternatively, open the Run prompt by pressing Win+R and typing eventviewer.exe. Screenshot of the Start button context menu with Event Viewer highlighted.

  2. Expand Applications and Service Logs > Microsoft > Windows > NCSI. Screenshot of the Event Viewer with expanded Applications and Service Logs, Microsoft, Windows, and NCSI highlighted.

  3. Right-click NCSI, select View > Show Analytic and Debug Logs. Screenshot of the Event Viewer with NCSI highlighted with Show Analytic and Debug Logs enabled.

  4. Right-click on Analytic under the NCSI folder, select Enable Log. A dialog box may notify you that you may lose Analytic and Debug log events when logging is enabled. Select Ok to proceed. Screenshot of the Event Viewer with the NCSI Analytic event logging enabled.

Retrieve NCSI data using Event Viewer

Performing the actions mentioned above will facilitate in data retrieval. For easier analysis, convert the generated logs to text format. While in the Event Viewer, follow these steps:

  1. Expand Applications and Service Logs > Microsoft > Windows > NCSI.

  2. Right-click on Analytic, select Save All Events As. Screenshot of the Event Viewer with the NCSI Analytic event with save all events being enabled.

  3. The "Save As" dialog box opens. Set the "save as type" to text (*.txt), name your file and select your location. Select Save. Screenshot of the save as dialog window with NCSI logs being saved to the documents folder.

Here's an example of a successful connection output:

Information    4/26/2023 12:17:46 PM    Microsoft-Windows-NCSI    4013    Internet Connectivity Detection    Active Internet Probe started on interface {611346db-8fbb-473d-808b-6c7573b3ef4d}
Information    4/26/2023 12:17:46 PM    Microsoft-Windows-NCSI    4017    Internet Connectivity Detection    Active Internet Probe (HTTP) started on interface {611346db-8fbb-473d-808b-6c7573b3ef4d}
Information    4/26/2023 12:17:48 PM    Microsoft-Windows-NCSI    4005    Wait for Internet Connectivity     Entered State: Internet Connectivity Interface Luid: 0x6008001000000
Information    4/26/2023 12:18:07 PM    Microsoft-Windows-NCSI    4018    Internet Connectivity Detection    Active Internet Probe (HTTP) finished on interface {611346db-8fbb-473d-808b-6c7573b3ef4d}
Information    4/26/2023 12:18:07 PM    Microsoft-Windows-NCSI    4014    Internet Connectivity Detection    Active Internet Probe finished on interface {611346db-8fbb-473d-808b-6c7573b3ef4d} (false)

Here's an example of a failed connection output:

Information    4/26/2023 12:01:02 PM    Microsoft-Windows-NCSI    4013    Internet Connectivity Detection    Active Internet Probe started on interface {611346db-8fbb-473d-808b-6c7573b3ef4d}
Information    4/26/2023 12:01:02 PM    Microsoft-Windows-NCSI    4017    Internet Connectivity Detection    Active Internet Probe (HTTP) started on interface {611346db-8fbb-473d-808b-6c7573b3ef4d}
Information    4/26/2023 12:01:04 PM    Microsoft-Windows-NCSI    4005    Wait for Internet Connectivity     Entered State: Local Connectivity Interface Luid: 0x6008001000000
Information    4/26/2023 12:03:23 PM    Microsoft-Windows-NCSI    4018    Internet Connectivity Detection    Active Internet Probe (HTTP) finished on interface {611346db-8fbb-473d-808b-6c7573b3ef4d}
Warning        4/26/2023 12:03:23 PM    Microsoft-Windows-NCSI    4051    None                               Active probe result code on interface {611346db-8fbb-473d-808b-6c7573b3ef4d} (0x6008001000000 Family: V4) = 12007

Correlate both the Analytic and Operational NCSI events with the packet capture timestamps to determine whether the active probe was fired, if it completed, and why it failed. To learn more about Winhttp error codes, see error messages (Winhttp.h).

How to reproduce a problem scenario

You can troubleshoot an issue by forcing an active probe to see if it completes. The easiest way to do this is to cause a network change event. The following demonstrates this on both wired and wireless connections:

Wired

  1. Disconnect the Ethernet cable. (Alternatively, you can disable the network adapter in Advanced network settings).
  2. Use a packet capture software, such as wireshark, and wait 30 seconds to collect the data.
  3. Reconnect the Ethernet cable. (Or enable the network adapter in Advanced network settings if it was previously disabled).
  4. Wait 60 seconds before stopping the capture to ensure ample time for active probe to be attempted.

Wireless

  1. Start the packet capture prior to the connection.
  2. Connect to the wireless network.
  3. Wait 60 seconds to ensure the active probe activity has fully transpired.
  4. Stop the network capture.

Additional references

Source: Microsoft Learn / Windows Server documentation by Microsoft and contributors (upstream author metadata: robinharwood). Documentation licensed CC BY 4.0. Code samples are covered by the MIT License. Converted from Markdown, with links normalized and embedded media omitted.

资料来源与适用范围

资料来源
Microsoft Learn / Windows Server documentation
适用范围
Windows Server · Source date 06/06/2023
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY 4.0 (documentation), MIT (code samples)

正文与所需资源由本站本地存储。查看来源及更新记录 ↗

请按适用版本和实际日志确认原因;本站没有对每一种系统或设备逐项执行文中的操作。