Hi,
13000 clients (wired, wireless, including Windows 7 clients and Cisco IP phones) are involved in our secured network strategy for many years.
We are using 3x ACS 5.5 servers (virtual machines in vSphere 6 environment) for radius Authentication with vlan "push".
Windows clients are authenticated with PEAP protocol (MS-CHAP v2) and Cisco wireless IP phones with EAP-TLS (mic certificate validation).
On september, Microsoft launched KB3175024 destinated to Windows 7 clients. After installation, Windows 7 clients couldn't connect to network, because they were not authorized by ACS server, with failure message "11514 Unexpectedly received empty TLS message; treating as a rejection by the client".
We opened a case by Microsoft but they were unable to investigate the cause of this issue according to the service PAK.
We investigated to Windows 10 issues, because we got the same error message with some Windows 10 newly configured clients.
We found the solution at this forum (for Windows 10), while upgrading ACS servers from 5.5 to 5.8 release and moving the certificate key strengh from 512 to 2048 bits. That was the modification included in the KB3175024 : As for Windows 10, certificate key must be at least 1024 bits ..
We associated the newly created key for EAP on our third ACS server and pushed (with Cisco Prime Infrastructure) a new Radius order list to our access switches, so as to recover network access and connectivity to any wired clients.
But we didn't change ACS the order of the Radius servers in our wifi controllers (WiSM2), because more than 600 Wireless phones (Cisco 7925G) are using EAP-TLS authentication with MIC, assuming that the former EAP certificate was donwloaded in every 7925G phone, during initial setup (indeed the ACS server must be authentified by the Phone in EAP-TLS handshake).
So the issue is coming here : "how replacing or adding the newly created certificate to every phone without the need to perform hundred of https sessions ?".
Now the primary and the secondary ACS servers are using the same old certificate for answering to wifi controller requests. Another secondary ACS server uses the new certificate as first Radius server for wired clients.
This situation should not stay for a long time, in case of failure of one ore more ACS server and in case of future upgrade ..
Any help would be appreciated,
Best Regards,
Bruno L.
