Apparently I was wrong. The failure to reliably authenticate issue was in fact a driver problem. I am now able to connect to PEAP and EAP-TTLS networks reliably using the 2.6.24-22-386 kernel. Now I can connect every time rather than every sixth time.
However, the EAP-TLS issue hasn't gone away. I've tested using Hardy's wpasupplicant, network-manager, network-manager-gnome, and Hardy's network-manager libraries. In every case, each connection attempt led to a successful authentication on the RADIUS server, but Ubuntu failed to connect with the same timeout message. Upgrading to the latest version of wpasupplicant and network-manager packages hasn't helped.
Status: EAP-TLS never works. PEAP and EAP-TTLS work consistently.
Fix: Use 2.6.24 kernel from Hardy packages
So any idea what could cause EAP-TLS networks to fail when the RADIUS server authenticates the user properly and does so promptly? What other packages could be involved?
PARTIAL SOLUTION:
Apparently I was wrong. The failure to reliably authenticate issue was in fact a driver problem. I am now able to connect to PEAP and EAP-TTLS networks reliably using the 2.6.24-22-386 kernel. Now I can connect every time rather than every sixth time.
However, the EAP-TLS issue hasn't gone away. I've tested using Hardy's wpasupplicant, network-manager, network- manager- gnome, and Hardy's network-manager libraries. In every case, each connection attempt led to a successful authentication on the RADIUS server, but Ubuntu failed to connect with the same timeout message. Upgrading to the latest version of wpasupplicant and network-manager packages hasn't helped.
Status: EAP-TLS never works. PEAP and EAP-TTLS work consistently.
Fix: Use 2.6.24 kernel from Hardy packages
So any idea what could cause EAP-TLS networks to fail when the RADIUS server authenticates the user properly and does so promptly? What other packages could be involved?