Category: Carleton Service Checker

A hardware issue has been identified as the source of the registration problems. Though the reason this hardware is causing the problem is still unknown it will help with further troubleshooting of this issue. Our systems team is continuing to work on this issue with the vendor.

Our systems team has engaged the support teams from all involved vendors and have worked throughout the day on this issue, but currently there is no known cause, nor ETA for resolution. Click to read more about known workarounds for some devices.

Several people are reporting an inability to connect to the Carleton Guests wireless network via the new ClearPass registration system. Our systems team is aware of and looking into the issue. We do not have an ETA to resolution at the moment, and will provide further details as soon as possible. If you have a Carleton account, please connect to Eduroam (run the profile configuration tool using your full email address to ensure the best connection (https://wiki.carleton.edu/x/usC6)).

Moodle users may have noticed a brief issue this afternoon. Services are restored.

We have been experiencing periodic issues this morning with Carleton sites still hosted in Reason failing to load.  We are investigating the root cause of the issue, but do not…

The DNS issue described in the previous post has been resolved, however sometimes computers cache/store information from when the problem occurred, and some people are still having difficulty loading some sites or connecting to the VPN. If you are unable to load certain pages or connect to the VPN, clearing your DNS cache and restarting your computer may help. Want help with the DNS clear? Call or chat with the helpdesk for support! go.carleton.edu/helpdesk

From approximately 5:15pm to 5:40pm, the service (DNS) that helps map URLs to internet addresses (IP addresses) was not functioning, which caused many sites to load slowly or not at all. We have resolved the issue, though VPN may still not connect. We will provide additional details in a follow-up post.

Just after 10:10am, login access was restored and the timeout issue was resolved. Our systems team and Moodle administrators are continuing to investigate this recurring issue to find a systemic solution.

Just before 10am Moodle began giving 504 gateway timeout errors. Those who were already logged in should not be affected. The issue should self correct momentarily. Our systems team is aware of and monitoring the situation.

The noon reboot has improved, but not completely resolved, the telephone issues.