iCloud server not responding

Worked for me as well.

Not sure how you figured that one out, but it worked for me too on 2 of my machines. thank you!

Dan

Thank you. Solved my problem also. My AppleID password changed and I would guess BTMM does not update because it uses a separate key.

This ultimately worked for me, but there are a couple caveats. Step 3 didn't appear to apply to my view of keychain access and I do not know why. In step 5, sorting by "Kind" went from "application password" to "certificate" without anything starting with a "B" in between. However, when I typed in "Back" into the search box, an item whose kind was "Back to My Mac Key" mysteriously showed up. I deleted it and ultimately that worked to restore my Back to My Mac capabilities. It's weird though that it didn't show up when sorting & scrolling to find the item by the "kind". It wasn't a case-sensitive sort either. I visually scanned the whole thing multiple times. It wasn't there for some reason.

Rob

While this fix does allow me to connect at all, it doesn't address the incredible flakiness of the connection. In the three hours I've been at work, I've lost the connection back to my home computer half a dozen times, and each time I have to turn Back to My Mac off and then back on again.

true, no sign anymore of a non responsive server, and I still see my remote computer, I can't log on to it, nor share its screen...

And I didn't see a deletable key in my keychain, like hepcat72, only after typing it in my search box, and then I got the message that I couldn't delete it because it already was ?????????

But still, the message is gone.

Could apple delete a keychainacces by remote?

Thanks as well to Bladdernose!

I was having a problem with my iMac not Sleeping, and I suspected it had something to do with a Console message that I was literally getting thousands of per day:

It read "awacsd: Connection failed. Retrying in 10 seconds."

I searched these forums for information on the awacsd process and came up with very little, other than that it had something to do with Back to My Mac. I didn't see how that could be the problem, since I have never used or activated Back to My Mac.

But I read your post here and figured what the heck- I'll try it. So I turned on BTMM in the iCloud Preferences pane, and sure enough got the "Server not responding" message. Soooo, I went ahead and accomplished your Keychain cleaning as described above. And that did it! BTMM activated. I then looked at my Console and the awacsd errors stopped for the first time in a week! And best yet, my Mac now sleeps!

I've now turned off BTMM since I don't use it, but the point is this solved the Awacsd errors and that's great! FWIW, I too suspect that the error was caused by some Mobile Me server (now shut down) that my Mac and the Awacsd process were trying to connect to. Clearing out that Keychain item fixed it! So thanks again!

Dave

hepcat72 wrote:

This ultimately worked for me, but there are a couple caveats. Step 3 didn't appear to apply to my view of keychain access and I do not know why. I

Rob-

I briefly ran into that as well. Turns out I needed to click the Show/Hide button in the bottom left of the Keychain Access window. That puts it in the view that Bladdernose is describing.

Dave

Worked for me too. Thanks.

Actually, only needed to delete ONE of the keys - the one obviously MUCH older than the three that were created on the day I tried to use BTMM, and as suggested in this post it probably referred to MobileMe of Mac.com.

Thank you! - Solved my problem too.

Thanks did the trick.

This worked! Why hasn't Apple picked up on this and included this fix in an update or an email instruction?

I should point out that I was having a different Back-to-my-Mac issue that could possibly be related to this issue.

When I followed the iCloud transfer procedure, it prompted me for my Apple ID and I entered it. I thought "Oh cool, everything from my mobile me account is going to be consolidated with my Apple account that I use for iTunes, the App Store, and accessing developer tools, etc. and I'm still going to be able to use my me.com email address." What I didn't know though was that my me.com login is what it really wanted. Somehow, I ended up with 2 incomplete and separate iCloud accounts on different computers which was causing me to not be able to share my screens. So the take-home lesson is "Watch out! you might have 2 iCloud accounts and not know it."

Rob

Bladdernose has the solution that fixed mine, thanks. I had to check und uncheck twice after deleting the key before the server warning went away.

Thank you, Bladdernose!