XClose

Information Services Division

Home
Menu

Wi-Fi troubleshooting & known issues

General Troubleshooting issues

I Cannot Connect to eduroam

The following check-list resolves a majority of issues:

  1. Authenticating to the eduroam SSID (Wireless Broadcast) requires a valid UCL userid and password. Your UCL userid is provided on the front of your registration slip and must be appended with @ucl.ac.uk (e.g. ucxxzano@ucl.ac.uk). It is NOT the user name @live.ucl.ac.uk!
  2. Ensure DHCP (Obtain IP address automatically) is enabled. View instruction guides on enabling DHCP on your computer.
  3. Ensure Proxy redirect within your web browser (e.g. Microsoft Internet Explorer, Firefox, Apple Safari) is disabled. Proxy URL must also be disabled!
  4. Your Operating System may require additional configuration to connect. Please refer to the Guide for further information.

My Connection is very slow!

Wi-Fi (Wireless) is shared. Therefore, if there are 20 devices connected to 1 Access Point, each device will get roughly an equal share of the total bandwidth. This is known as the contention ratio. We have a program to upgrade our Access Points to increase the available bandwidth. In the meantime, you can either (a) move to a quieter location, or (b) stop Network intensive applications (e.g. P2P, BBC iPlayer, Video Streaming) whilst using the wireless  service.

Also, unlike the Wireless Site Survey which uses accurate measuring tools, wireless adapters may report inaccurate signal strength (i.e reporting excellent signal strength when it is in fact poor). Please ensure you are in an official location listed on the Locations page before requesting support.

Apple IOS (iPhone, iPad, iPod touch) Known Issues
  • If you change your UCL password (typically every 3-months) you must forget the eduroam Network and repeat the Quick Guide.
  • On initial connection your device may prompt: Unable to join the network "eduroam". Dismiss this and try again. If the problem persists, ensure you are not connected to UCLGuest and forget the network if you are. 
  • IOS 10. Recommended you disable Wi-Fi Assist. Select Settings > Mobile Data. At the bottom of the page, toggle Wi-Fi Assist to Off.
Google Android Known Issues
  • Google Android and Kaspersky Mobile Security: Kaspersky Mobile Security configures a manual proxy which is known to cause eduroam configuration issues. This issue is discussed in the following Kaspersky user forum.
  • Google Android Gingerbread 2.3.6: We are aware of an issue with Gingerbread 2.3.6 and Phase 2 Authentication. This will prevent successful authentication on the eduroam service. This appears to be a known issue as a patch is available for Samsung devices via Kies ». This is reported to fix the issue on the Samsung Galaxy Y. For users of none-Samsung devices, please refer to the manufacturer for an update.
  • Google Android Wireless Roaming Issue: There is a known issue with Google Android devices roaming on a Enterprise WPA2 infrastructure, which is what eduroam is based on. i.e. when moving from one location to another you will be disconnected from eduroam. The only know solution is to turn off/ on Wi-Fi and if this fails Forget the eduroam Wi-Fi and re-configure.
  • Google Android 2.2: There is a known bug with 2.2.x Android phones that may prevent automatic connection to eduroam » It is expected that 2.3.3 (Gingerbread) will fix this issue.  A temporary workaround to this bug is to toggle wireless off and on again. It has also been reported that Juice Defender will do this automatically (this is useful if your manufacturer will not issue an OS update).
Common issues for returning Staff & Students

Staff or Students returning from holidays or prolonged periods away from UCL may find their device is unable to connect to eduroam. Below is a check-list of common issues.

  • Password Changed: On some devices, specifically Apple IOS devices (i.e. iPhone, iPad, iPod touch), you will not be prompted to input your new UCL password. Subsequent your connection to eduroam will fail. Please refer to the eduroam connection guides for further information.
  • Certificate Update: On the Monday 2nd July 2012 the eduroam certificate was replaced.
  • WPA2 Enterprise/ AES Encryption Cipher: On Thursday 20th October 2011, support for WPA2 Enterprise/ AES was enabled on eduroam. A majority of clients will automatically re-negotiated using the improved cipher. Clients which are statically configured with WPA1 Enterprise/ TKIP will continue using this cipher until manually re-configured. Please refer to the eduroam connection guides for more information. There are a number of benefits of using WPA2 including improved security, roaming and connection stability.
  • Connection Guides: If your connection still fails, please refer to the eduroam connection guides for more information.
Apple Mac OS X Known Issues
  • Apple Mac Os X Yosemite Wi-Fi Issues: Various forums would suggest the Apple’s Wireless Direct Link (AWDL) service impacts on Wi-Fi performance. The following link provides a workaround but is not supported by UCL and is provided for help only Medium.com.
  • Apple Macbook Intermittent Connectivity: There is a known issue with intermittent connectivity on the Apple Macbook, especially whilst roaming. A fix, and further information was discussed in the following Apple article but this was since removed by Apple.

