Airport Extreme (802.11n) - Connection drops (no auto-reset)

Here it is, February of 2008, and it appears the problems still persist.

In my case, things may be a bit different. My problem seems to only be related to the AEBS and a MyBook external USB drive connected to it. I lose the connection when trying to copy files onto it. I have an Intel iMac that was purchased in April of 2007. I'm running Tiger.

The funny part is that the AirDisk worked fine just before Christmas.

Then I decided to remove the USB drive from the AEBS, and use it on a PC until I could buy a larger internal drive for the PC. (At every step of the way, I re-formatted the drive to the proper file structure for the computer it was connected to.)

I changed my mind yesterday, and decided to install the MyBook drive on the AEBS again. Then I had the dropoff problems.

On the network, I have the iMac, a PC Notebook connected wirelessly, and a PC Desktop ("wired").

It seems quite clear to me that the problem is related to firmware... and the problem has now existed for several months.

I tried reverting to an older version of the firmware, but the problem exists.

Sorry Dan, I'm probably being a bit simple here.

I'm on a Mac and I managed to pull-up the firmware menu (using the option key as you described). I selected the firmware in question (several are greyed out), however, once it actually downloads the firmware (the AEBS has a habit of disappearing half-way through the download, so haven't managed to do it yet) how do I apply the firmware to the AEBS? i.e. do I need to click on 'Update' in the normal AEBS dialogue box or should the firmware simply be applied once "successfully" downloaded?

Thanks for your patience!

Stu

If you've got a new AEBS, you can't downgrade the firmware beyond a certain level, I think, as the older versions aren't compatible with the newer hardware. At least, that's what I've gleaned from reading these fora and others. I can't roll back my firmware either. I'm waiting patiently for Leopard 10.5.2 and hopefully, a new firmware for the AEBS at the same time. Apple are (hopefully) about to release these.

Depending on what model you have will make the diffrence in firmware.
For example:

AEBS N Fastethernet 10/100 works with firmware: 7.0(?) 7.1, 7.1.1 and 7.2.1(Fast ethernet version)

AEBS N Gigabit 10/100/1000 works with firmware: 7.2 and 7.2.1(Gigabit version)

Stuart,

If your having issues reloading the firmware, try hard resetting the base station first. At least that way it a completely clean start. I did a hard reset and then once finished unplugged it for about a minute and plugged it back in. I would also suggest only updating the firmware via the ethernet port and not over the wireless.

-Dan

Message was edited by: MoparDan

Message was edited by: MoparDan

Thanks Dan.

Actually the problem I was having was how I actually apply the firmware version once it's been downloaded.

So for anyone else who struggled as I have, the final firmware downgrade step (after downloading the previous version) is as follows: Select the 'Base Station' menu and choose Upload Firmware...
Then simply Select the firmware version you want to downgrade to and click OK.

Thats right, I had forgotten that it had to be done twice.

How did the rest of those settings work out for you? If needed I can make some screenshots of my setup to clarify how I did my setup.

Its still been working great, even with >4Gig downloads.(no torrents, Unix related)

Dan

Hey I did alot of research into this and found out from another thread that there is a setting on the airport that needs to be changed.
I forget how to tell you exactly how to get there but if you open up airport utility. and double click on your airport icon it will let you change settings.
Find the one that is set to portal or nodal and change it to the other one. (portal or nodal i forget which one, but I changed mine and it hasn't dropped the connection since.)

Hey when I got home I figured out exactly what the settings are you need to go into airport utility double click on the airport icon then click on the advanced icon at the top select the IPv6 tab and then switch tunnel to Node. (not portal to nodal like what I said before). Anyway that is what I did and it worked for me.

I solved the problem by returning the AEBS to the Apple store. They replaced it with a new one and it has not dropped for several weeks.

I look at things very simply:

Apple sold us a device that was supposed to work. Apple didn't tell us we'd have to waste countless hours trying all sorts of arcane tricks to make it work.

It worked before, and now it's broke. Apple needs to get off their duffs and fix it. It's already been months.

In the meantime, I've ended my own struggle. I disconnected the USB drive, and am now using it on my PC....

Hey Dan,

Since the firmware downgrade (7.2.1 to 7.1.1) everything appears to be pretty stable. No packet loss and the AEBS has been up now for a day now without dropping the connection of restarting (or just plain disappearing).

I'll keep you posted, but it seems as though the downgrade seems to have done the trick. Fingers crossed!

Thanks for the help and for following up,

Stu

I'm having the same problem. I have to go and unplug the router almost once a day.
The 2 airport expresses (bridge mode) in the network are rock solid, never had to reboot them, but the Airport Extreme often disappears from communication with the Airport Utility.
I NOT running 10.5, never have. All Macs on the network are running 10.4.11.

I had thought that it might be my satellite modem that was messing it up but it went down for 2 weeks and I still had the same problems.

Apple! with 462 posts, this may be something you should address!

I "upgraded" from a Dlink 514 to the Airport Extreme in the hope of getting a stable connection but am having the same problem as everyone else. I have just tried that ipv6 adjustment but if that does not work, the Airport goes back and I get a cheap modem with the same problems and save $$$$

I had also tried the IP6 "fix" and did not get any better results. The best thing that has worked for me is what I listed above.

-Dan

I don't think anyone here has come up with the right solution so far. If they had, everyone would have fixed it by now.

The right solution is for Apple to fix the firmware update.