Campus Wireless Access - Troubleshooting

Troubleshooting Resources

Known Issues

The following are specific problems that have been encountered at one time or another outside of standard authentication issues.

Windows

  • Windows XP Fast User Switching /Login Screen

The AEGIS client for Windows XP disables Windows XP's Fast User Switching option, which causes Windows XP to revert to a username/password based login screen.

This is not a bug in the software. It is caused due to the way Meetinghouse Communications is hooking into Windows to provide single-sign on capabilities. AEGIS is working on a fix for the problem.

Meetinghouse has provided the following tool for restoring Windows XP to its previous state. The Fast User Switching problem and this tool were both created by Meetinghouse, so please contact them regarding the issue. This tool is provided for your convenience but IS NOT SUPPORTED. Meetinghouse GINA Removal Tool (http://www.mtghouse.com)

  • Windows Blue Screen / Laptop Reboots

We have seen situations where laptops will reboot when a wireless card is inserted, and the AEGIS client is running. It is currently not clear whether this is a bug with the AEGIS client, or the card drivers. We are attempting to identify the problem more thoroughly.

Cards that are affected include:

  1. Proxim's 802.11a/b/g Combo Card. (The 802.11a/b Combo Card is not affected.)
  2. NetGear's 802.11a/b Combo Card.
  • Novell Client for Windows / AEGIS Incompatibility

The same problem that disables Fast User Switching also creates an incompatibility with Novell Client for Windows. If you need to run Novell Client, do not install the AEGIS client. Assistance is available if you have already installed AEGIS; contat the Campus Help Desk at 1-4000 for additional information.

Mac OS X

 

  • Mac OS X Repeated Kernal Panics

Occasionally, Mac OS X can get into a state where it repeatedly panics on boot. This seems to be related to the AEGIS client, but we have not been able to successfully reproduce it. Removing the Meetinghouse KEXT in single user mode fixes this problem.

  • Mac OS X Requires Static WEP Key

    Mac OS X has issues automatically acquiring the association key from the access point, and as such, we have been forced to configure a static WEP key for use on our wireless network. We are working on this issue and hope to eventually be able to provide connectivity for Mac OS X users that does not require this step.

Linux

  • Linux Requires Static WEP Key

Common Authentication Issues:

My laptop gets to the "Started" state, but never finishes authentication.

This problem can be caused by multiple issues:

  1. You may not be associated to the access point. Ensure that the laptop is associated to the correct wireless network.
  2. This problem can sometimes occur when a card's drivers aren't behaving properly. We hope to have more information on compatible wireless cards later this year.

My laptop gets to the "Authenticating" state, but never finishes authentication.

This problem can be caused by multiple issues:

  1. Make sure your date is current. If your system date is set to something prior to or after the authentication server certificate's valid date, your client will reject the certificate. This may happen if your laptop's battery has been completely drained, or if you have purposefully set the date on your laptop forward or backward.
  2. This problem can sometimes occur when a card's drivers aren't behaving properly. We hope to have more information on compatible wireless cards later this year.
  3. This problem can sometimes occur when a wireless access point is misconfigured. If you believe this to be the problem, please contact the Campus Help Desk at 581-4000. Please include detailed information about your laptop, and the area that you are having connection problems in.

My laptop ends up in the "Unauthenticated" state.

This problem usually indicates a configuration problem. Use the following list to troubleshoot the issue:

  1. Verify that your username and password are entered correctly.
  2. Verify that you are using the correct authentication type, as mentioned in the instructions.
  3. Make sure that you have the Server Certificate information set up correctly. Check the instructions for details.

My laptop ends up in the "Authenticated" state, but I still can not access the network.

This problem can be caused by multiple issues:

  1. This problem can occur if you have authenticated, but not yet obtained a DHCP lease. You should check your IP settings to verifiy that you have a library wireless address. (Library wireless addresses are in the format 155.97.6.x).
  2. This problem can occur if you are on a fringe wireless area, or have bad signal quality, which will cause you to lose connectivity to the access point, or drop packets, including authentication information. If you think this is a problem you should try moving to an area that may have a better signal quality.
    PLEASE NOTE: "signal strength" is not the same as "signal quality". You may have 100% strength, but horrible quality due to bookcases or human bodies being in between you and the access point.
  3. This problem can sometimes occur when a wireless access point is misconfigured. If you believe this to be the problem, please contact the Campus Help Desk at 581-4000. Please include detailed information about your laptop, and the area you are having connection problems in.
  4. This problem can be caused by drivers incorrectly encrypting authentication frames. This is especially problematic in Linux.

For More

For More Info

uconnect No-Client Configuration

Main Wireless page

Frequently Asked Questions

For more help with campus wireless access, contact the Campus Help Desk at 581-4000 option 1.