Unable to connect to time capsule

actually the only way i got it work was to leave it alone! only my imac is connected to the hdd via time machine. it works.

everything else (including more than one mac connecting via utility or to the hdd) makes time capsule instable 😟

anyhow the internet connection works fine all the time

Strangely, after returning the 3TB TC for a new unit...the same problem persisted (please refer to my post on July 9th, where my new 3TB TC would NOT maintain connection to TC long enough to finish the initial backup; regardless if it was wireless or wired...and eventually the network went down...).

Additionally, I had TimeWarner replace the cable modem...and I've even tried a new RJ45 cable.

Bottom line...the problem resides in the TC software (firmware). There is no doubt in my mind...

My specific problem shows (in the TC logs) that something with a MAC address ending in ":45" is attempting to log into my new 3TB TC. And the handshake fails...a couple of times PER SECOND.

After about 8 - 10 minutes, all TC functions lock up, the backup fails and the TC reboots. I believe the log file grows too large and causes a fatal overflow / panic...somewhere...

See a small snap shot of the log file below...

My solution? I now do NOT password protect my wireless network. I don't have many neighbors nearby...as I live in a rural area. So I am not that worried. Doing so eliminated the problem...since I was unable to determine which device in my house is attempting to initiate a secure transaction/login. After making this change, I looked at the clients attempting to use my network and am unable to see ":45".

Very weird.

Anyhow, this is a TERRIBLE solution...and I look forward to a TC firmware/software update soon!!!

Apple...hurry!!!

Jul 09 12:10:28 Severity:5 Associated with station 00:11:d9:36:ae:45

Jul 09 12:10:28 Severity:1 WPA handshake failed with STA 00:11:d9:36:ae:45 likely due to bad password from client

Jul 09 12:10:28 Severity:5 Deauthenticating with station 00:11:d9:36:ae:45 (reserved 2).

Jul 09 12:10:28 Severity:5 Disassociated with station 00:11:d9:36:ae:45

Jul 09 12:10:29 Severity:1 WPA handshake failed with STA 00:11:d9:36:ae:45 likely due to bad password from client

Jul 09 12:10:29 Severity:5 Deauthenticating with station 00:11:d9:36:ae:45 (reserved 2).

Jul 09 12:10:29 Severity:5 Disassociated with station 00:11:d9:36:ae:45

Jul 09 12:10:29 Severity:5 Associated with station 00:11:d9:36:ae:45

Jul 09 12:10:29 Severity:5 Connection accepted from [fe80::223:32ff:fec8:5492%bridge0]:49608.

Jul 09 12:10:29 Severity:5 Connection accepted from [fe80::223:32ff:fec8:5492%bridge0]:49609.

Jul 09 12:10:29 Severity:5 Connection accepted from [fe80::223:32ff:fec8:5492%bridge0]:49610.

(Cross posted from another discussion thread)

Strangely, after returning the 3TB TC for a new unit...the same problem persisted (please refer to my post on July 9th, where my new 3TB TC would NOT maintain connection to TC long enough to finish the initial backup; regardless if it was wireless or wired...and eventually the network went down...).

Additionally, I had TimeWarner replace the cable modem...and I've even tried a new RJ45 cable.

Bottom line...the problem resides in the TC software (firmware). There is no doubt in my mind...

My specific problem shows (in the TC logs) that something with a MAC address ending in ":45" is attempting to log into my new 3TB TC. And the handshake fails...a couple of times PER SECOND.

After about 8 - 10 minutes, all TC functions lock up, the backup fails and the TC reboots. I believe the log file grows too large and causes a fatal overflow / panic...somewhere...

See a small snap shot of the log file below...

My solution? I now do NOT password protect my wireless network. I don't have many neighbors nearby...as I live in a rural area. So I am not that worried. Doing so eliminated the problem...since I was unable to determine which device in my house is attempting to initiate a secure transaction/login. After making this change, I looked at the clients attempting to use my network and am unable to see ":45".

Very weird.

Anyhow, this is a TERRIBLE solution...and I look forward to a TC firmware/software update soon!!!

Apple...hurry!!!

Jul 09 12:10:28 Severity:5 Associated with station 00:11:d9:36:ae:45

Jul 09 12:10:28 Severity:1 WPA handshake failed with STA 00:11:d9:36:ae:45 likely due to bad password from client

Jul 09 12:10:28 Severity:5 Deauthenticating with station 00:11:d9:36:ae:45 (reserved 2).

Jul 09 12:10:28 Severity:5 Disassociated with station 00:11:d9:36:ae:45

Jul 09 12:10:29 Severity:1 WPA handshake failed with STA 00:11:d9:36:ae:45 likely due to bad password from client

Jul 09 12:10:29 Severity:5 Deauthenticating with station 00:11:d9:36:ae:45 (reserved 2).

Jul 09 12:10:29 Severity:5 Disassociated with station 00:11:d9:36:ae:45

Jul 09 12:10:29 Severity:5 Associated with station 00:11:d9:36:ae:45

Jul 09 12:10:29 Severity:5 Connection accepted from [fe80::223:32ff:fec8:5492%bridge0]:49608.

Jul 09 12:10:29 Severity:5 Connection accepted from [fe80::223:32ff:fec8:5492%bridge0]:49609.

Jul 09 12:10:29 Severity:5 Connection accepted from [fe80::223:32ff:fec8:5492%bridge0]:49610.

Of course TC is a router! What did he think it was a modem? I hear some people calling a modem a router interchangeably and it's very confusing when trying to solve a problem when someone describes a modem as a router instead!

I have had the same problem, powering everything down (cable modem, time capsule, both MacBooks Pros) and back on has fixed it so far. Seems Apple has some kind of software or firmware problem. I wish they would post an update that fixes this. It is very annoying.

I found the answer in this archived post:

https://discussions.apple.com/thread/1421776?start=0&tstart=0

It's way simpler than anything you can imagine....

Basically, I did two things:

Went to AirPort Utility >> Disks, clicked on the name of the disk, which was Michael's Time Caps, and renamed it MikeTimeCap

I also disabled the guest network.

Now backing up for the first time in a week or so.