"This version of AirPort Utility doesn't support this base station"

[Bruno09]

OK.

Stay connected to your current wifi network, have AU 5.6.1 open, connect the old Airport device to your router via Ethernet, and reset it.

It then will show up in AU 5.6.1 and you will be able to set it up.

 

[mixelK]

via Ethernet

Great, was missing something obvious (blush).

Just tried it and it works, thanks !

Sadly I got a new problem now, as I tried to extend my existing network, with my old Airport, now it blocks after configuration, when restarting the Airport. This issue is of course not related to the current conversation treat. Any help would be welcome, I'm clearly out of my comfort zone with these technical issues.

 

[Bruno09]

Glad you got it sorted out.
[doublepost=1476001718][/doublepost]Remember that an Airport device can "extend a wireless network" created by another Apple device only.

It can not extend (wirelessly) the network of a non Apple wifi-router or access point.

If you wish to increase your wifi coverage, the best solution is to connect your Airport device to your router via Ethernet and use the "create a wireless network" function.
You can set its network with the same name (SSID), security, and password as your current network (= "roaming network").
https://support.apple.com/en-us/HT204616
(the "primary base station" can be a non Apple router)

If this does not help you, please explain what is your current setup and what you wish to do.

 

[Altemose]

Sadly I got a new problem now, as I tried to extend my existing network, with my old Airport, now it blocks after configuration, when restarting the Airport. This issue is of course not related to the current conversation treat. Any help would be welcome, I'm clearly out of my comfort zone with these technical issues.

In order for it to work, you must have an AirPort as the main router as referenced by @Bruno09, but that main AirPort must also be in DHCP & NAT mode.

 

[Balso]

In order for it to work, you must have an AirPort as the main router as referenced by @Bruno09, but that main AirPort must also be in DHCP & NAT mode.

Well but you can "join an existing network"... at least I could do it! I am facing the same issue: I have run the setup via ethernet but the airport cannot find the wireless networks... inserting manually, even if it is correct won't make it work any idea to avoid plugging another ethernet cable?

 

[Altemose]

Well but you can "join an existing network"... at least I could do it! I am facing the same issue: I have run the setup via ethernet but the airport cannot find the wireless networks... inserting manually, even if it is correct won't make it work any idea to avoid plugging another ethernet cable?

If the main router is an AirPort, it will work to extend wirelessly. Otherwise, it must connect using Ethernet.

 

[Balso]

Sure, that's what I did, nevertheless... using my old(!) Powerbook G4 allows me to extend a wireless network not coming from an Apple Device.. sad but true my old PBG4 is now 1000km from me... Thanks anyways, I have to say that the ethernet connection makes it more reliable and stable on the long run by the way!

If the main router is an AirPort, it will work to extend wirelessly. Otherwise, it must connect using Ethernet.

 

[jinnko]

I recently wanted to make use of an old Airport Express, but none of the macOS packages was able to connect.

Ironically I was able to get the old "Airport Utility 5.6.1 for Windows" package installed via wineBottler on macOS Sierra and use that to configure my old Airport Express. Download the AU package directly from the Apple site, and if you have wineBottler installed you just double click the *.exe file and the installation options pop up.

The only option I had to change when installing the package in wineBottler was to set it to Windows 7 rather than XP. There was a bit of a delay and hang during installation, but after a few minutes it continued and everything works perfectly!

 

[gadgetronica]

Hi,

to use your A1088, you need Airport Utility 5.6.1.

See here, this works perfectly (including Yosemite): http://coreyjmahler.com/2013/10/24/airport-utility-5-6-1-on-os-x-10-9-mavericks/

When you launch 5.6.1, it will offer to update : don't !

You can have the 2 versions on the same computer, no problem, they can even run simultaneously.

Thank you Bruno09! This old post helped us activate our Airport in 2018!

 

[QuarterSwede]

Resurrecting this dead thread in case someone wants to get this working in Catalina. Check out this article by John Ganotis. Just requires completely disabling SIP while you launch the app. Note: I did not have to use ethernet to see my 1st gen Airport Express. However, it was already on the network and I wasn't setting it up from factory reset. I just wanted to change the default name.

Thank God Apple wrote the Airport Utility 5.6.1 in 64-bit!

 

[lukehawkins]

I've tried all of the above. When I go to open the app and after verifying I want to open it in Security Preferences I get this error message:

sh: line 2: cd: /private/var/folders/dw/m3gr08d97cn2lb5f1wp6ttmr0000gn/T/AppTranslocation/53397EB8-175A-4315-9CB2-55FCCB92B2B0/dAirPort Utility 5.6.1.app/Contents/MacOS: No such file or directory


sh: line 3: ./AirPort Utility: No such file or directory
sh: line 2: cd: /private/var/folders/dw/m3gr08d97cn2lb5f1wp6ttmr0000gn/T/AppTranslocation/53397EB8-175A-4315-9CB2-55FCCB92B2B0/dAirPort Utility 5.6.1.app/Contents/MacOS: No such file or directory


sh: line 3: ./AirPort Utility: No such file or directory (127)

Can anybody help me understand how to get passed this bit? I have tried using Airport Utility 5.6.1 on Windows to setup the device but it doesn't seem to find it on the network.

TIA

Luke