Hello we have a strange issue which is reoccuring on all HP elitebooks using 8260 and 8265 networks. All drivers after 19.0.1 will fail getting internet access when connected To windows 2012R2 fully updated NPS using certificate (eap-tls)
When we however install a wifi driver earlier or at the level of 19.0.1 it works flawless. For 8260 we have tried 18.40 and it works great and for 8265 we tried the first driver 19.0.1 and it worked great.
All clients no matter the version will be able to connect and authorize radius, they will all get a valid ip adress and dns servers aswell as default gateway but after that the "new" drivers will stop working. Almost like they are missing a route or something.
The network for the Client will not work although the wifi still reports connected , working. on the newer drivers
The solution with using older drivers has worked on 3 of 3 clients all with similar issues so this IS an issue with the intel driver. Windows 10 version has ranged from the newest to 16xx versions, it doesn´t seem to matter
Anything previously reported? any solution to this issue?
Correction, the 8260 driver model is 18.33, 18.40 works sporadically (much better than the new drivers that doesn´t work at all but 18.33 works all the time, flawless)
All drivers works on wpa2-psk so this is only related to eap-tls
As we understand, your systems are not able to connect to the wireless network using Radius EAP-TLS authentication when they have drivers newer than 19.0.1. We haven't had any similar reports, so we would like to check a few items first:
- Are you performing a driver update, or a initial system installation? If possible, try a https://www.intel.com/content/www/us/en/support/articles/000022173/network-and-i-o/wireless-networki... Clean Installation of Wireless Drivers using the https://downloadcenter.intel.com/download/27849/Wireless-Intel-PROSet-Wireless-Software-and-Drivers-... Intel® PROSet/Wireless Software and Drivers for Windows® 10 version 20.60.0.
- Have you tried recreating the wireless profiles from scratch? You can import and configure the profiles to use EAP-TLS using the tools embedded in the OS, such as Windows* wireless configuration utility.
Please let us know if there is any improvement after the clean driver install and recreating the wireless profile.
I have both tried to completely reinstall a computer using a stock win10 1803 image. and the proceed with clean install of 20.60 and it doesn´t work. For the network interface 8265 only the 19.0.1 driver seem to work. Which is the first released driver
For 8260 we had complete success on bothe elitebook 820 G3 and HP revolve using driver 18.33. Nothing else works, 18.40 works sporadically but everything later doesn´t
WIFI profile is the same for all computers tested.
All older computers we have in the company seem to work fine aswell, probably cause they have older drivers
Please try using the drivers provided by the http://www.intel.com/content/www/us/en/support/topics/OEMs.html Computer Manufacturer Support and let us know if there is any change in the behavior.
Also, we would like to know the process you are using to create the wireless profiles. Try recreating the profiles and security configuration from scratch in one of the computers with the issue.
If the issue persist, please provide screenshots of the profile and any errors received. Also, download https://downloadcenter.intel.com/download/25293/Intel-System-Support-Utility-for-Windows-?product=91... Intel® System Support Utility for Windows*, create a log with all options enabled, then save the file to your PC and attach it to this thread using the Advanced options.
We will be waiting for your reply.
Hello, we have been on vacation. I will post the full log file. Its not a problem with the profile since it works with certain drivers, right? Or do you have any known profile issue in newer drivers?
On 7/31/2018 we released newer version of the Intel® PROSet/Wireless Software and I would like you to give it a try. You may download it from this link https://downloadcenter.intel.com/download/27989/Intel-PROSet-Wireless-Software-and-Drivers-for-Windo... https://downloadcenter.intel.com/download/27989/Intel-PROSet-Wireless-Software-and-Drivers-for-Windo...
Please try a clean installation of the wireless driver. This link will give you the steps https://www.intel.com/content/www/us/en/support/articles/000022173/network-and-i-o/wireless-networki... https://www.intel.com/content/www/us/en/support/articles/000022173/network-and-i-o/wireless-networki...
If issue persists please attach to this thread the .txt file the Intel® System Support Utility will generate https://downloadcenter.intel.com/download/25293/Intel-System-Support-Utility https://downloadcenter.intel.com/download/25293/Intel-System-Support-Utility
To attach a file, you must click "Use Advanced Editor" on the upper right hand corner of the response box, then the "attach" option will appear on the bottom right hand corner of the response box.
Shortly after that log was taken i switched to driver 188.8.131.52 and it worked perfect again. The log I posted is taken with your newest driver which you linked, it worked sporadically. Really strange behaviour. Some times it connected to internet after 15 ping drops but mostly not at all.
The old driver is consistent in that it always work. For ordinary wireless networks like wpa2 all drivers work fine, its only when using ad authentication and cert validation. All clients do get validatet using the radius no matter the driver, all clients get an IP from dhcp no matter the driver. But then, its up to the network driver and newer drivers just doesn´t work consistently
Thank you for the feedback you are providing about our latest wireless driver. Please provide the following information so I can investigate this issue further:
Access Point manufacturer, model, & SW version:
I was wondering if you still need assistance regarding the wireless issue you were having. in case still need assistance just let me know.
We are still gathering some information to continue troubleshooting these issues. Please provide the following information:
1. Are the clients able to get a valid IP address if you use newer driver versions such as 184.108.40.206?
2. If so, can the client ping the AP or access to the local network?
Intel Customer Support Technician
Under Contract to Intel Corporation
1. Yes they get a valid DHCP adress
2. No they cannot access anything and as soon as i uninstall the drivers and install the old ones they work immediateley. It is the same behaviour on all clients we have seen with some particular intel NICS mentioned earlier
Older NiCS usually work well with whatever driver still available.
I have sent you a direct email as we are working with engineering on your issue . Is it possible for you to provide over the air traces? If so please reply to the email sent so we can continue troubleshooting.