Wireless
Issues related to Intel® Wireless Adapters and technologies
6285 Discussions

Intermittent connection on Surface PRO 7 with Intel(R) Wi-Fi 6 AX201 160MHz - Network adapters

paulhorsey
Beginner
4,763 Views

The latest Microsoft driver package and October Windows 10 update, has the driver v22.80.0.9. But getting intermittent connection to a SSID with Radius certificate, all other SSID's are fine.

Updated the driver to 22.80.1.1 (Latest Intel), and the issue still happens, but if I rollback to v22.40.0.7 all Wi-Fi connections work!

 

This issue has been seen on all Pro7's that have been updated with the October 2021 patch!

0 Kudos
23 Replies
DeividA_Intel
Moderator
4,338 Views

Hello paulhorsey,  

  


Thank you for posting on the Intel® communities.   

  


In order to better assist you, please provide the following:  


  


1. Run the Intel® System Support Utility (Intel® SSU) to gather more details about the system.  


· Download the Intel® SSU and save the application on your computer: https://www.intel.com/content/www/us/en/download/18377/intel-system-support-utility-for-windows.html  


· Open the application, check the "Everything" checkbox, and click "Scan" to see the system and device information. The Intel® SSU defaults to the "Summary View" on the output screen following the scan. Click the menu where it says "Summary" to change to "Detailed View".  


· To save your scan, click Next and click Save.  


  

2. Is this the original adapter that came pre-installed on your computer or did you change/install the adapter to this one?   


3. What is the brand and model name of your router?


4. Have you reported this issue to the laptop manufacturer?



Regards,    


Deivid A. 

Intel Customer Support Technician 


paulhorsey
Beginner
4,322 Views

2. Is this the original adapter that came pre-installed on your computer or did you change/install the adapter to this one?   

Yes, it's a surface Pro. So I cannot change it!

 

3. What is the brand and model name of your router?

Cisco Meraki setup MX68, MS225 and MR42

 

4. Have you reported this issue to the laptop manufacturer?

Yes, Microsoft is aware.

2bsoni
Beginner
962 Views

Hi DeividA_Intel,

we do face the similar issue, is there any fix released for this; kindly be advised? as on the website - i see the latest drivers.

 

Problem:

 

1. Abrupt intermittent WiFi disconnections while working (system is not in sleep or idle mode)

2. some times, WiFi signal remains stable - but no internet message comes.

 

System Manufacturer: Microsoft Corporation

System Product Name: Surface Pro 7

BIOS Date:11/16/2020

BIOS Version:9.102.140

OS Build:19041.1.amd64fre.vb_release.191206-1406

Device: Intel(R) Wi-Fi 6 AX201 160MHz

Current driver version: 22.80.0.9

Driver date: 8-19-2021

DevNode flags: 0x180200a

2bsoni
Beginner
886 Views

Can someone please update!?

DeividA_Intel
Moderator
4,292 Views

Hello paulhorsey, 



In order to help you further, please try the following:



1. Have you tried with the Microsoft drivers?

2. Does the issue occur with both bands (2.4GHz and 5GHz)?

3. Try clean installation of the drivers:

- steps:https://www.intel.com/content/www/us/en/support/articles/000022173/wireless/intel-wireless-products....

- Driver: https://www.intel.com/content/www/us/en/download/19351/windows-10-and-windows-11-wi-fi-drivers-for-i...

4. Have you performed all the Windows updates, including the optional updates?




Best regards, 


Deivid A.  

Intel Customer Support Technician 


paulhorsey
Beginner
4,265 Views

Hi Deivid,

 

Yes the new driver was from the Microsoft October patch and driver release via Windows update, this has happened on all our Surface Pro 7 devices!!

 

Yes it happens on both bands

 

Tried this and it still happens on your latest driver.

 

Only fix is to roll back the driver!!

DeividA_Intel
Moderator
4,184 Views

Hello paulhorsey, 


  


Thank you for the information provided 


  


I will proceed to check the issue internally and post back soon with more details. 


  


Best regards, 


Deivid A.  

Intel Customer Support Technician 


DeividA_Intel
Moderator
4,129 Views

Hello paulhorsey, 



