Time capsule Not Recognized in AP Utility

This is usually the simple DNS issue.

Power down the entire network and all clients.

Start up again in correct order.

Modem,

TC1

TC2

Clients.

With a 2min gap between each device that is dependent on the previous one.

No luck we will need you to fill us in on what the connections are and what is the make and model of the modem.

Make sure in the computer you have IPv6 set correctly.. for most people that is link-local only.. but for some cable that has now updated to ipv6, it now can be set to an auto.

Here is an example for wifi.

Same problem on my network. Yesterday the "Repeater" Time Capsule was not found in the Airport utility. But the LED are green and the Network works with Safari and Mail, but the hard drive was not found. After a reset to the factory setting (a nightmare when the Airport utility not found the airport station) i reconfigured the time capsule and all runs normal. Today when i started the Computer both Time capsules have the LED green but the Airport Utility found no Time Capsule. Backup canceled while the drive was not found. After a Reset to the factory settings the first Time Capsule was found (Creator of my Network) but the repeater was not found. Network for Safari and Mail works. Backup works on the first Time machine, when i mount the Time capsule hard drive. I think OS X 10.11.6 has a big bug in the WLAN routines or the protocol is bad.

Here is a part from the communication from airport from the console. Anything can understand the lines?

12.08.16 14:57:43,000 kernel[0]: AirPort: Link Down on en1. Reason 8 (Disassociated because station leaving).

12.08.16 14:58:27,000 kernel[0]: AirPort: Link Up on en1

12.08.16 14:58:27,000 kernel[0]: AirPort: RSN handshake complete on en1

12.08.16 15:00:30,000 kernel[0]: AirPort: Link Down on en1. Reason 8 (Disassociated because station leaving).

12.08.16 15:00:30,000 kernel[0]: AirPort: Link Up on en1

12.08.16 15:00:30,000 kernel[0]: AirPort: RSN handshake complete on en1

12.08.16 15:15:51,000 kernel[0]: Sandbox: SpotlightNetHelp(12748) deny(1) file-read-data /Applications/Utilities/AirPort Utility.app

12.08.16 15:15:51,000 kernel[0]: Sandbox: SpotlightNetHelp(12748) deny(1) file-read-data /Applications/Utilities/AirPort Utility.app/Contents

12.08.16 15:15:51,000 kernel[0]: Sandbox: SpotlightNetHelp(12748) deny(1) file-read-data /Applications/Utilities/AirPort Utility.app/Contents/PkgInfo

12.08.16 15:15:51,000 kernel[0]: Sandbox: SpotlightNetHelp(12748) deny(1) file-read-data /Applications/Utilities/AirPort Utility.app/Contents/MacOS/AirPort Utility

12.08.16 15:15:51,000 kernel[0]: Sandbox: SpotlightNetHelp(12748) deny(1) file-read-data /Applications/Utilities/AirPort Utility.app/Contents/MacOS/AirPort Utility/..namedfork/rsrc

12.08.16 15:15:51,000 kernel[0]: Sandbox: SpotlightNetHelp(12748) deny(1) file-read-data /Applications/Utilities/AirPort Utility.app

12.08.16 15:15:51,000 kernel[0]: Sandbox: SpotlightNetHelp(12748) deny(1) file-read-data /Applications/Utilities/AirPort Utility.app/Contents

12.08.16 15:15:51,000 kernel[0]: Sandbox: SpotlightNetHelp(12748) deny(1) file-read-data /Applications/Utilities/AirPort Utility.app

12.08.16 15:15:51,000 kernel[0]: Sandbox: SpotlightNetHelp(12748) deny(1) file-read-data /Applications/Utilities/AirPort Utility.app/Contents/MacOS/AirPort Utility

12.08.16 15:21:24,231 cloudpaird[438]: BUG in libdispatch: 15G31 - 1718 - 0x0

12.08.16 15:39:09,000 kernel[0]: AirPort: Link Down on en1. Reason 8 (Disassociated because station leaving).

12.08.16 15:39:13,000 kernel[0]: AirPort: Link Up on en1

12.08.16 15:39:13,000 kernel[0]: AirPort: RSN handshake complete on en1

12.08.16 15:39:23,000 kernel[0]: AirPort: Link Down on en1. Reason 3 (Deauthenticated because station leaving).

12.08.16 15:39:27,000 kernel[0]: AirPort: Link Up on en1

12.08.16 15:39:27,000 kernel[0]: AirPort: RSN handshake complete on en1

