Richard, We ran into the same problem here at Marshall University. After several phone calls, hours of troubleshooting, and multiple packet captures the problem was escalated to the software devs at Cisco. The problem was determined to be on our end in how we named and requested the ssl certs for our manager and server. We were using a mixed case naming scheme (ex: muNACM). We had to revoke our ssl certs, rename in all lower case, and request the certs with the all lower case naming scheme. After doing so, NAC behaved as normal again. A defect was filed with Cisco and hopefully this will be resolved in a later release. I hope this takes care of the problem for you.
Later, Kelly
