- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
I have purchased a collection of HP ProBook 450 G9 that has an Intel AX211 Wi-Fi card. These devices have the same specs and same hardware. I have attempted to connect to an SSID that uses 802.1x with radius however when I attempt to connect, I get the message can't connect to this network. When I connect to an SSID that uses PSK WPA2 encryption, it will connect just fine. We can connect to the SSID that uses Radius with other devices in the past and they connect without any issues till this day.
I have updated the drivers based on the manufacturers website however the issue still persists.
According to other forums and threads who are facing a similar issue, they have been given a link to a driver that will work for this matter. Would I be able to get this link for the known working driver?
I have attached the SSU log as part of this forum
Thanks
NKerai
- Tags:
- ax211
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello NKerai,
Thank you for posting on the Intel
To start with the troubleshooting please answer the following questions:
- Did it work before with Radius?
- Update the wireless driver to version 22.190.0.4 HP Support. For guidance, you can contact them.
- If the issue persists, update the graphics driver to version 22.220.0.4. For installation steps, Windows Software and Driver Installation Guide for Intel® Wireless Adapters.
Let me know the results.
Regards,
Andres P.
Intel Customer Support Technician
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Andres,
1) These devices are brand new out of the box and they have problems connecting to a radius SSID out of the box. All devices purchased have the Intel® Wi-Fi 6E AX211 wifi card and are all experiencing the same problem. We have had Radius for 12 years and haven't had a problem since these devices were purchased.
2) I have updated the driver to 22.190.0.4 and the issue still persists.
3) I have updated the driver to 22.220.0.4 and the issue still persists.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello NKerai,
Thank you for your response, all the information provided has been really helpful.
I will start with an investigation to provide you with the next steps, as soon I have further information I will let you know.
Regards,
Andres P.
Intel Customer Support Technician
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Andres,
I have done some testing and I have found out that Windows 11 Version 22H2 has problems with connecting with an SSID that uses Radius.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello NKerai,
Thank you for your answer and for keeping me informed.
We have been working on the investigation and it is very unlikely that brand new devices are the root cause of the problem, I would suggest to check with their laptop manufacturer to confirm the cards are working fine in a normal environment, if the issue happens only with Radius is merely a configuration/authentication that must be checked.
Let me know if you have further questions.
Regards,
Andres P.
Intel Customer Support Technician
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello, I hope you are having a good day.
Just to let you know that this is an INTEL wireless cards problem.
I had like 5 new devices with INTEL Wi-Fi 6E AX211 and they didn't connect to my RADIUS WiFi, after doing a month of troubleshooting I couldn't connect the devices, I changed the WiFi cards from the devices to a Realtek card and they connected automatically to my RADIUS WiFi, without doing anything else.
I assume this is a firmware problem, so it would be nice to know if INTEL is working on something to solve this.
Regards.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
we have the same problem with Lenovo laptops and Cisco AP's. I have tried all available firmwares to AX211 but still no success.
I have checked release notes on newest firmwares but there is not anything about this problem.
Br
Jukka
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
As this issue is still currently present, please see my reply from today.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi, i'm having exactly the same issue here with a Surface Pro 9 device Intel(R) Wi-Fi 6E AX211 160MHz card,
drivers which we tested: 22.150.3.1 and 22.220.0.4
PC is running on W11 22621.1848 currently. the PC was never able to connect to our wifi network, while connecting fine to other home or public networks for example.
the AP's we try to connect to: Aerohive AP122 running on 10.6.1.0 and Aerohive AP230 running on 10.5.3.0
in eventviewer we can find back below message:
"The description for Event ID 7021 from source Netwtw12 cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
The message resource is present but the message was not found in the message table"
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I have found the "solution" to this and the reason it appears to be happening, but I don't want to post a step by step for anyone who doesn't understand what they are doing. The root cause to this issue is that the driver/firmware does not have appropriate system access to pull saved credentials from credential guard because its being treated as an external peripheral instead of a system device. If you disable the credential guard via uefi lock, reboot, open up local policy editor and enabled secure boot without DMA protection and re-enable credential guard, your radius Wi-Fi will work.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
I also have an issue with an Intel Network Card AX211. I can't connect to our WiFi through computer authentication over RADIUS server.
We often have AX201 card and it works, but on this new device with the AX211 it does not worked.
This computer is running under Windows11 23H2 (22631.3296). I 've also downloaded and installed the newest card driver (v. 23.30.0.6), but still not working.
What was your solution to this issue?
Regards
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Just ran into this with a bunch of new Dell Latitude laptops that arrived with the AX211 chip. We use 802.1x everywhere here, so pretty disheartened to see this is such a widespread issue. I fully believe this is a driver issue at the core and none of these steps should be necessary, but here we are...
Looking through this thread, I see that ITGinga had found a solution and gave high-level instructions (appreciate that!).
I thought I would spell them out for those who might need some extra guidance like we did.
Pulling from this Microsoft site open an Administrative CMD prompt and paste each of these lines in one-by-one:
mountvol X: /s
copy %WINDIR%\System32\SecConfig.efi X:\EFI\Microsoft\Boot\SecConfig.efi /Y
bcdedit /create {0cb3b571-2f2e-4343-a879-d86a476d7215} /d "DebugTool" /application osloader
bcdedit /set {0cb3b571-2f2e-4343-a879-d86a476d7215} path "\EFI\Microsoft\Boot\SecConfig.efi"
bcdedit /set {bootmgr} bootsequence {0cb3b571-2f2e-4343-a879-d86a476d7215}
bcdedit /set {0cb3b571-2f2e-4343-a879-d86a476d7215} loadoptions DISABLE-LSA-ISO
bcdedit /set {0cb3b571-2f2e-4343-a879-d86a476d7215} device partition=X:
mountvol X: /d
Reboot the computer and when you get the prompt, press the appropriate key to disable.
Now, pulling from this website:
Once the computer has completed booting back into Windows, open the local group policy and drill to:
Computer Configuration/Administrative Templates/System/Device Guard

- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page