Here's my problem... I just purchased, setup and installed my new Airport Express 802.11n. It's up and running BUT..... I can no longer read the configuration file via the Airport Utility (v.5.3.1). I'll select my AE (v. 7.3.1), click on Manual Setup and after waiting 5+ minutes, I get "An error occurred while reading the configuration. blah blah blah error code -6722.
My MacBook Pro is running 10.5.2 with all the updates. I can access my Time Capsule (v. 7.3.1) and my older AE 802.11g (v. 6.3) using the Airport Utility. I just can no longer access my AE 802.11n. I also tried accessing it from my older G4 iMac 400Mhz running 10.4.11 with all the updates. I get the same error. Any suggestions? Thanks.
I also get this same message. After resetting the base station through both a soft and then a hard reset, I always now get the "An error occurred reading the configuration".
I am using Airport Utility 5.3.1 and have a Base Station (Extreme N Fast Eth). I originally was trying to upgrade to the 7.3.1 update (because of security precaution reasons) and this was failing each time. So I tried a soft-reset.... and then the hard reset....
and now it is back to the factory default (It is showing 7.2.1 ) and I cannot even get into it to reconfigure it! I am connected to the internet via the ethernet cable as the wifi no longer works
Also I have seen on another Mac discussion group to try and set up another Admin account and try it from there. This didn't work either.
Yet another thread said to make sure IPv6 was set to automatic - which it also is.
I just got an Airport Express, running I think the latest firmware, off of ebay, and it's doing the same thing, even after a hard reset. I tried configuring it from two different machines. I'll let you know if I figure anything out.
Hi - I had the same issue, Apple sent me a new one. That one didn't work either. Then I clued in and shut OFF Jumbo Frames on my Ethernet card. Now all works again. Unplugging the cable and/or turning Ethernet off in the preferences wasn't enough, I had to go back in and chance ethernet to standard MTU of 1500
Hope this helps
My Ethernet settings are on the default 'Automatic' option (and always have been) so the MTU has always been set to Standard (1500). So this is not it.... The only thing that (I can think of that) has changed is the software that manages it.... Airport Utility (Apologies Apple if not true). I tried to go back and reinstall 5.2 via time machine and no luck either. I guess I am hoping for a software update fix or maybe I have to return the unit.... urgh!
Do you have anything connected to the USB port? If so, try disconnecting it and
then resetting.
I had a similar problem with a TC recently: Couldn't read config in Airport utility with 6722 and 6753 errors reported. Disconnected the USB disk and the fault vanished. Reconnected the disk and the fault returned imediately. (The disk looks like toast, btw - but I haven't had time to check it thoroughly yet)
Nope - nothing is plugged into the USB port. In fact when I do the reset none of the ethernet plugs are in either. Once it is reset I re-plug in the ethernet cable from the laptop to the unit without it further being connected to the internet - connected or not to the internet after the reset is still comes up with the error.
OK! I also tried to see if I could get into my airport express as I have one of these for when I have to travel and it also came back with the error ....
BUT get a load of this! I also have a PC running XP in the house and was ABLE to get into it via the APple Airport Utility software loaded onto it and reconfigure everything!!
So what is preventing my MacBook Pro from getting in? Any suggestions anyone. I have tried to reload the software that came with the unit and no luck, tried to download the latest version off the Apple website, no luck, threw out the "com.apple.airport.preferences.plist" preferences, no luck. Any suggestions, I am no techi.....
I had a very similar problem when trying to configure my new Airport Express via Airport Utility - it would error out, either on reading or writing the configuration with a cryptic error number - I saw both 6722 and 6753 at various times. I was trying to add the Express to an existing wireless network.
After some fumbling around, I eventually tried using the manual configuration option in Airport Utility. This actually worked, in that the configuration was successfully written and the light on the Airport Express turned green. Airport Utility still reported an error at the end of all this though, but the Airport Express does work now.
BUT get this! Out of shear frustration I then tried to use a PC running XP in the house and not only was able to get back in a reconfigure it, I was also able to download the 7.3.1 update through XP!
Even after this update to 7.3.1 and the OS 10.5.3 update I tried to go into the Airport Extreme unit and still get the error!!
I hate using XP (even worse the OS & Software update was in Polish which I can't read/understand) so if anyone can enlighten me how to get back control from within my MacBook Pro, I would really, really appreciate it.
An Update..... Well, after doing nothing and letting it go for a while..... all of a sudden, I can now read the configuration file. Again, I didn't do anything out of pure frustration. Go figure......
I would like to add my data to this discussion. I believe it is the same issue.
Configuration:
Base Station Extreme (AE) 7.3.1 WDS Main DHCP on Cox sharing public IP; wireless to a MacBookPro
Airport Express (AXg) 6.3 WDS network slave to the base
AX 7.3.1 (AXn) WDS network slave to the base; drop to a printer through the USB
Time Capsule (TCg) 7.3.1 WDS network slave to the base; hard ethernet tap to a Mac Cube
AX 7.3.1 (AXn) 7.3.1 WDS network slave to the TC; drops an audio to the stereo
all works except the AP Utility 5.3.1 cannot Manual Setup the new AXs - the AXg works fine. both AXns don't. Manual setup works on TC and AE. Have done hard resets on both AXgs and reset up with no luck. Have an extra AXg I tested - same problem. AXs appear to be working as relays on the WDS fine so it is just the config that doesn't work once they are part of the WDS network.