After the wireless terminal (Win11) connects to Wi-Fi, it frequently disconnects, and only stabilizes after multiple offline and online attempts.
- 0 Followed
- 0Collected ，2487Browsed
Network Topology
Null
Problem Description
After the wireless terminal (Win11) connects to Wi-Fi, it frequently disconnects, and only stabilizes after multiple offline and online attempts.
Process Analysis
Asking customer provide the Wlan report of the win11, and we find the following phenomenon:
It means the windows client NCSI keep detecting the internet periodically. And when the NCSI failed to detect the internet accessing, or NCSI find the internet accessing is limited, it might to reset the NIC Capability, and it would cause the re-connection of the wifi.
For example the log in the wlan report:
Solution
If the client keep re-connecting when it try to connect to the wifi, and you can find the log as above in the wlan report, you can try to turn off the Windows Network Connectivity Status Indicator"s active tests on you windows client.
To enable the policy to turn off the Windows Network Connectivity Status Indicator"s active tests using the Local Group Policy Editor, follow these steps:
1. Press Win + R to open the Run dialog box.
2. Type gpedit.msc and press Enter to open the Local Group Policy Editor.
3. In the Local Group Policy Editor, navigate to the following path: Computer Configuration -> Administrative Templates -> System -> Internet Communication Management -> Internet Communication settings
4. In the right pane, find and double-click on the policy named "Turn off Windows Network Connectivity Status Indicator active tests."
5. In the policy settings window, select the "Enabled" option.
6. Click "OK" to apply the changes and close the policy settings window.
7. Close the Local Group Policy Editor.
NOTE: After turn off the NCSI active tests, the client would stop sending the internet connectivity testing packets when connecting to the wifi. It would prevent the terminal from automatically popping up in a captive portal scenario. However, when the user manually opens the browser, the captive portal authentication can still be used normally.