The synopsis of this article was to Always Trust the orps.jrs.ucl.ac.uk certificate in the Keychain.

  1. Open Finder and navigate to Applications > Utilities > Keychain access.
  2. On the left-hand pane, ensure login is highlighted under Keychains and Certificates under Category.
  3. Highlight the orps.jrs.ucl.ac.uk certificate, right-click and select Get Info from the context menu.
  4. Expand the Trust node and ensure the Extensible Authentication (EAP) is set to Always Trust.
  5. Close the window. You may be prompted for the Username and Password of your machine (not your UCL credentials). Select Update Settings to commit the changes.
  • Apple Mac OS X 10.x Keychain: There is a known issue with invalid items in the Keychain preventing successful authentication. To resolve; Open Finder and select Applications > Utilities (folder) > Keychain Access. This will display a list of items stored in the Keychain. Ensure the login keychain from the left-hand pane is highlighted and delete any reference to eduroam.
  • Apple Mac OS 10.7 (Lion and above) 802.1x: As of Mac OS X Lion (and above) you can no longer modify the 802.1x profile. If you are coming from another institution or you have an old 802.1x profile this can cause connection problems. To resolve, open System Preferences > Profiles and remove the eduroam profile. If Profiles is not available the following workaround is available but not supported by UCL and is provided for help only:

It is strongly recommended you backup your data prior to proceeding! These instructions will wipe any existing Wi-Fi networks! In Finder, navigate to /Library/Preferences/SystemConfiguration and manually rename the following files (e.g. com.apple.airport.preferences.plist.bak):

com.apple.airport.preferences.plist 

com.apple.network.eapolclient.configuration.plist

com.apple.network.identification.plist

networkInterfaces.plist

Microsoft Windows 7
  • Microsoft Windows Security Alert: On first connecting to eduroam you may get a prompt saying the connection attempt could not be complete. Click the Connect button to connect to eduroam. Don't press Terminate - this will cancel the entire connection process and you will have to start again from the beginning.
  • Microsoft Windows 7 Cached User Credentials: An automatic update to Windows 7 introduced an advanced setting. As a result of the update you may be constantly prompted for your credentials when attempting to join eduroam. To fix:
  1. Open the Network and Sharing Center.
  2. Click on Manage Wireless Networks from the left-hand pane.
  3. A list of configured wireless Networks will be displayed. Highlight eduroam and right-click. Select Properties from the context menu.
  4. Select the Security tab. A window similar to the illustrated is displayed.
  5. Select the Advanced settings button.
  6. Ensure the Specify authentication mode option is ticked.
  7. From the drop-down select User authentication. Next select the Save credentials button. 
  8. Set User name to your UCL userid and password. Your UCL userid must be appended with @ucl.ac.uk (e.g. zcxxano@ucl.ac.uk). Set Password to your UCL password.
  9. Click OK to all windows to save the settings.
Microsoft Windows 8 & 10 Known Issues
  • Credentials Not Saved: We are aware of an issue with Windows 8 where a user is constantly prompted to re-enter credentials. This problem appears to be related to the power saving features of Windows 8. Initial reports would suggest manually configuring the eduroam Wi-Fi network connection resolves this issue.

To resolve this please follow the Connecting to eduroam WiFi with Microsoft Windows 8 Guide

  • UCL Password Cached: When your UCL password is updated via (My Account) it is a known issue that Windows 8/10 may not prompt you for the new password. To resolve, Command Prompt by swiping in from the right edge of the screen, tapping Search (or if you're using a mouse, pointing to the upper-right corner of the screen, moving the mouse pointer down, and then clicking Search), entering ‘Command Prompt’ in the search box, and then tapping or clicking Command Prompt. At the prompt, type

netsh wlan delete profile name=eduroam

Microsoft Windows Vista known issues
  • Microsoft Windows Security Alert: On first connecting to eduroam you may get a prompt saying the connection attempt could not be complete. Click the Connect button to connect to eduroam. Don't press Terminate - this will cancel the entire connection process and you will have to start again from the beginning.
  • Microsoft Windows Vista Corrupt TCP/IP Stack: There are known issues with TCP/IP stack and corrupt routing tables in Windows Vista. Either of these issues will prevent successful connection to the Internet. Both issues are rectified via the Command Prompt (Start > All Programs > Accessories > Command Prompt - right-click and "Run as administrator").
  1. To reset the routing table type route /f. You will need to reboot your PC for the changes to take effect.
  2. To reset the TCP/IP stack type netsh int ip reset. You will need to reboot your PC for the changes to take effect. More information about this issue is discussed in Microsoft KB article 299357.