12.08.16 15:43:49,205 AirPort Utility[12895]: [Accounts] Failed to update account with identifier 5C43D349-B9EC-436B-AC80-26E982C5D536, error: Error Domain=ABAddressBookErrorDomain Code=1002 "(null)"

12.08.16 15:44:03,631 AirPort Utility[12895]: Failed to connect (_basePopupButton) outlet from (StepByStepNSViewController_ExtendWirelessNetworkChoice) to (NSPopUpButton): missing setter or instance variable

12.08.16 15:44:03,632 AirPort Utility[12895]: Failed to connect (_basePopupContainer) outlet from (StepByStepNSViewController_ExtendWirelessNetworkChoice) to (NSView): missing setter or instance variable

12.08.16 15:44:03,632 AirPort Utility[12895]: Failed to connect (_basePopupLabel) outlet from (StepByStepNSViewController_ExtendWirelessNetworkChoice) to (NSTextField): missing setter or instance variable

12.08.16 15:44:03,632 AirPort Utility[12895]: Failed to connect (_wiFiPopUpButton) outlet from (StepByStepNSViewController_ExtendWirelessNetworkChoice) to (NSPopUpButton): missing setter or instance variable

12.08.16 15:44:03,632 AirPort Utility[12895]: Failed to connect (_wiFiPopUpContainer) outlet from (StepByStepNSViewController_ExtendWirelessNetworkChoice) to (NSView): missing setter or instance variable

12.08.16 15:44:03,632 AirPort Utility[12895]: Failed to connect (_wiFiPopUpLabel) outlet from (StepByStepNSViewController_ExtendWirelessNetworkChoice) to (NSTextField): missing setter or instance variable

12.08.16 15:44:07,000 kernel[0]: AirPort: Link Down on en1. Reason 8 (Disassociated because station leaving).

12.08.16 15:44:07,000 kernel[0]: AirPort: Link Up on en1

12.08.16 15:44:07,000 kernel[0]: AirPort: RSN handshake complete on en1

12.08.16 15:50:41,000 kernel[0]: AirPort: Link Down on en1. Reason 3 (Deauthenticated because station leaving).

12.08.16 15:50:45,000 kernel[0]: AirPort: Link Up on en1

12.08.16 15:50:45,000 kernel[0]: AirPort: RSN handshake complete on en1

This all working well for the past to years, until this situation thats started yesterday...

I think the TC has a reliability issue at around 1-2 years.. mine just took a nosedive and I have reverted to my older Gen4 TC which IMHO is a better model.

I strongly recommend you do factory reset on both TC.. do it on TC1 first without TC2 connected at all.

Factory reset universal

Power off the TC.. ie pull the power cord or power off at the wall.. wait 10sec.. hold in the reset button.. be gentle.. power on again still holding in reset.. and keep holding it in for another 10sec. You may need some help as it is hard to both hold in reset and apply power. It will show success by rapidly blinking the front led. Release the reset.. and wait a couple of min for the TC to reset and come back with factory settings. If the front LED doesn’t blink rapidly you missed it and simply try again. The reset is fairly fragile in these.. press it so you feel it just click and no more.. I have seen people bend the lever or even break it. I use a toothpick as tool.

N.B. None of your files on the hard disk of the TC are deleted.. this simply clears out the router settings of the TC.

Setup the TC again.

Then redo the setup from the computer you want to use for TM using Airport Utility.

1. Use very short names.. NOT APPLE RECOMMENDED names. No spaces and pure alphanumerics.

eg TCgen5 for basestation and TCwifi wireless name.

If the wireless is still a problem set wireless names like TC24ghz and set the 5ghz to different name.. eg.TC5ghz

2. Use all passwords that also comply with 1. but can be a bit longer. ie 8-20 characters mixed case and numbers.. no non-alphanumerics.

**3. If the TC is main router you can skip this point. This is only an issue when the TC is bridged.

Ensure the TC always takes the same IP address.. you will need to do this on the main router using dhcp reservation.. or a bit more complex setup using static IP in the TC.

4. Make sure IPv6 is set correctly in the computer. ie link-local only for ethernet and/or wireless depending on which you use. Auto is not good enough.

In your setup it is really important for both TC to maintain a static IP..

Your first one in router mode will be fine. If at default it will be 10.0.1.1

However the second TC can easily get lost so use either DHCP reservation or fixed static IP on it.

If you use it as per normal bridge with wire connection let me strongly recommend you move the connection from WAN port to LAN once setup is done.

