Performance Issue: Windows Certificate-based Authentication For Eduroam
Last Updated:
2025-02-10 09:50:39
Event:
2025-02-03 10:43:00
Status:
Closed
Brief Description:
There appears to be an issue with Windows-based devices that use the SecureW2 certificate-based authentication for eduroam connectivity. This presents itself as "can't connect to this network." when trying to connect to eduroam/.
User Impact:
Message of "can't connect to this network." when trying to connect to eduroam.
Workaround:
Connect to Cornell-Visitor and login to connect. Once connected, going to https://onboard.it.cornell.edu and going through the oboard process will resolve the issue.
Current Status:
The issue has been resolved.
Services Affected:
Wi-Fi Network Service
Subsites Affected:
Wi-Fi
Full Description:
There appears to be an issue with Windows-based devices that use the SecureW2 certificate-based authentication for eduroam connectivity. This presents itself as "can't connect to this network." when trying to connect to eduroam. The solution for these devices is to connect to Cornell-Visitor and login to connect. Once connected, going to https://onboard.it.cornell.edu and going through the oboard process will resolve the issue.
CIT TDX ID:
1692717
Timeline of Changes
Description | Current Status | Date | Time |
---|---|---|---|
There appears to be an issue with Windows-based devices that use the SecureW2 certificate-based authentication for eduroam connectivity. This presents itself as "can't connect to this network." when trying to connect to eduroam. The solution for these devices is to connect to Cornell-Visitor and login to connect. Once connected, going to https://onboard.it.cornell.edu and going through the oboard process will resolve the issue. |
The issue has been resolved. |
2025-02-10 | 09:50:39 |
There appears to be an issue with Windows-based devices that use the SecureW2 certificate-based authentication for eduroam connectivity. This presents itself as "can't connect to this network." when trying to connect to eduroam. The solution for these devices is to connect to Cornell-Visitor and login to connect. Once connected, going to https://onboard.it.cornell.edu and going through the oboard process will resolve the issue. |
CIT staff are working on the issue. |
2025-02-03 | 10:50:12 |