Recently , my AirPort web pip a major snag . While my independent Base Station carry on to run properly , AirPort Utility ( on my Mac and iPad ) indicated that my three subsidiary AirPort gimmick had cut down off the web ( see figure above ) . select any of the equipment in the bottom row resulted in a “ equipment not observe ” error . substantiate that these AirPort gimmick were indeed MIA , none of my wireless devices ( iPhone , iPad , MacBook Pro ) would link to them . The position with AirPort Utility on my iPhone was even more disturbing : no AirPort twist showed up at all !
Huh ? Everything had been work fine for months . I had made no changes to the AirPort hardware or mount . Why this sudden and unexpected collapse ?
One possibility focus on AirPort Utility itself . I had recently update the program toversion 6.3 , the version demand to accommodate the new Base Stations with 802.11ac support . However , a computer software bug seemed more likely to precipitate only a communication failure between AirPort Utility and the AirPort devices , rather than an real removal of the devices from the internet .
In any guinea pig , a lookup of the World Wide Web revealed legion confirmations of networking problems first seem after updating to AirPort Utility 6.3.The initial posting of one threadsounded exactly like an example of my “ gimmick not found ” error . More by and large , reported problemscentered on various failure of AirPort Utility to access AirPort Base Stations .
Several possible solution were provide , including the obvious one of downgrading back toAirPort Utility 6.2 . However , the most recommended suggestion ring advice thatcomes from Apple :
1 . Go to internet System Preferences on your Mac .
2 . Select your active net overhaul ( for instance , Wi - Fi or Ethernet ) and get across the Advanced button .
3 . Click the TCP / IP tab .
4 . opt the “ radio link - local only ” option from the Configure IPv6 pop - up card and click OK .
To fix standardised problem with AirPort Utility on iOS machine , Apple ’s adviceis simple : Just power down the machine and turn it back on .
Unfortunately , I discovered all of this only after I had already made my own attempts to gear up the problem . I wind upresettingall four of my AirPort equipment and re - entering all their mount . This made for a long and frustrating evening , but eventually I got the entire connection work again . As it turned out , my fixture did not call for any change to the Configure IPv6 setting ; it stay lay out to “ Automatically . ” This was not a big surprisal , as I mistrust my trouble went beyond what the IPv6 setting savoir-faire .
For my iPhone , Apple ’s recommendation to power down the equipment was what was needed to get its AirPort Utility back on rail . After a restart , all my equipment were again listed on the phone .
If you are experiencing AirPort problem similar to what I ’ve described here , take heart . Your ironware almost certainly does not necessitate any repair or substitution . Based on what I ’ve learn online and my own experience , at least one of the suggested fixes should relieve your situation .
