This discussion is archived
13759 Views 61 Replies Latest reply: Jun 8, 2009 3:03 AM by fabio909
Currently Being ModeratedMar 6, 2009 9:03 AM (in response to Miv Fournier1)Whacked it in mine - no troubles at all - in fact it fixed an inability to use DHCP ( I had to hard code the IP address previously )17" Powerbook G4, MacBook Pro 15", G4 500MHz, Mac OS X (10.4.11), Extensive AirPort network (4 x express, 1 x extreme), AirDisk SAN & printer
Currently Being ModeratedMar 6, 2009 9:10 AM (in response to Shawn Grinter 2)That's good to hear. I am just running disk utility to see if it sorts anything.
The error I am getting is when I attempt to go into the set up:
AN ERROR OCCORRED WHILE READING THE CONFIGURATION
Make sure your Apple wireless device is plugged in and in range of your computer or connected via Ethernet and try again. (-5)Mac Pro, MacBookPro, imac, iphone, Mac OS X (10.5.4)
Currently Being ModeratedMar 6, 2009 9:18 AM (in response to Miv Fournier1)Yep firmware upgrade bricked my AEBS.
After the best part of an hour wasted now back up.
Hard reset (I needed to use the unplug power - hold reset button - plug in method)
DO NOT FOLLOW ASSIST ME
downgrade back to 7.3.2 (click "version" and chose from drop down list.
Configure as required follow Assist Me if you like
Good LuckiMac Intel 2.8 4GB, Mac OS X (10.5.6)
Currently Being ModeratedMar 6, 2009 10:10 AM (in response to Miv Fournier1)Bonjour,
May be you had the same trouble than me.
In my case, it was the automatically selected canal that was wrong: in 5GHz, it was the channel 149. It was previously (with firmware 7.3.2) channel 36.
To fix the problem I had to connect thru Ethernet to get back access, and than, I tried to change the channel, but the only choice, was "Automatic". So, I had to fall back to firmware 7.3.2
Now it works.
New feature not available for previous model?
I don't know.
ChristianMacBook pro (3,1), Mac OS X (10.5.6)
Currently Being ModeratedMar 6, 2009 5:25 PM (in response to BenJonesUK)Exact same thing happened to me. Thanks for the solution. I was also able to get it working again with 7.4.1 after the reset (w switch) and re config using manual.iMac 24" Core2Duo3.06GHz, MBA 128SSD, MB, AppleTV, iPTouch, Mac OS X (10.5.6)
Currently Being ModeratedMar 6, 2009 6:37 PM (in response to justin_case)I had to downgrade the firmware with a laptop that has Airport Utility and access to the router.
Not the first time that my router had been bricked. Probably won't be the last.Dual 2GHz G-5, Mac OS X (10.4.11)
Currently Being ModeratedMar 8, 2009 10:25 AM (in response to Miv Fournier1)I am using a Ralink RT2870-based USB client adapter with an AEBS. This update killed the 5 GHz connection with this adapter, doesn't even show up in the list of available access points. It worked fine as a wired router and as a wireless on the 2.4 GHz band. But I had to revert to firmware version 7.3.2 to get my 5 GHz wireless connection back.Dual 1.8 GHz G5, Mac OS X (10.5.6), 2 Gb RAM, Ralink RT2870
Currently Being ModeratedMar 11, 2009 5:05 AM (in response to Miv Fournier1)I just installed the firmware update 7.4.1 via wireless laptop instead of the ethernet connected desktop. I expected some problems to crop up but NO, everything works fine. My method is to install only one update at a time, after running integrity checks before & after installation.
Just my 2 cents.Dome iMac, MacBook, MacBook Pro, Mac OS X (10.5.4), 3 Airport Expresses & Time Capsule
Currently Being ModeratedMar 12, 2009 3:10 PM (in response to Miv Fournier1)I had similar issues. My Airport Extreme is configured a WDS main base station. After some investigation (and downgrading and re-upgrading), I discovered that the "Allow wireless clients" option under WDS had been turned off. I re-checked that option, updated the settings and was back in business.MacBook Pro (rev A), Mac OS X (10.5.6)