Wireless Access

Greetings,

what could be the possible reason why Windows10 laptops cant connect thru 802.1x.

while the rest such as Macbook, windows 7 and mobile can connect.

we already configured the station accordingly.

i'm currently using Aruba650 as controller.


any recommendation will be greatly appreciated

#AirheadsMobile

You might hit a change the Microsoft introduces late 2016 that prevents a Windows 10 client from connecting to a Wireless network protected with 802.1X and only offering older ciphers. Windows 10 requires TLS-1.2 supported.

Please check the following post for more information: http://community.arubanetworks.com/t5/Wireless-Access/Authentication-with-EAP-PEAP-on-Windows-10/td-p/252673

In summary, use an external RADIUS server, disable EAP-Termination and if that is not possible make sure you run te latest firmware on your controller that has TLS-1.2 support for EAP. I'm not sure if there is firmware that is recent enough for the 650 controller that has this support, so you might end up with the (preferred) external RADIUS to solve your problem.

Ran into same issue with Win10 clients on 802.1x ensure your have tls v1.2 authentication set as Win10 only uses v1.2 by default tls v1.2 is not enabled on the controller.

 

Your software must be at least 6.4.3 + support TLS v1.2.

 

be warned older clients such as XP will not be authenticated, as they do not support tls v1.2

 

 

THank you very much for your response. saw this firmware on support.arubanetworks and hope this will be enough to support TLS v1.2

ArubaOS_6xx_6.4.4.9_55980

 

also, if I have to enable TLS v1.2 on controller, do I also need to configure something on external RADIUS(AD) or any on win10 workstations?\

 

 

If you enabled EAP Termination on your controller in the 802.1X L2 Authentication Profile, no further changes should be needed.

 

In most situations, it is better to have the termination switched off on your controller and install a RADIUS certificate on your RADIUS server.