Currently Being ModeratedFeb 13, 2012 8:30 PM (in response to Sherman Gregory1)
I am 100% certain your version of AirPort Utility is correct, and is the correct version to use with OS X 10.6.8. I believe that KB article is incomplete.
Forget you ever heard about AirPort Admin Utility, in fact if you still have it you can safely get rid of it. AU 5.5.3 will administer your older AEBS just fine.
The problem you are encountering probably can be fixed by connecting it to your computer directly with an Ethernet cable. If that doesn't work you may need to perform a "hard reset" which will wipe out all its settings.
Whatever is going on, it is not a problem with Snow Leopard or your version of AU.
Oh and one more thing - AU 5.5.3 ought to have several firmware versions available to upload to the AEBS. I recommend using version 5.5.1 and no other. The two subsequent versions 5.6 and 5.7 have problems with the AEBS that would cause it to become unresponsive, the only cure being a power cycle. With 5.7 it could run for as long as a several days, or it might need to be reset twice a day. 5.6 was worse. I have no idea why.
Currently Being ModeratedFeb 14, 2012 9:35 AM (in response to John Galt)
Thank you for the quick reply, and I hope that you are right.
Here is some additional information.
I did try connecting through ethernet, and got the same result. There was an ethernet switch between the Mac and the AEBS, so I guess it was not entirely direct, but close. Do you think that would make any difference?
I found a Tiger machine with AirPort Admin Utility 4.2 on it. That seemed to to work fine. So the AEBS can send its configuration and be administered, but I consider this a temporary solution. This does tell me that the configuration file is not fundamentally broken.
I thought that I might try the AirPort Admin Utility 4.2.5 that is linked to from the above mentioned article, but the Read Me for that installer says just to use it for the Graphite Airport and Dual Ethernet Airport, and not for any Airport Extreme.
I thought about the hard reset but am somewhat hesitant because it is working and I do not want to get into an unrecoverable state. My configuration is non trivial with manual IP address and a bunch of port mapping, so it will take a little time to get it all back even if I can administer it with Airport Utility 5.5.3. I did save the configuration to a file on the Tiger machine. Do you think that Airport Utility 5.5.3 will understand that file?
Currently Being ModeratedFeb 14, 2012 9:47 AM (in response to John Galt)
Oh, and about the firmware versions. My AEBS has 5.7 and has been running for years without requiring a power cycle. I remember going through some firmware years ago that did have the problems that you describe (probably 5.6), but 5.7 has been stable for me. Of course that could be related to the present problem. Maybe 5.5.1 would talk to Admin Utility where 5.7 will not. Is it possible to back grade the firmware to 5.5.1? Is that downloadable from somewhere?
Currently Being ModeratedFeb 14, 2012 9:57 AM (in response to Sherman Gregory1)
It is possible the switch might be preventing communication, but I think it's more likely an internal AEBS parameter that has been corrupted. The only way to recover from that is a "hard reset". This has happened to me on rare occasions and there is nothing else that can fix it.
Before giving up on the switch, try cycling its power or try another port. Stranger things have happened.
The last version of AirPort Utility I used for OS X Tiger was 5.4.2. Here is the link: http://support.apple.com/kb/DL839
AU 5.5.3 requires Leopard or later, but I assure you it will also communicate with your AEBS.
I would not bother with any version of Airport Admin Utility. It might work but AirPort Utility 5.4.2 and later will do everything the old AAU did, and more. If you had an older Graphite or Snow, you might need AAU but that's a moot point.
Your configuration file ought to work. In the end you have to be prepared to reconfigure the AEBS. It's just something you get used to after a while...
Currently Being ModeratedFeb 14, 2012 10:03 AM (in response to Sherman Gregory1)
No, the ability to communicate with the AEBS with AirPort Utility is independent of the firmware revisions you specified. If 5.7 is working then let sleeping dogs lie. I had problems with mine but I am nearly certain it was related to a conflict with some fairly new, non-Apple gear.
Can't be overstated - forget about AirPort Admin Utility.
I believe AirPort Utility 5.4.2 and 5.5.3 both have the ability to upload several firmware choices. It just so happened I needed 5.5.1 to maintain reliable service with the new equipment.
Message was edited by: John Galt reason: bold text
Currently Being ModeratedFeb 14, 2012 9:29 PM (in response to John Galt)
Thank you John. You are completely correct. I did the hard reset and now Airport Utility 5.5.3 under Snow Leopard talks to my AEBS. I configured everything manually instead of using the saved file just because I figured a clean start might be better. All appears to be working now.