X

AirPort Extreme Update 2007-002 (#2): Problems connecting to third-party wireless routers, fixes

AirPort Extreme Update 2007-002 (#2): Problems connecting to third-party wireless routers, fixes

CNET staff
4 min read

Despite documentation indicating that the revision is intended to enhance compatibility with some third-party wireless routers, some users have reported loss of connection to their devices after applying the AirPort Extreme Update 2007-002 for Intel-based Macs.

MacFixIt reader Rick Pearce writes:

"This update ran this morning and after reboot, it was not able to connect to my dlink wireless router.  I get an error message that says something to the extent of 'Problems connecting to dlink'.  I've tried cycling the power on the dlink and cycling the airport connection.  I was using a Personal WPA ? configuration.  It prompted me for my passphrase.  Won't connect even after entering it."

Another reader adds:

"After the update my mac mini CD wont connect to my WPA PSK protected router. Restart, repair permissions, retype the PSK PW didnt help."

If you are having problems connecting to a third-party router after applying this update, try the following workarounds:

Potential fixes

Check for/quit third-party wireless applications (monitors/sniffers) Some third-party applications that manipulate or otherwise interact with the wireless connection may cause problems -- particularly an issue where speed vacillates quickly between normal and dismal throughput.

Among the implicated applications are older versions of coconutWiFi.coconutWiFi is an application displays you a small aqua-bubble at the top of your screen which indicates whether or not. you're in range of a wireless network. Current versions of the application do not exhibit this bug.

Change security protocol In some cases, WEP key-based access can provide better speeds when compared to the more secure WPA standard.

This setting can be changed on AirPort base stations by using the AirPort Admin Utility (located in Applications/Utilities) to configure the target base station.

Delete all "Preferred Network" listings then re-establish One surprisingly effective AirPort Base station-specific fix for an inability to connect to wireless networks involves deleting all stored preferred networks, then re-establishing any used listings. Here's the process:

  1. Open System Preferences and select the "Network" pane
  2. Select "AirPort" and click "Configure"
  3. In the "By default, join:" pull-down menu, select "Preferred networks"
  4. Delete the network(s) you regularly use from the list
  5. Launch the "Keychain Access" application located in Applications/Utilities.
  6. Click on the "Kind" filter at the top, and look for "AirPort network password" entries. Delete them.
  7. Restart, or log out then back in.
  8. Repeat steps 1-3, this time re-adding your regularly used AirPort networks to the list using the " " button.
  9. Restart or log out then back in.
"Keep Looking for recent networks" In some cases, selecting "Keep looking for recent networks" in the Network pane of System Preferences can resolve an inability to connect to local networks. Turn router off, then on In some cases, turning a wireless router off, then back on -- usually by unplugging then re-connecting to power -- can return a normal connection

If your third-party router has a reset button, try using it for a similar effect.

Toggle firmware Toggling of firmware versions (the edition of controller software stored on your wireless router) is perhaps the most successful fix for dropouts from virtually all wireless router models. By "toggling firmware," we mean trying different versions available from your manufacturer until one provides a more stable connection. In other words, a user's first attempt should always be use of the latest firmware version, but sometimes older versions provide better stability.

Unfortunately, the trick is in locating appropriate firmware updates. You can usually find the different firmware editions on a router manufacturer's Web site, but some vendors fail to offer the updates or old versions in Mac-based installer packages.

[Failing the above fixes, you may want to try one of the workarounds in our more expansive wireless troubleshooting tutorial, or resort to unisntalling key components of the update as described below]

Uninstalling (getting the update off your Mac) If you are experiencing dire issues after applying AirPort Extreme Update 2007-002 that cannot be resolved by workaround posted elsewhere in this report, you may need to uninstall the update.

The first thing to try is reversion to an earlier edition of the 802.11 kernel extension. [WARNING: This workaround risky because you should not generally mix and match kernel extensions after updates, you will lose some improvements (including security refinements) brought about by AirPort Extreme Updater 2007-001, and new conflicts can ensue. Still, in a bind, it can restore wireless connectivity where other workarounds fail.]

The kernel extension reversion process is as follows:

  1. Download the most recent version of Mac OS X for Intel (10.4.8) but do not install it.
  2. Download and install the shareware application Pacifist
  3. Drag the Mac OS X 10.4.8 installer package onto the Pacifist application icon.
  4. Click the triangle next to "System" to expand it
  5. Click the triangle next to "Library" to expand it
  6. Click the triangle next to "Extensions" to expand it
  7. Scroll down and find the file IO80211Family.kext. Drag it to your Desktop or another location (you will have to enter your administrator password)
  8. On your Mac OS X startup drive, navigate to /System/Library/Extensions and locate a similarly named file (IO80211Family.kext). Move it to another location for safe keeping.
  9. Now drag the file from step 7 (the one that you retrieved from the Mac OS X 10.4.8 install package) into the /System/Library/Extensions, in effect replacing the newer file (installed by the AirPort updater) with and older copy -- you will have to enter an administrator password.
  10. Restart your Mac

A more tedious workaround is to completely remove all traces of the update via an Archive and Install. This can be accomplished via the following process, adapted from our tutorial on reverting to a previous iteration of Mac OS X. Note, however, that reverting your system will remove any refinements brought by the update and leave your system open to potential vulnerabilities.

Previous coverage:

Resources

  • coconutWiFi
  • wireless troubleshooting t...
  • Mac OS X for Intel (10.4.8...
  • Pacifist
  • reverting
  • AirPort Extreme Update 200...
  • More from Late-Breakers