Resolved: BU wireless network (802.1x) was experiencing issues.
Thursday, February 18th, 2021
Incident Discovery Time: 09:33am on 02/18/2021
Time of Resolution: 12:36pm on 02/18/2021
Services Impacted: Network Services
Description of Impact
Some clients on the BUMC campus were unable to connect to 802.1x.
Incident Description and Resolution
IS&T teams have resolved the incident.
Additional Information
The cause of this incident was determined to be a sync error between servers that appeared after a change this morning. The change did not need to be reverted; instead the network team fixed the synchronization problem. The three reports of issues on the CRC campus turned out to be unrelated.
If you continue to have issues, please contact the IT Help Center.
Previous Update
Incident Discovery Time: 09:30am on 02/18/2021
Services Impacted: Network Services
Description of Impact
Clients have reported issues connecting to 802.1x on both the BUMC and CRC campuses.
Current Status
Network operations continues to investigate this issue. After updating the BUMC DHCP servers, it appears that all the BUMC clients are able to use wifi now. We are investigating the CRC reports at this time.
Additional Information
This currently appears to be affecting just a few clients. Workarounds to try include using one of these networks: BU guest , BU requires VPN or Eduroam.
Next Update: 01:30pm
Previous Update
Incident Discovery Time: 09:30am on 02/18/2021
Services Impacted: Network Services
Description of Impact
Clients have reported issues connecting to 802.1x on both the BUMC and CRC campuses.
Current Status
Network operations continues to investigate this issue.
Additional Information
This does not appear to be affecting all users. Workarounds to try include using one of these networks: “BU guest” , “BU requires VPN” or “Eduroam”.
Next Update: 12:30pm
Previous Update
Incident Discovery Time: 09:33am on 02/18/2021
Services Impacted: Network Services
Description of Impact
Clients are reporting issues accessing the BU wireless network, 802.1x.
Current Status
IS&T teams have not yet identified the cause of the incident, but are investigating.
Next Update: 11:30am