Within our organisation we are currently experiencing wireless connectivity issues on our Lenovo L14 (Gen 2) laptops when roaming APs. These laptops contain an Intel 6E AX210 wireless chipset.
We are finding that at random times when the laptop roams to another AP (same SSID) it will lose its IP; sitting on a 169 APIPA address. Sometimes this comes back within about 5 - 20 minutes; other times we have to switch the laptop wireless off and on. To clarify; when the device has no IP it is connected to the AP which can be seen both with the signal strength on the laptop and it’s successful authentication in ISE.
We don’t have this issue with our L14 (Gen 1) laptops that have the AX201 chipset.
The only way we have been able to work around this issue, is by disabling all 5Ghz and 6Ghz functionality on the AX210 and forcing it to connect @ 2.4Ghz/g; of course this limits us to 54mbps and this isn’t acceptable.
We have also tried updating the drivers to the latest ones release by Lenovo along with the latest ones from Intel directly (22.150.0.3) and this has made no discernible difference.
Was there any driver/OS update or any other change that may have triggered the issue? Or has it been like that since day one?
its been like this since we bought them; we currently have roughly 200 of these devices with users; many of them are working from home where they essentially only have one AP (their home router) so didn’t have this issue and the low number of on-site users meant reports were sporadic and we spent time looking into AP coverage (not realising the the devices were actually fully connected to the AP, but didn’t have an IP). When we recently started to get more consistent reports from people on site (such as directors) who AP hop and move around the building more frequently we managed to troubleshoot and consistently confirm the mentioned device behaviour,
Thank you for your response. We are going to work on this issue with the information provided. As soon as I have an update or need more information, I will let you know.
Since we have not heard back from you, we will close this thread. If you need any additional information, please submit a new question, as this thread will no longer be monitored.