back to my mac iCloud server not responding

John,

I may or may not get a message back with what is going on. However, I think they are going to have to fix something in Mavericks. I suspect it is some weirdness with 1) upgrades from .mac, mobile me, and then icloud or something weird with ipv6 tunnels to icloud.

John

I found another solution last week. It is described here:

http://rogersm.net/icloud-problems-mountain-lion-serial-number

Please follow the instructions exactly. Don't worry: no terminal stuff. I was successfull in applying the app.

I've had serial numbers all along, and Back to My Mac still doesn't work for me.

But the Connect to Server workaround works for me every time.

Janauk,

This may help some people but this isn't the case for my situation. Both my Macs have serial numbers.

John

I used BTMM without incident and often under 10.8. It has been broken since 10.9.

dns-sd -B _afpovertcp

... returns correctly on both machines.

ping6 machinename.3614205214.members.btmm.icloud.com

... returns correctly on both machines.

I've tried the methods in this thread to no avail.

I got this working finally ... by doing a clean install. I suspect that either TunnelBlick was causing a problem, or my having had ML Server installed and not cleanly removed was the culprit. I had noticed I was unable to ping, even locally, with IPv6. I'd done a fresh install in a new partition, and when it worked I decided to bite the bullet and clean install, without restoring directly from time machine. No issues so far.

Hopefully there is a better solution out there though!

TGN,

My ping6 and traceroute6 work fine. Apple is still working to find the problem. I suspect something left over from a previous iteration is causing the issue. When Apple finds something out, I will let you all know.

John

Does anyone know if BTMM works on brand new machines and/or a clean install of Maverick?. Just trying to gauge whether the problem is only on machines that have been updated. I have a new iMac on order. I'm hoping that BTMM will work.

I don't know if this is a fluke, but since updating the firmware on my AC Time Capsule, all of a sudden, I can see and access my Mac Mini at home from my MacBook Pro at work using Back to My Mac. I do not believe I have done any additional trickery to make this happen!

I will update people if anything changes!

Hello all,

Based on the engineering questions I am getting, it appears they are focusing on the cable modem. I have a Ubee from TWC. Those having issue, can you post here your router and modem configuration?

John

BTW, I have a 4 Generation TC with the Ubee in bridge mode.

John

One 4th generation TC in bridge mode, connected to a 2nd generation TC in router mode. Cable modem: CISCO EPC3928 (provider: Ziggo - Netherlands)

I have an early model TC in bridge mode connected to an Asus RT-N16 router. My cable modem is a Zoom 3.0 series 1079. My friend has no TC, connects with a new Linksys router (model ?) and connects to the internet via Qwest DSL device.

I have the most recent version of the FIOS-supplied router. I, like many others, was using BTMM successfully for a couple of years -- NO ISSUES until I upgraded to 10.9. It appears to me that the issue I'm having DOES NOT relate to DISCOVERING other BTMM Macs (that are outside my home router sub-net; those inside work just fine) but in actually RESOLVING the IP address of the remote host once choosing/using the BTMM DNS-supplied name. This is true whether trying to access the remote Mac via the Finder OR in Terminal with the Remote Connection panel. BTW: I've tried EVERY solution that I could come up with from this and other forums. Also, I performed an upgrade from ML, not a clean install of Mavericks.

By my way of thinking, this problem was caused by the installation of Mavericks.

I agree. Something about Mavericks "broke" this for me. However, it could something about how Mavericks is interacting with certain configurations is causing issues.

John