Pace Secure (Existing Network)

Printer-friendly version

How can I connect to the Pace_Secure wireless network?

If your device (laptop, iPad, Smartphone) was previously configured for Pace_Secure, or if you have a Pace-owned computer on the Pace domain, you should be able to connect to the Pace_Secure wireless network without making any new configuration changes.

Otherwise, simply configure your wireless device to connect to Pace_Connect and follow the instructions to load XpressConnect.   XpressConnect automatically configures your wireless device for the Pace_Secure wireless network.   

Important Notes:

  • XpressConnect works with Windows  (XP, Vista and 7), Mac (Tiger, Leopard, Snow Leopard and iPhone), Ubuntu, and Android devices (except Original Androids which are not compatible with the Pace_Secure wireless network)
  • Running  XpressConnect is a one-time process.  Once completed your device is configured to connect to Pace_Secure.
  • If using an Apple product, once you are connected to Pace_Secure, you should go into your wireless settings and “Forget” the Pace_Guest and Pace_Connect networks.

Attention Mac OS X 10.8 (Mountain Lion) Users:
If you are experiencing issues connecting to Pace_Secure using the process outlined above, there is an alternative configuration process that you can follow.  Please click the following link for detailed instructions: Mac OS X 10.8 (Mountain Lion).


How Do I Set-up My Mobile Device?

You will find instructions on how to configure your wireless devices to connect to the Pace_Secure network by clicking the links below.

Configuration Instructions:

Note: If the Entrust Security Certificate is not installed on your Windows OS, click Root Certificate Update.


General Wi-Fi Configuration Instructions 

Below are general (non OS specific) Wi-Fi configuration information for users who are trying to connect with 3rd party software on their devices.

  • EAP Methods: PEAP with MSCHAPv2
  • Encryption: AES
  • Key Management: CCMP
  • Certificate Details: Certification Authority (2048) and Secure Server Certification Authority