AirPennNet-Help and XpressConnect: Known Issues
From Provider Wiki
This page contains known issues with AirPennNet-Help and XpressConnect and identifies workarounds when they have been identified.
- https:// pages are not found when connected to AirPennNet-Help.
- Workaround Identified: This is expected behavior as there is not an https:// listener enabled. Users who receive a not found error should attempt to load a standard page such as: www.upenn.edu for the redirect to work.
Desktop Operating Systems
- Users of very old SecureW2 versions (<3.1) may not be able to connect after running XpressConnect.
- Workaround Identified: Users should uninstall both the old version of SecureW2 and the new version, restart the computer, and re-run the XpressConnect process.
- Out of date wireless drivers will cause SecureW2/XpressConnect to fail.
- Fix Identified: Providers should obtain the latest driver from the device manufacturer, install the newer driver, and re-run the XpressConnect process.
- XpressConnect does not function as expected with Windows 8.
- Workaround Identified:
- From the wireless networks list, select "AirPennNet"
- When prompted for a username and password, enter your PennKey and PennKey Password.
- If you are notified that "Windows can't verify the server's identity", click "Connect".
- This works, but relies on the Window's built-in certificate stores which don't always have all the necessary certificates and sometimes are changed as the result of a software update. A new version of XpressConnect is expected that will work with the Windows native wireless supplicant but will also ensure the appropriate certificate chain is installed to successfully connect to AirPennNet. Once this new version is available, XpressConnect should be used as the exclusive means to configure computers and devices to connect to AirPennNet.
- Workaround Identified:
- Users of a non-Symantec antivirus product (product other than Norton AntiVirus or SEP for Mac OS X) may be prompted that antivirus software could not be detected.
- Workaround Identified: XpressConnect is looking for the installed application LiveUpdate.app on Mac OS X computers. If LiveUpdate is not detected, users will see the antivirus warning. If a product is installed, users can disregard this warning.
- Some users who were able to connect successfully to AirPennNet at the time of running XpressConnect may not be able to connect after rerunning the process. This seems to affect only currently connected/properly configured computers.
- Workaround Identified: These users should reboot their computer and attempt to connect.
- Some Mac OS 10.7 users report issues reconnecting after their computer wakes from sleep/hibernate. These seems to be a new issue introduced with 10.7.1.
- Workaround Identified: This problem can be avoid by turning off wireless connectivity before the computer hibernates or waiting sometimes over 1 minute before the connection is resumed. This problem can occur with any encrypted network.
XpressConnect may not work with all Ubuntu-based operating systems. The vendor has specified support for versions: 9.04, 9.10, 10.04, 10.10, 11.04, 11.10, 12.04.
Mobile Operating Systems
- Android users unable to download XpressConnect application from the Market while connected to AirPennNet-Help.
- Workaround Identified: Users should disconnect from AirPennNet-Help to download the XpressConnect application from the Market. After installing XpressConnect, users should connect to AirPennNet-Help and complete the configuration.
- Android devices install XpressConnect but fail to complete configuration via AirPennNet-Help
- Workaround Identified: Devices need to have an SD Card installed to allow the certificate package to be installed on the device. Some, but not all devices that exhibit this behavior can be successfully connected by running through the AirPennNet-Help configuration a second time. For these devices, the second configuration cycle will work when the first did not.
- XpressConnect may not work with all versions of Android. The vendor has specified support for versions: 2.1, 2.2, 2.3, 3.0, 3.1, 3.2, 4.0, 4.1.
- Inconsistent behavior among Android devices connecting to AirPennNet after configuration: Many Android devices have a user interface overlay which sometimes conflict with the native Android network and certificate management. This affects HTC devices with Sense UI, Motorola devices with Motoblur, and Samsung devices with TouchWiz. Devices with stock builds of Android are generally unaffected. If your user has a problematic device please provide the logs from the device to the Provider Desk.
All devices running BlackBerry OS 10 can connect to AirPennNet using the advanced settings: AirPennNet_Configuration_for_BlackBerry_10
BlackBerry OS 7 (and older) devices lack support for the protocols used by AirPennNet and thus will not connect to the network.
- .mobileconfig file does not load. AirPennNet-Help uses a .mobileconfig file to configure AirPennNet on iOS devices that will not load if the short DHCP lease on AirPennNet-Help expires.
- Workaround Identified: Users encountering this issue should remove existing profile for AirPennNet, power cycle their device, reconnect to AirPennNet-Help and run through the process immediately.
- Device will reconnect to AirPennNet-Help or AirPennNet-Guest after the AirPennNet profile is installed.
- Workaround Identified: These will automatically be forgotten in iOS 5.x and later. For pre iOS 5 releases, wireless networks that users don't wish to connect to should be "forgotten." In Settings-->Wi-Fi , click the blue > next to the SSID and click the "Forget this network" button. This needs to be done for each wireless network that needs to be removed.
Windows Phone 7
Windows Phone 7 does not currently support the protocols in use by AirPennNet. This may be addressed in a future version of the platform.