I also need you to tell me how the two TC are connected.. wireless or wired?

The latest DNS is problematic and has been for a while.. that is why static IP is essential.. then you can mount the TC disk manually by IP.

I can give you a bit more info on that but give me some screenshots first once you complete the factory resets.

You have the same messages repeated over and over..

En1 being wireless?? Is not stable.

Try using ethernet.

Here is a part from the communication from airport from the console. Anything can understand the lines?

12.08.16 14:57:43,000 kernel[0]: AirPort: Link Down on en1. Reason 8 (Disassociated because station leaving).

12.08.16 14:58:27,000 kernel[0]: AirPort: Link Up on en1

Make sure IPv6 is set correctly to link-local only.

I'm having this exact problem and it started at about the same time. Funny that!

All the above suggestions have no impact. Same problem. In addition, the computer can see the hard drive, but Time Capsule cannot! The AP utility cannot see it over WiFi or Ethernet. However I can get to it by entering "Configure other..." and make changes. However, the network changes are not retained and it still doesn't show up in the APU. Each and every time I have to manually enter the IP address.

BTW, I have to use DHCP & NAT. I'm connecting to the Internet via PPPoE and when doing so that's the only option available.

I don't know how they did it, but it looks like Apple was able to screw up a whole bunch of Airports all at the same time.

BTW, this is Airport Extreme #3. One and two lasted a bit less than two years and number three is just a bit over two years. Nice way to sell more hardware.

Chris

In addition, the computer can see the hard drive, but Time Capsule cannot!

I am pretty sure you mean Time Machine here??

The computer would not see the hard disk if the TC did not see it.

I suggest a few things.

1. Mount the TC disk manually.

ie In Finder use Go, Connect to Server. AFP://10.0.1.1 (or whatever your TC IP is.. it must be static).

2. If possible no wireless.. do it with ethernet straight to the TC.

3. Use Carbon Copy Cloner or Chronosync for a while.. I generally recommend to people Time Machine is rather finicky and issue prone now.

BTW, this is Airport Extreme #3. One and two lasted a bit less than two years and number three is just a bit over two years. Nice way to sell more hardware.

I would say the same applies to most brands.. the latest AC version airport and TC have been rather less than reliable in my experience.. I am also on my 3rd one which has also taken a dive.. I think I will dispose of it and go back to using other brand router and the synology NAS.

I've reconfigured my first TC and used a TC 2 Gen. since yesterday. It works. Now today i filled the fields from "Zugang zu meinem Mac" with my apple id and my password and the timcapsule was removed from Airport Utility. Then i restart the TC open the settings in Airport utility and removed the bot lines (see screenshot) and the TC is not removed. Can you check this and test it?

Best regards

Lutz

Here is the Screenshot from Airport displayed after removing the both lines.

LaPastenague,

Thank-you very much!!!!! I did what you suggested by connecting to the server via AFP and now backups are working again. Whew!

(And yes, I use AE = TC since they are really the same except for the disk.)

AU still doesn't see the "TC", but at least I can manage it by using "Config other....".

To summarize what appears to be known:

1. The problem applies to a lot of AE's, but not all.
2. Recently a lot of AE's suddenly developed this problem.
3. It isn't the computer. I've tried both Windows and Mac and had the same issues.
4. A soft reset has no impact.
5. A hard reset has no impact. (Good idea to keep current configuration exports.)
6. The problem has possibly come and gone for the past several years. (Not sure that it's exactly this problem.)
7. Does not appear to have been triggered by a SW/FW update.

So it's very likely the problem is with the AE/TC itself. Anyone try a return to factory defaults? (After exporting the configuration.)

Chris

Hi Chris, I did all the 3 reset options on my airport extreme, unfortunately no change. For the moment I'm happy with the workaround for accessing AE via AU and the connected HD via Finder "go to" and using the IP "Connect to server" until this behavior has been fixed.

Hi,

make following.

Hard reset the TC or AE. Open Airport utility and select the TC or AE (you have not much time 1 or 2 minutes)

Clear the formula fields below the Password fields for the TC or AE. Actual the settings and than wait some minutes. It's possible you have the same issue with the firmware how I. My network runs now stable.

I'm having this same issue starting August 11th. My mac hasn't been able to do a backup because of it.

I read on another thread (Why am I seeing "device not found" AirPort Admin?) that it has something to do with Back To My Mac being enabled on the time machine. If you have it enabled, try disabling it on the time machine (not your computer).

I just tried it on mine and it is working fine (for now at least).