Wireless Network Access
Anyone with a valid Seattle University network account has the necessary credentials to use wireless.
There are currently two wireless networks at Seattle University. The wireless network "SU_secure" provides strong authentication and encryption. The wireless network "SU_wireless" has no encryption, but requires authentication to access. Most Seattle University web sites such as MySU, SU Online, and Outlook Web Access are encrypted and secure over "SU_wireless".
Accessing the Service
Connecting to Seattle University's "SU_wireless" is very similar to connecting to any public WiFi hotspot. There are no special security or encryption settings. Once connected to "SU_Wireless" open a web browser and you will automatically be directed to the login page. Enter your Seattle University network account user name and password. Once you successfully authenticate you can continue to the web page you were attempting to access. You should only need to log on with your Seattle University network account once every 24 hours.
Connecting to "SU_secure" requires that your device support WPA2 with AES encryption; all modern systems do. To configure your device, please follow the instructions located here.
Wireless is supported by OIT Network Services. If you have a question about using wireless, are unsure how to use wireless, or if you are experiencing a technical problem, please phone the OIT Help Desk at (206) 296-5571 for assistance and be prepared to provide the following information:
- Your Seattle University network account user name (we will never ask for your password)
- Web browser name and version
- What operating system you are using
- What version of your operating system
- Your specific location - building and room number
- The date and time you encountered the technical difficulty
If the issue is determined to be technical in nature, you will be asked to open a support request with the OIT Help Desk. You can also email your support request, including the information above, to firstname.lastname@example.org
None at this time.