This discussion is archived
5021 Views 21 Replies Latest reply: May 6, 2008 5:01 PM by Alain Duchesneau
Currently Being ModeratedApr 21, 2008 9:47 PM (in response to Robert Madry)The most recent version of AX has a different way to factory reset the device than the manual states
The correct instructions are to leave the unit plugged in, press and hold the reset button until the light flashes. Then wait... a long time until it comes back online as a factory reset device.
(The old model was similar except you would need to hold the reset button AS you plugged it in. On the latest model, that does not work).
I had to call AppleCare to find that out. MBP, G4, Nano TV, TC, AP Express , Mac OS X (10.5.2)
Currently Being ModeratedApr 21, 2008 10:11 PM (in response to usernameistaken)I spent 3 hours with Apple tech support on this issue. I got bumped up 2 levels because I had a configuration where my MacBook and iMac are running Leopard and Tiger respectively, and my AirPort is Express is running on the G frequency to downsample for the iMac.
Found one glitch. The older iMac could not connect with the router after being configured by Leopard's newer utility. We tracked it down to a WEP problem. I noticed that the iMac issued a warning about WPA being incompatible. SO WEP it as. But the new Leopard utility allowed for 13+ passwords; the older AirPOrt utility could only accept 13 ASCII words. That was glitch #1.
#2 was traced back to the Leopard utility setting the specs for the AirPort Express. The Tiger iMac could set and reset with no problems, but the MacBook would lose the signal, never the G5 iMac.
After hours of doing Apple's troubleshooting for them, I went for a beer. It was very interesting. I had documents everything, every step. When they could replicate my problems, they bumped me.MacBook 2.2 Johnny Cash Black, Mac OS X (10.5.2)
Currently Being ModeratedApr 24, 2008 6:36 AM (in response to swixo)So I got this AX and I love it but I have the same problem everyone else is having, "Cannot read config". Strange this is, since I moved the unit to another location I am unable the read config. I'm think this maybe a RF interference problem because my last location I didn't have a modem transformer plugged into the same outlet as the AX. This time I have the AX plugged in the same outlet as the AX and thus cannot read config...
My last wireless router (Motorola) was very prone to RF interference, to the point I count not connect to the internet...Macbook, Mac OS X (10.4.11), After owning 5 PC's. I went Mac and will never go back.
Currently Being ModeratedApr 24, 2008 6:52 AM (in response to VE3XTR)I doubt it, I've had my express plugged into completely separate outlets from my modem, right next to my extreme router, on the other side of the house, less than a room away, etc and it still kicks up the error.MacBook Pro, Mac OS X (10.5.2)
Currently Being ModeratedMay 4, 2008 7:53 AM (in response to swixo)I was having this problem too. Just got a new airport extreme and wanted to put my old airport expresses on the network (itunes, boost signal, share printers ...). I reset these, factory reset these and kept getting -6722 error. I read some of the posts and thought "perhaps this is a Leopard thing" - there are a lot of Leopard things.
So, I reset the AX's one more time and used airport utility in Tiger to reconfigure them. I could then put on my network. Once I had them up and running on Tiger, airport utility on leopard could see them and could also update the firmware. I got one AX on WDS, but the other (same configuration) would start up give the green light and go to flashing amber. I could do the easy set up and have it join my network, it will be used to iTunes sharing. They are running - sort of. All in all a pretty painful experience.
Perhaps this is a new -> old issue. I should point out that before the Airport extreme upgrade (old basestation, old expresses) everything was happy, but I did not have to use the new airport utility with the old equipment.G5 (dual 2 GHz), Intel (2.16, 2.2) Macbook pro, G5 iMac (tiger), Mac OS X (10.5.2)
Currently Being ModeratedMay 6, 2008 3:16 PM (in response to swixo)OK, same problem here, got it today. Don't know if it's in the firmware upgrade I did first thing when I started Airport Utility or a problem with the Airport Utility itself. The only good thing here is that I'm not alone with this and hopefully we can soon see a fix from Apple.MacBook Pro, Mac OS X (10.4.11)
Currently Being ModeratedMay 6, 2008 5:01 PM (in response to swixo)Alomst same problem here.
Bought my APEn friday, it worked fine the first day. It was configured to access my current wifi network (D-Link 624 - WEP 40bit) and it was working fine.
The next day, there was an update for my APEn, I installed it and just after that, nothing, the thing is just unreachable, with blinking amber light.
I taught it was my D-Link the problem (http://forums.macrumors.com/archive/index.php/t-112000.html) but after reading this discussion, it looks like the problem come from my APEn.
The thing work great with default factory settings. That's fine with me, my iMac is wired to the D-Link. I can't say the same for our other machines in the house. I have to fix this. I just sold my older Airport Express that was working absolutely fine...
Message was edited by: Alain DuchesneauiMac Intel 1.83 GHz Core Duo, Mac OS X (10.5.2), Airport Express 802.11n