Skip to main content area Skip to institutional navigation Skip to sub-navigation

System Status and Known Issues

Some Systems are Down

All systems are running normally.

The next scheduled maintenance outage is Friday, January 2 (ALL DAY)

Known Issues

Ongoing issues with technology which we are aware of and actively working to improve.

Unable to log into Single Sign-In

There's currently an intermittent issue which prevents people from logging in.  It only happens occasionally, but if you see an error, wait about 15 minutes and try again.  We're working to fix this.

Unable to open INB from Single Sign-In

This appears to be an issue with security settings or version of Internet Explorer.  We've found that using chrome instead will get you into INB as a workaround.

Unable to use remote control in SSLVPN - juniper client crashes

This error is happening on new operating systems (Windows 8.1 and OS X Mavericks), and occurs because a hardware component is old and out of support.  We're working on getting a new method for VPN up and running as soon as possible.

3/15/2014: A workaround that works consistently is to edit the shortcut to the remote control item (or create a new one) and use the IP address instead of the name.  For example, instead of "IT-termsrv4", you would use ""

Tigernet2 drops connection

The tigernet2 wireless connection will suddenly drop and need to reconnect.  This can happen frequently in the course of normal computer usage, and gets even more frequent when the device moves around (and thus connects to a different wireless access point).

2/13/2014: We implemented a configuration change which has drastically reduced the errors we see in our monitoring tools.  Current drop errors are only about 33% of what they were before the change.

12/7/2013: We implemented a change from 3 wireless controllers down to 1, which should reduce the frequency of drops.

11/3/2013: We are aware that many devices, particularly apple-based are experiencing drops in wireless connectivity on tigernet2.