My airport extreme base station (802.11n, but pre-TimeCapsule era version) kept working perfectly for more than one year – untill I installed the latest firmware this morning. The thing refused to appear in Airport Utility after update. It is possible to reset it, but once I change any settings and let the Airport Extreme reboot to load them, I always get stuck in the same point – solid amber light, not visible in Utility, nothing helps but yet another hard reset.
It must be caused by the firmware update, since it stopped working right after I installed it. Is there any known way to install previous firmware? And if it is, how can I get the earlier sw in the first place? Looking forward to any advices.
MacBook Pro 2.33 15",
Mac OS X (10.5.6),
Airport Extreme Base Station
Uploading old firmware is actually really easy. All you do is select your base station from the list in Airport Utility, and under "Base Station" choose "Upload Firmware." From there you can select which firmware version to upload (old or new) from a drop down box.
Wow. I had the same problem. I attached to the AEBS via Ethernet and reverted the firmware back to 7.3.2, and the wireless network came back up right after the AEBS rebooted. I didn't even have to do a hard reset. I am thankful it was so easy to fix. Thanks to everyone who posted here!
I have 2x Airport Extreme BSs and 4x Airport Express BSs (bg only). I have two networks in the house, one is "n" only with the Extremes and the other is "bg" only.
Thought readers might like to know that the Extremes updated smoothly. No problem even though one extends the other.
Maybe I was lucky! Maybe my "n" network was not as complex as others here.
Was hit by the can't load the configuration error (-5) after applying 7.4.1. There's no need to downgrade, a hard reset and reconfigure works although aggravating.
For all those getting the Error -5 cant read configuration(i got this on 3 different macs), I was able to get into the manual config from both a Vista PC and a Windows 7 PC.
Seems like this is an issue with the mac airport utility.
Is anyone getting an error -5 with the windows utility?