We understand that the systems using the Intel® Dual Band Wireless-AC 8260 and Windows® 10 are not able to connect to network if you use profiles created with Intel® PROSet/Wireless Software for IT administrators.
Here are some items for your consideration:
- This may be related to problems in the package and profile itself. Please download the most recent Intel® PROSet/Wireless Software for IT administrators [19.50.1]. Then create a new package, reconfigure the wireless profile and add it to the package.
- When creating the profiles, make sure you specify the right settings for security, authentication and encryption. A mismatch may cause the profile not to work.
Please check the following advisory for more information: Frequently Asked Questions for Enterprise and IT Administrators.
It is worth to mention that Windows® 10 manages the wireless connections by itself, in most cases custom PROset profiles are not required.
I should mention that the machines configured with this profile are able to connect to the same SSIDs in other areas of campus that are not configured with the high density settings on the AP.
So this is not a problem with improper SSIDs, keys or authentication. The fact that these laptops are able to connect manually shows that the problem is not an incompatibility with our APs or driver issues.
In talking with someone knowledgeable in Aerohive's hardware, he thought that the Proset profile might be preventing automatic negotiation of management frame data rates as that is one of the specific settings changes when dealing with an area of high load.
As I stated before, the only three things I am configuring via the ProSet tools are the SSID, TKIP Key and setting the band to 5GHz only.
One of the reasons we chose the Intel hardware is that the ProSet tools make it very easy to manage things like this as we have used it often in the past. Proset makes it easy to package and deploy wireless profiles to lab machines. If we wanted maximum compatibility with our APs and wanted to do all of this via scripting, we could have chosen Broadcom instead of Intel (that is what is in the guts of AeroHive). So in telling me not to use your tools is like telling me not to buy your hardware. ProSet tools should be a selling point, not a hinderance.
We are already using the latest version of everything.
Stephen in TN.
We will need additional information about the issue and environment to work on this. Please check your private messages.
OK, in case any other AeroHive users run into this.
Jonathan sent me the following link and after applying those specific settings along with changing encryption from TKIP to AES ( we use both), it started working great!
Before making the changes in the ProSet profile, it would not connect via either encryption scheme. Originally, I was only configuring the SSID, key, and frequency preferences via the profile.
- Apply the configuration from the advisory Recommended Settings for 802.11n Connectivity:
Again, in our case, the cards would connect manually via the Windows interface without issue. Only the ProSet created profiles were having problems with our AeroHive high density configuration which is used in only one building.
Thank you Jonathan!
We are glad to know our recommendations helped you resolve the issue and that your systems are now working fine.
This will be a good reference for other users as well.