|Wireless Access (OSX)|
|Wireless Access (Linux)|
Configuring Microsoft Windows
Windows Vista Must use PEAP to connect to the Network. See Vista_Wireless_Config
Instructions on setting up wireless using Windows XP can be found here: XP Wireless Config
The following Cisco Compatible wireless cards have been tested and are compatible on University of Akron's wireless network:
- Apple Airport and Airport Extreme cards in OS X (These detect as Atheros cards when booted into Windows via Boot Camp.)
- Atheros AR500x-series cards
- Broadcom AirForce One and Sentry5-series cards
- Cisco Systems Aironet-series cards
- Dell Axim x50 and x51-series PocketPCs (using bundled Odyssey Access Client)
- Dell TrueMobile 1300 & 1400-series cards
- Intel PRO/set 2100, 2915, 3495-series cards
- Intel Centrino Mobile Technology
- RaLink RT2400, RT2500, and RT2600 cards
First: Determine Wireless Card/Chipset
In determining the wireless card/chipset you can do several things. The most efficient way is to:
- Hold WindowsKey+PauseBreak (System properties)
- This can also be accessed via right clicking on My Computer and selecting Properties
- Go to Hardware, click Device Manager.
- Click the '+' sign next to Network adapters.
This will allow you to easily determine which wireless card/chipset is installed.
However, many supported wireless cards are often labelled something generic, i.e. "802.11b/g WLAN." To determine if your card is compatible, please call x6888 or bring your computer to Bierce 69.
Second: Obtain Wireless Driver/Utility
The wireless drivers and utilities are usually bundled together as one package. These are available from the manufacturer's website.
Third: Configure the Utility
- For a Cisco walk through click here
- For a Intel walk through click here
- For a Atheros walk through click here
- For a Broadcom walk through click here
The University of Akron uses the Cisco proprietary method of authentication known as LEAP (Lightweight Extensible Authentication Protocol). By default, Windows does not support LEAP, this is why it is necessary for the manufacturer to provide support for it in the utility. Make certain that the option to let the manufacturer's utility manage the wireless connection is checked. Select either "802.11x" or "Cisco Compatible" and under authentication select "LEAP". Enter in the user's UAnet ID as the username, leave the Domain field blank. The password should be typed in BY THE USER for security purposes and then click OK/Apply. The utility should take care of the rest and after the authentication process is done, an IP should be automatically assigned to that computer.
We now have updated the Broadcom, Atheros, Intel, and Dell drivers. The entire set of "old" files is in a folder labeled "old" should compatibility issues arise. The Broadcom driver that's up now should be compatible with the Linksys WPC54G rev.3 cards that the Computer Solutions store is selling. We haven't tried any other Broadcom-based cards.
Also, if a machine comes with an existing copy of the Dell Wireless or Broadcom package, the Linksys card may work with it without installing new drivers or the new client. If the machine requires the new install, remove the existing copies of the drivers and clients and run the Autoinstaller as usual. It should detect as a Broadcom card and proceed normally.
If a user comes in with the Multiband Cisco Aironet (B/G or A/B/G) card, the utility will incorrectly identify it as an Atheros-based card. Do NOT install the drivers, they will not work.
If you have a machine that should work with existing drivers, but for one reason or another doesn't work. Run the debug.bat script included with the utility and that will create a complete listing of any and all hardware devices in the user's machine and save it to a text file on the currently logged on user's desktop. This file may come in handy when identifying compatibility issues.
Support for 64-bit OSes is unknown. The Microsoft command that the utility is based on (devcon) isn't designed to run in 64-bit environment, so it will more than likely toss out a nasty error. On the other hand, the drivers themselves should have 64-bit support.
Legacy Windows 9x/Me/2000 Support
All drivers except the Broadcom driver currently in circulation include Windows 9x/Me/2000 Support. The Broadcom driver currently in circulation add support for new cards, but drop support for Windows versions older than XP. Drivers for this are currently experimental, and the installation procedure is a bit unrefined. The driver is not on the file server since a misconfiguration sometimes results in an unbootable machine.