back to my mac iCloud server not responding

More than likely it's because I'm a dunce (wearing the cone of shame), but I can't get the Connect to Server string to work for me. I have everything updated in Mavericks, Firewall off. My setup is:

Cox internet cable modem -> Apple Time Capsule -> Wireless Connection to Macbook.

My router WAN address looks something like 98.169.xx.xxx and my LAN address of my computer looks like 10.0.1.xx

I'm sure it's probably something I'm doing. "It's not you, baby, it's me."

Connect to Server… should be:

vnc://98.169.xx.xxx:10.0.1.xx with the x numbers converted to real numbers.

Check your Sharing Preferences Panel:

When you make the first connection, you will need to put in your user name and password. After saving, you shouldn't have to enter them again.

Until Apple comes up with a fix the only solution for me is LogMeIn. It's not quite as easy as BTMM, but it's still easy, free, and most importantly, IT WORKS!

James, I had been using IPv6 addresses in the past, so my conclusion that vnc:// strictly does not work is premature. I will try using IPv4 as in your example instead, and let you know.

At this point I'd welcome any workaround. Thanks!

I found one thing I was doing wrong. I left the [brackets] in the command.

Other point of interest. I am trying to connect to my work iMac from my home Macbook. For the two addresses, are they derived from the home or work computer?

Those are the addresses of the remote Mac - in other words, not the one at which you're seated when attempting to connect to the other.

Part of the problem is that those addresses don't always remain the same. Unless you pay for a static IP address, your ISP changes your IP addresses periodically. The remote Mac's IP address may also change, if you were to reboot your router or if the Mac remains offline for the duration of its DHCP lease. Of course you can assign your Mac a static IP address too.

BTMM precludes all that tedium... when it works.

Just for the record, I don't think router IP addresses change as often as they used to. I just rebooted my router under AT&T U-verse service, and the WAN IP address did not change.

Also, if your router doesn't support a DDNS service (Apple routers don't), you can subscribe to a service (for as little cost as free) that will update any router WAN IP address changes via an always-running app on one of your computers. The Connect to Server string I always use for my home computer is:

vnc://xxxxx.dyndns.tv:192.168.1.28

If you're doing remote connections regularly, I think it's always best to assign a static LAN IP address to the remote computer or computers.

Thanks James, I assume you are using dyndns?

As you wrote my external IP changes very infrequently. Less than every couple of months, perhaps twice a year.

Like everyone else I've been patiently waiting for Apple to fix this. With no resolution forthcoming it's time to devote my attention to a workaround. I appreciate your suggestions.

tried vnc and afp and nothing still. It's def not a port issue.

We don't know what you've tried to do nor do we know what your settings are. If you want to post more information about what you're doing that doesn't work, perhaps someone can help you.

sorry, my response was orginally intended as follow up to my conversation with John Galt (where I've mentioned what I've tried etc). No worries, appreciate the follow up.

Just wanted to follow up on my experience. When I originally posted, I was using a MBP that we'll call "ORIG". I had been running ML on that and using BTMM with no problems. I then upgraded to Mavericks and BTMM stopped working. Tried all the various suggestions found here and elsewhere to fix the issue with no success. Upgraded my MBP to a new one, that we'll call "NEW", by doing a TimeMachine backup from ORIG and then using Migration Assistant to migrate my user from ORIG, from the TM backup. HOWEVER, when I selected what to restore, I selected ONLY my user. DID NOT select the System stuff or "other files" options. JUST my user. When logging in to that user once it was restored, I had to validate a few things in iCloud preferences, but toggling BTMM resulted in a successful use of BTMM.

This would indicate to me that there's something at the System level that is the issue. Some sort of inconsistency that is causing confusion due to the Mavericks upgrade; like having two different configuration files that conflict or something.

Anyway, I hope that maybe someone else could repeat the steps I did and determine if it works for them in hopes of providing a workaround for those still experiencing this problem.

Happy Holidays!

I wanted to follow up in case it helps someone- I was able to finally figure this out on my end albeit it doesnt make a ton of sense at the moment.

I was able to connect via terminal to screen sharing on my remote mini (using MBP). I rt clicked terminal for the automatic 'new remote connection' and saw that using the SSH command 'SSH -2 -2 username@remotecomputername....' worked as opposed to 'SSH -2 -6...' which I was using before.

Total accident but seemed to do the trick. Hope this helps.

-d

Brilliant answer, thanks! I've been searching for weeks for a solution and this nailed it.

I was having mavericks-related issues, and then made them a lot worse by implementing a VPN with split-tunneling to connect to work. Your solution is EXACTLY right, as it allows me to use the VPN and target the internal IP addresses rather than using the internet iCloud routing that my splt-tunneling was trying (and failing) to use. Thanks SO much!

I'm going to reintitate this thread, maybe someone at APPLE wil read it. BTTM same problem since Mavericks.

RIght now in my office away from home I have a mid 2012 retina MBP and a late 2012 iMac right next to each other, and a mid 2013 iMac at my home, both computers in office are on WiFi wireless. same network.

The MBP BTTM works fine to connect to iMac at home.

The iMac right next to the MBP will not BTTM connect to iMac at HOme, giving the "iCloud server not responding" message in the iCLoud preferences in system preferences.

The iMac at home connects to the MBP at work

this used to work fine with iMac at work, so it , like others, seems to be MAvericks related, but only on one computer!

All have Mavericks. All updated etc. Same sharing preferences.

Lets fix this APple!

roger