You can make a difference in the Apple Support Community!

When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

grafiksol Author

Level 1

0 points

Airport Utility V6.3 Update

Software update identified a new Airport Utility version (V6.3) and the update was installed. However, the new version no longer sees my AirPort Extreme (says the device "was" part of my network but is no longer. Airport Utility V6.2 (still on another machine) still sees the existing AirPort Extreme normally, and can edit the configuration with no problems. The Airport Extreme is an 802.11n (4th Generation) device. Any thoughts?

AirPort Extreme 802.11n (4th Gen), Mac OS X (10.7.5)

Posted on Jun 11, 2013 6:41 AM

46 replies

Jun 11, 2013 9:56 PM in response to dfavor

COOL, it wroks fin i 6.2 again.....

THX a lot~~~ dfavor

PeterLZ

Level 1

10 points

Jun 11, 2013 10:38 PM in response to grafiksol

BRILLIANT, dfavor!

Nice, elegant solution.

jhph

Level 1

8 points

Jun 11, 2013 11:57 PM in response to grafiksol

You can download the older Airport Utility 5.6 from Apple and use that. I keep whatever new version as well as 5.6 on my MacPro for situations like this. 5.6 is just so dead simple it's nice to use. Just rename the app and you can choose which to use to modify the settings.

http://support.apple.com/kb/dl1482

To bump the thread with the same problem, Airport Utility 6.3 (630.34) isn't recognizing my Airport Extreme (1st gen) either.

Jun 12, 2013 4:43 PM in response to dfavor

I was also seeing the same problem. Following dfavor's instructions allowed me to reinstall v. 6.2 and I'm back in working order.

However, like others have mentioned I also keep a copy of v. 5.6 installed because it has always seemed more reliable than any of the 6.x versions and it also has more features.

Jun 12, 2013 7:49 PM in response to dfavor

nope didn't work

markwmsn

Level 6

15,635 points

Jun 13, 2013 5:27 AM in response to jeff work

6.3 worked for me when I first installed it, but today it could not find my Extreme (5th gen) or an older Express.

Using "Configure other..." to make a minor change to the name of the Extreme and reboot is caused both the Extreme and the Express to reappear. We'll see how long that lasts.

(MBP-R 2012, 10.8.4)

Jun 13, 2013 9:55 AM in response to grafiksol

Looks like 6.3 is using IPv6 to talk to Time Capsules/Airports. I know I had turned off IPv6 long ago since I didn't need it. Also looks like Apple has removed 'Off' as a valid choice for that setting.

To turn IPv6 back on:

Open System Preferences->Network

Click Advanced

Change Configure IPv6 from 'Off' to 'Link-local only'

Click Ok

Click Apply

AU 6.3 should now be able to communicate with your device.

jhph

Level 1

8 points

Jun 13, 2013 10:03 AM in response to Jeff Leigh

Thank you Jeff! That is the solution, worked immediately on my Mac Pro w/ a 1st gen AE.

Jun 13, 2013 10:37 AM in response to Jeff Leigh

Good sleuthing, Jeff! Works great now after switiching to IPv6. Still don't see any notification to install firmware upgrade to 7.7.1, but that's apparently what a lot of folks are experiencing..

jlophoto

Level 1

5 points

Jun 13, 2013 11:01 AM in response to Jeff Leigh

Excellent. Enabling IPv6 worked! I can now see the Gen 5 and Gen 4 Airport Extreme's.

Thanks for the help!

-- Jeff

ashute

Level 1

35 points

Jun 13, 2013 11:05 AM in response to Jeff Leigh

Worked for me evrything displaying as it should.

Thanks Jeff.

grafiksol Author

Level 1

0 points

Jun 13, 2013 11:32 AM in response to Jeff Leigh

Jeff (Leigh), your diagnosis and solution are both "right on" in identifying the problem. When I started this discussion, I also filed a bug report with Apple, and included a reference to this discussion for them to follow. An Apple Engineer has contacted me for additional details, which I have provided...also again referring him to this discussion and to your findings. Seems a bit presumptuous of Apple to suddently start relying (apparently exclusively) on IPv6 for connectivity without notifying users of such a change, or at least checking for the presence of IPv6 before blindly proceeding with the installation of V6.3. Anyway, presumably some additional <update/statement> will be forthcoming from Apple.

Jeff Anderson

Jun 13, 2013 11:40 AM in response to grafiksol

I think what probably happened is when they removed the 'Off' option for IPv6 it didn't default to another option. Hard to test a configuration you can't get to except through terminal commands. I also got an email from Apple and when they started asking for IPv6 addresses and ping results I realized why it wasn't working. Clearly the connection isn't solely based on IPv6 as Configure Other... still works. Something as simple as release notes stating that the connection now relies on IPv6 would have been very useful.

lusebra

Level 1

4 points

Jun 13, 2013 11:49 AM in response to grafiksol

On my computer iMac 27 with OX 10.8.4 changing the IPV6 to "only local link" don't sort any effect. AU 6.3 is still not working.

Jun 13, 2013 12:59 PM in response to lusebra

Do you now have an IPv6 address in the Network control panel screen?

Also check that the Airport has IPv6 enabled. You'll need AU 6.2 or 5.6 to access it obviously.

Airport Utility V6.3 Update