Fixing AirPort Utility 6.3 problems

This is a discussion on Fixing AirPort Utility 6.3 problems within the Apple Airport forums, part of the Apple Hardware category; Recently, my AirPort network hit a major snag. While my main Base Station continued to function properly, AirPort Utility (on my Mac and iPad) indicated ...

Results 1 to 1 of 1
  1. #1
    Join Date
    Jul 2011
    Northern Michigan
    Member #
    316 times

    Fixing AirPort Utility 6.3 problems

    Recently, my AirPort network hit a major snag. While my main Base Station continued to function properly, AirPort Utility (on my Mac and iPad) indicated that my three subsidiary AirPort devices had dropped off the network. Selecting any of the devices in the bottom row resulted in a ‘Device not found’ error. Confirming that these AirPort devices were indeed MIA, none of my wireless devices (iPhone, iPad, MacBook Pro) would connect to them. The situation with AirPort Utility on my iPhone was even more disturbing: no AirPort devices showed up at all!

    Huh? Everything had been working fine for months. I had made no changes to the AirPort hardware or settings. Why this sudden and unexpected collapse?

    One possibility focused on AirPort Utility itself. I had recently updated the application to version 6.3, the version needed to accommodate the new Base Stations with 802.11ac support. However, a software bug seemed more likely to precipitate only a communication failure between AirPort Utility and the AirPort devices, rather than an actual removal of the devices from the network.

    In any case, a search of the web revealed numerous confirmations of networking problems first appearing after updating to AirPort Utility 6.3. The initial posting of one thread sounded exactly like an instance of my ‘Device not found’ error. More generally, reported problems centred on various failures of AirPort Utility to access AirPort Base Stations.

    Several possible solutions were offered, including the obvious one of downgrading back to AirPort Utility 6.2. However, the most recommended suggestion echoed advice that comes from Apple:

    1. Go to Network System Preferences on your Mac.

    2. Select your active network service (e.g. Wi-Fi or Ethernet) and click the Advanced button.

    3. Click the TCP/IP tab.

    4. Choose the ‘Link-local only’ option from the Configure IPv6 pop-up menu and click OK.

    To fix similar problems with AirPort Utility on iOS devices, Apple’s advice is simpler. Just power down the device and turn it back on.

    Unfortunately, I discovered all of this only after I had already made my own attempts to fix the problem. I wound up resetting all four of my AirPort devices and re-entering all their settings. This made for a long and frustrating evening, but eventually I got the entire network working again. As it turned out, my fix did not require any change to the Configure IPv6 setting; it remains set to ‘Automatically’. This was not a big surprise, as I suspect my problem went beyond what the IPv6 setting addresses.

    For my iPhone, Apple’s recommendation to power down the device was what was needed to get its AirPort Utility back on track. After a restart, all my devices were again listed on the phone.

    If you are experiencing AirPort problems similar to what I’ve described here, take heart. Your hardware almost certainly does not need any repair or replacement. Based on what I’ve read online and my own experience, at least one of the suggested fixes should remedy your situation.


  2. Ads


Remove Ads


Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts

Similar Threads

  1. AirPort Utility 6.2
    By kobzar in forum Mac OS X
    Replies: 6
    Last Post: 05-31-2014, 02:49 PM
  2. Replies: 4
    Last Post: 02-11-2013, 12:52 PM
  3. Apple's ebook price-fixing court battle spills into Canada
    By sparkyscott21 in forum Apple News
    Replies: 0
    Last Post: 04-21-2012, 01:58 PM
  4. Replies: 4
    Last Post: 04-03-2012, 02:51 AM

Contact Us
Back to top