Hi,
we're using certificates to authenticate to our corporate wifi network. All went fine using Windows 10. I'm getting reports that there are authentication failures when using Windows 11. Had a look at such a host today. And indeed :
Aug 5 05:40:57 rad-acct-int-update -> 64:bc:58:8a:29:6a 18:64:72:cb:82:d0/wifi-be-di-003 - -
Aug 5 05:51:03 rad-acct-int-update -> 64:bc:58:8a:29:6a 18:64:72:cb:82:d0/wifi-be-di-003 - -
Aug 5 05:59:16 station-down * 64:bc:58:8a:29:6a 18:64:72:cb:82:d0 - -
Aug 5 05:59:19 rad-acct-stop -> 64:bc:58:8a:29:6a 18:64:72:cb:82:d0/wifi-be-di-003 - -
Aug 5 05:59:19 station-up * 64:bc:58:8a:29:6a 18:64:72:cb:82:d4 - - wpa2 aes
Aug 5 05:59:19 station-term-start * 64:bc:58:8a:29:6a 18:64:72:cb:82:d4 1 -
Aug 5 05:59:19 eap-term-start -> 64:bc:58:8a:29:6a 18:64:72:cb:82:d4/auth-dv-authenticated-cert - -
Aug 5 05:59:19 station-term-start * 64:bc:58:8a:29:6a 18:64:72:cb:82:d4 1 -
Aug 5 05:59:19 station-term-end * 64:bc:58:8a:29:6a 18:64:72:cb:82:d4/auth-dv-authenticated-cert 1 - failure
Aug 5 05:59:19 eap-failure <- 64:bc:58:8a:29:6a 18:64:72:cb:82:d4/auth-dv-authenticated-cert - 4
Haven't got all the bits and pieces yet but it seems the issue only happens on a site where the authentication is against a root certificate which is installed on the Aruba controller itself. Can't find anything wrong though. Been searching a little bit and only thing i could find is that servernames in Windows 11 are case sensitive, particularly when using them in an Windows nps config. No nps config here though. Config of the wifi does happens through a gpo.
Anyone encountered already something similar using Windows 11?