As of now, there are some customers reporting a similar situation as you are experiencing so Intel has started working directly with AP manufacturer and Microsoft to understand where the root cause of the problem is. As of now we have analyzed several logs from several customers and working together to find possible reasons.


One common factor that we have noticed is that some customers have the CCKM (Cisco Centralized Key Management) option enabled by default so we would like to ask if you could test by disabling at WLC level option and report back the behavior.


Some other customers have reported that disabling the 802.11R (Fast transition feature) also seems to fix the problem. 


- Make sure that Windows® 10 Wi-Fi Drivers for Intel® Wireless Adapters - Version: 21.60.2 or later is installed:

https://downloadcenter.intel.com/download/29258/Windows-10-Wi-Fi-Drivers-for-Intel-Wireless-Adapters 



In the meantime, we need customers to also open a case directly with Microsoft to get all cases tracked. So if you could please do so will be great.


We will keep you posted on any new updates.


Thanks for your patience and understanding.



Regards,    


Deivid A.  

Intel Customer Support Technician  


paulhorsey
Beginner
4,116 Views

HI Deivid,

 

I assume these setting are on the AP, rather than the WIFI driver?

 

Checked the Meraki SSID setup and 802.11r is already disabled, but there is no option for WLC on Meraki.

 

Thanks

ako90
Novice
4,073 Views

We have the same issue with WiFi 802.1x RADIUS.

My open case number 05268311.

Intel has not found a solution so far, others people opened a same case (look hier: https://community.intel.com/t5/Wireless/Intel-WiFi6-AX201-160Mhz-L3-Issues-with-RADIUS-Authenticatio... and hier: https://community.intel.com/t5/Wireless/Intel-R-Wi-Fi-6-AX201-160MHz-22-80-1-1-disconnects/m-p/13265...

 


The fact is that it is an Intel WiFi adapter and not a firewall/rotuer problem!

 

DeividA_Intel
Moderator
4,058 Views

Hello paulhorsey, 



Thanks for the details. Also, I would like to know if you were able to open a case with Microsoft, if so can you provide me with the case number?



Regards,  


Deivid A.  

Intel Customer Support Technician  


paulhorsey
Beginner
4,004 Views

yes, 2111030050001427

Blu-Ripper
Beginner
3,990 Views

Hi @paulhorsey 

What's your specifc user experience with this issue? I'm wondering if it's the same as ours.

Our Surface Laptop 3's and Surface Pro 7's running that same wifi6 adaptor, and either driver 22.80.0.9 or 22.80.1.1, have an intermittent issue where the devices stay connected to the wifi6 AP's ok, but they randomly get 'No Internet' message and no connectivity.

So far all we seem to be doing is going back and forth with MS with the same info and logs. Occasionally we're asked for different logs but it feels it's just dragging it out.

DeividA_Intel
Moderator
3,967 Views

Hello paulhorsey, 



Thanks for the case number, I will proceed to perform further research on this situation and as soon as I have any details I will let you know.




Regards,  


Deivid A. 

Intel Customer Support Technician 


paulhorsey
Beginner
3,929 Views

Yes that's the same as us. Hopefully Microsoft will pull the driver update and Intel will get a working driver!

DeividA_Intel
Moderator
3,871 Views

Hello paulhorsey, 



I would like to advise you to keep checking with Microsoft since they will need to release a customized driver for their system.


Thanks for your comprehension.



Regards,    


Deivid A.  

Intel Customer Support Technician  


paulhorsey
Beginner
3,760 Views

True Deivid, but the issue also happens on the latest Intel driver!!

KeviReag
Beginner
3,697 Views

Deivid A.,

 

The issue affects the following operating systems:

  • Windows 10 x64
  • Windows 11 x64

For us, the issue affects these manufacturers:

  • Microsoft Surface
  • Dell Precision

We can reproduce the issue on the following build configurations:

  • As delivered from OEM
  • On an laptop installed from ISO

For the following Intel NIC: (We can reproduce the issue on ANY computer with this NIC)

  • Intel(R) Wi-Fi 6 AX201 160MHz

With the following wireless authentication:

  • 802.11x

With any of the following drivers: (all previous versions of the driver do not have the issue)

  • 22.70.0 (supplied by Intel or by vendor)
  • 22.80.1 (supplied by Intel or by vendor)
  • 22.90.0 (supplied by Intel or by vendor)

So please realize that this is not a Microsoft or Dell issue, this is an Intel issue.  We can turn the issue on/off by rolling the driver forward and backward.  All older versions of the driver work as desired.  The three newest drivers do not.

The issue:

  • The AP and the laptop both register as connected with each other at all times
  • At the 802.11x re-authentication interval, the laptop CAN lose it's IP address, and the wi-fi status shows 'no internet access' (but still connected to the AP).  This does NOT always happen.  If you decrease the re-auth interval to 5 minutes you can easily repeat the issue within 30 minutes.
  • A packet capture on the laptop shows the DHCP handshake initiates repeatedly, but never finishes, thus the laptop loses its IP address.
  • If you hard code the IP address, or if you hard code the DNS server, the issue does not happen.  I think that this is the key to fixing the issue.  This is DHCP and DNS related, but I think specifically DNS because hard coding the DNS server does not make sense as a fix to the issue.
  • Rolling back the driver fixes the issue.
  • Packet captures on the AP show the DHCP offer being passed along to the laptop.
  • Packet capture on the laptop never shows the offer arriving.  Eventually it will get one, see next line.
  • Eventually an IP address is negotiated.  The outages range from 5 seconds to hours, but it always recovers.

 

Respectfully,

KeviReag

RZimmer
Beginner
3,308 Views

Hi there!

 

I would row myself in on this issue as we encounter exactly the same problems as KeviReag described.

Using 22.60 driver version fixes the issue. But with 22.70 (which Windows Update is rolling out) and upwards, the described problems return.

 

------------------------------------

If you trace with Netmon it will look like this:

 

397935 16:20:55 06.12.2021 6053.4864153 [502FA8 8D76CF] [B89A2A BF8C81] EAP EAP:Request, Type = Identity {EAP:6899}
397936 16:20:55 06.12.2021 6053.5014914 [B89A2A BF8C81] [502FA8 8D76CF] EAP EAP:Response, Type = Identity {EAP:6899}
397937 16:20:55 06.12.2021 6053.5140436 [502FA8 8D76CF] [B89A2A BF8C81] EAP EAP:Request, Type = EAP-TLS {EAP:6899}
397938 16:20:55 06.12.2021 6053.5145527 [B89A2A BF8C81] [502FA8 8D76CF] EAP EAP:Response, Type = Nak (Response only) {EAP:6899}
397939 16:20:55 06.12.2021 6053.5248101 [502FA8 8D76CF] [B89A2A BF8C81] EAP EAP:Request, Type = PEAP,PEAP start {EAP:6899}
397940 16:20:55 06.12.2021 6053.5270489 [B89A2A BF8C81] [502FA8 8D76CF] TLS TLS:TLS Rec Layer-1 HandShake: Encrypted Handshake Message. {TLS:6901, SSLVersionSelector:6900, EAP:6899}
397941 16:20:55 06.12.2021 6053.5427443 [502FA8 8D76CF] [B89A2A BF8C81] TLS TLS:TLS Rec Layer-1 HandShake: Encrypted Handshake Message.; TLS Rec Layer-2 HandShake: Encrypted Handshake Message. {TLS:6901, SSLVersionSelector:6900, EAP:6899}
397942 16:20:55 06.12.2021 6053.5444753 [B89A2A BF8C81] [502FA8 8D76CF] EAP EAP:Response, Type = PEAP {EAP:6899}
397943 16:20:56 06.12.2021 6053.5546803 [502FA8 8D76CF] [B89A2A BF8C81] EAP EAP:Request, Type = PEAP {EAP:6899}
397944 16:20:56 06.12.2021 6053.5563656 [B89A2A BF8C81] [502FA8 8D76CF] EAP EAP:Response, Type = PEAP {EAP:6899}
397945 16:20:56 06.12.2021 6053.5668667 [502FA8 8D76CF] [B89A2A BF8C81] EAP EAP:Request, Type = PEAP {EAP:6899}
397946 16:20:56 06.12.2021 6053.5683196 [B89A2A BF8C81] [502FA8 8D76CF] EAP EAP:Response, Type = PEAP {EAP:6899}
397947 16:20:56 06.12.2021 6053.5787781 [502FA8 8D76CF] [B89A2A BF8C81] EAP EAP:Request, Type = PEAP {EAP:6899}
397948 16:20:56 06.12.2021 6053.5803049 [B89A2A BF8C81] [502FA8 8D76CF] EAP EAP:Response, Type = PEAP {EAP:6899}
397949 16:20:56 06.12.2021 6053.5904159 [502FA8 8D76CF] [B89A2A BF8C81] EAP EAP:Request, Type = PEAP {EAP:6899}
397950 16:20:56 06.12.2021 6053.5920119 [B89A2A BF8C81] [502FA8 8D76CF] EAP EAP:Response, Type = PEAP {EAP:6899}
397951 16:20:56 06.12.2021 6053.6022636 [502FA8 8D76CF] [B89A2A BF8C81] EAP EAP:Request, Type = PEAP {EAP:6899}
397952 16:20:56 06.12.2021 6053.6089628 [B89A2A BF8C81] [502FA8 8D76CF] TLS TLS:TLS Rec Layer-1 HandShake: Encrypted Handshake Message.; TLS Rec Layer-2 Cipher Change Spec; TLS Rec Layer-3 HandShake: Encrypted Handshake Message. {TLS:6901, SSLVersionSelector:6900, EAP:6899}
397953 16:20:56 06.12.2021 6053.6210088 [502FA8 8D76CF] [B89A2A BF8C81] EAP EAP:Request, Type = PEAP {EAP:6899}
397954 16:20:56 06.12.2021 6053.6489297 [B89A2A BF8C81] [502FA8 8D76CF] EAP EAP:Response, Type = PEAP {EAP:6899}
397955 16:20:56 06.12.2021 6053.6595320 [502FA8 8D76CF] [B89A2A BF8C81] EAP EAP:Request, Type = PEAP {EAP:6899}
397956 16:20:56 06.12.2021 6053.6611350 [B89A2A BF8C81] [502FA8 8D76CF] EAP EAP:Response, Type = PEAP {EAP:6899}
397957 16:20:56 06.12.2021 6053.6718429 [502FA8 8D76CF] [B89A2A BF8C81] EAP EAP:Request, Type = PEAP {EAP:6899}
397958 16:20:56 06.12.2021 6053.6792333 [B89A2A BF8C81] [502FA8 8D76CF] EAP EAP:Response, Type = PEAP {EAP:6899}
397959 16:20:56 06.12.2021 6053.7004428 [502FA8 8D76CF] [B89A2A BF8C81] EAP EAP:Request, Type = PEAP {EAP:6899}
397960 16:20:56 06.12.2021 6053.7031790 [B89A2A BF8C81] [502FA8 8D76CF] EAP EAP:Response, Type = PEAP {EAP:6899}
397961 16:20:56 06.12.2021 6053.7141900 [502FA8 8D76CF] [B89A2A BF8C81] EAP EAP:Request, Type = PEAP {EAP:6899}
397962 16:20:56 06.12.2021 6053.7162580 [B89A2A BF8C81] [502FA8 8D76CF] EAP EAP:Response, Type = PEAP {EAP:6899}
397963 16:20:56 06.12.2021 6053.7462100 [502FA8 8D76CF] [B89A2A BF8C81] EAP EAP:Success {EAP:6899}
397964 16:20:56 06.12.2021 6053.7462100 [502FA8 8D76CF] [B89A2A BF8C81] EAPOL EAPOL:EAPOL-Key (4-Way Handshake Message 1), Length = 117
397965 16:20:56 06.12.2021 6053.7746800 [B89A2A BF8C81] [502FA8 8D76CF] EAPOL EAPOL:EAPOL-Key (4-Way Handshake Message 2), Length = 119
397966 16:20:56 06.12.2021 6053.7766500 [502FA8 8D76CF] [B89A2A BF8C81] EAPOL EAPOL:EAPOL-Key (4-Way Handshake Message 3), Length = 151
397967 16:20:56 06.12.2021 6053.7768100 [B89A2A BF8C81] [502FA8 8D76CF] EAPOL EAPOL:EAPOL-Key (4-Way Handshake Message 4), Length = 95
397968 16:20:56 06.12.2021 6053.7999887 0.0.0.0 255.255.255.255 DHCP DHCP:Request, MsgType = REQUEST, TransactionID = 0x67EB86C6 {DHCP:25334, UDP:6903, IPv4:6902}
397985 16:20:58 06.12.2021 6055.7370328 0.0.0.0 255.255.255.255 DHCP DHCP:Request, MsgType = REQUEST, TransactionID = 0x67EB86C6 {DHCP:25334, UDP:6903, IPv4:6902}
397988 16:20:59 06.12.2021 6057.1668932 0.0.0.0 255.255.255.255 DHCP DHCP:Request, MsgType = REQUEST, TransactionID = 0x67EB86C6 {DHCP:25334, UDP:6903, IPv4:6902}
398002 16:21:03 06.12.2021 6060.9055630 0.0.0.0 255.255.255.255 DHCP DHCP:Request, MsgType = REQUEST, TransactionID = 0x67EB86C6 {DHCP:25334, UDP:6903, IPv4:6902}
398031 16:21:08 06.12.2021 6066.3318405 0.0.0.0 255.255.255.255 DHCP DHCP:Request, MsgType = REQUEST, TransactionID = 0xE23500DE {DHCP:25337, UDP:6903, IPv4:6902}
398036 16:21:11 06.12.2021 6069.0534811 0.0.0.0 255.255.255.255 DHCP DHCP:Request, MsgType = REQUEST, TransactionID = 0xE23500DE {DHCP:25337, UDP:6903, IPv4:6902}
398042 16:21:13 06.12.2021 6071.4142146 0.0.0.0 255.255.255.255 DHCP DHCP:Request, MsgType = REQUEST, TransactionID = 0xE23500DE {DHCP:25337, UDP:6903, IPv4:6902}
398089 16:21:29 06.12.2021 6086.7011164 0.0.0.0 255.255.255.255 DHCP DHCP:Request, MsgType = DISCOVER, TransactionID = 0xC43A687B {DHCP:25338, UDP:6903, IPv4:6902}
398120 16:21:33 06.12.2021 6090.6718175 0.0.0.0 255.255.255.255 DHCP DHCP:Request, MsgType = DISCOVER, TransactionID = 0xC43A687B {DHCP:25338, UDP:6903, IPv4:6902}
398180 16:21:37 06.12.2021 6094.6645557 0.0.0.0 255.255.255.255 DHCP DHCP:Request, MsgType = DISCOVER, TransactionID = 0xC43A687B {DHCP:25338, UDP:6903, IPv4:6902}
398209 16:21:46 06.12.2021 6103.6534555 0.0.0.0 255.255.255.255 DHCP DHCP:Request, MsgType = DISCOVER, TransactionID = 0xC43A687B {DHCP:25338, UDP:6903, IPv4:6902}
398218 16:22:01 06.12.2021 6119.5041527 0.0.0.0 255.255.255.255 DHCP DHCP:Request, MsgType = DISCOVER, TransactionID = 0xC43A687B {DHCP:25338, UDP:6903, IPv4:6902}
398239 16:22:33 06.12.2021 6150.9918875 0.0.0.0 255.255.255.255 DHCP DHCP:Request, MsgType = DISCOVER, TransactionID = 0x71F5114D {DHCP:25354, UDP:6903, IPv4:6902}
398242 16:22:36 06.12.2021 6154.4980599 0.0.0.0 255.255.255.255 DHCP DHCP:Request, MsgType = DISCOVER, TransactionID = 0x71F5114D {DHCP:25354, UDP:6903, IPv4:6902}
398253 16:22:45 06.12.2021 6163.2395850 0.0.0.0 255.255.255.255 DHCP DHCP:Request, MsgType = DISCOVER, TransactionID = 0x71F5114D {DHCP:25354, UDP:6903, IPv4:6902}

----------------------------------------------------

This is 100% reproduceable with 22.70 and upwards. Wireless connection retains while IP address is lost and the adapter will not get a new one.

 

Regards,

Ray

paulhorsey
Beginner
3,595 Views

Hi @KeviReag 

 

I tried your fixed DNS entry fix on my Pro7 and sorry to say it still happened! dropped connection after about 20 minutes and then recovered 30 seconds later  

 

Thanks

Reply