Originally published at: https://tidbits.com/2018/08/25/apple-abandoning-back-to-my-mac-in-mojave/
Apple has posted a support article about how the decade-old Back to My Mac service—which enables users to access files on and share screens with on their Macs over the Internet—will not be in macOS 10.14 Mojave.
Originally published at: https://tidbits.com/2018/08/25/apple-abandoning-back-to-my-mac-in-mojave/
Do we know if BTMM will continue to work with older OS’s, or will they be removing the functionality from iCloud for everyone? I suspect the latter, though the announcement doesn’t address this.
Back to my Mac - hasn’t worked for years. Barely worked when it did.
I have found BTMM (in remotely connecting from my MBP to my iMac) very helpful and easy to use, however it sometimes didn’t work, or was erratic with making the connection. I had to get someone to restart the iMac to make a connection work, as in show up in the sidebar (not a good thing to rely on someone else to be onsite!). That’s a great feature when connecting into your own devices.
However, the feature I use most is helping elderly clients via Messages Screen Sharing to give simple and even complex tuition on using apps or even something really simple such as putting back into the Dock an app icon they may have removed accidentally etc. It is a very convenient, time saving, way of assisting people.
With Screen Sharing (via the Messages app) I find that works really well, when it works. In Australia I’ve found the Telstra supplied modems often times don’t allow me to access a client’s computer, but I could share my screen with them.
At one client’s house, I could screen share easily with his iMac, but his MBP wouldn’t connect as “me to him”, but would connect if I shared my screen with him.
I’ve found that turning off and turning back on the Back To My Mac in SysPrefs will sometimes allow a connection to work properly. But not always.
It seems Apple are really only wanting Screen Sharing to work on a LAN as their support guides don’t give hints for remote connection troubleshooting.
I would like a guide on how to use (and troubleshoot) the app ScreenSharing (which is in a “hidden” folder on the Mac) so that if a client on the other end of the phone can tell me relevant info required in their SysPref Sharing dialogue box, to make a ScreenSharing connection.
I’ve used TeamViwer (I think ScreenSharing via Messages works better once a connection is made) but find it harder to invoke especially it the client is not computer savvy and has not used TeamViewer previously.
One thing with TeamViewer is that it always seems to be able to make the connection (when Messages ScreenSharing wouldn’t).
Apple seem to have their own app they get a customer to download and then tell the Apple person the code they see on screen to make a connection (but it may be observe only?)
Who has the answers?
I’ve used BTMM to remotely access my own machines for years, with few problems. And those were due to whatever router I had at the time not being able to correctly allow setup via UPnP.
Since TeamViewer was mentioned, would that be able to allow screen sharing back to a machine without anyone sitting in front of it? (Like back to my desktop while I’m out of town.)
Yes. You can set it up in a few ones, and one of them is unattended access.
Apple has a long history of abandoning their software. So do others, but it is frustrating because we expect better from Apple.
I think some of this comes from being so secretive about their projects. They never test them out in the real world, and when they do, they are not used as much as they like. On the other hand, a few people use them extensively (Aperture) and then they feel upset when something in their workflow is taken away.
In principle that can work right out of the box. Enter the remote Mac’s IP in the Screen Sharing app and as long as that remote Mac is set up to allow Screen Sharing (Sys Prefs > Sharing) it should work just fine.
The reason most people will run into trouble here is not related to SS, but rather networking. Many remote Macs will be sitting on a LAN behind a router that is running a firewall that will be blocking incoming port 5900.
If you’re a bit UNIX savvy and not afraid of the CLI you can easily get around this by setting up SSH port forwarding and just tunnel SS traffic through 22 to the remote Mac. I have used that myself for many years and, especially if you have static (or rarely changing) IPs, that will be very convenient to use in practice.
Things can get more complicated if you do not have access to the firewall setup on the remote router so you cannot ensure that e.g. 22 is open so you can use it for secure tunneling or if you have frequently changing IPs. If I understand right, the problem with BTMM now vanishing is that this last step was taken care of behind the scenes by macOS. BTMM would basically act as a dynamic IP forwarding service. It’s this last important bit of the puzzle that Apple is removing. IIRC you could even use BTMM to collect the dynamically changing remote IP by hand parsing some command output (can’t find the link right now).
If Apple would include IP forwarding into FMMac or FMiPhone that would basically solve that issue. You’d get the IPs of all your iCloud devices, maybe even an ad-hoc name (something like 123456.youriCloud.iCloudClients.apple.com). But Apple hasn’t done anything like that as far as I’m aware—I’m sure that’s too corporate or too yesterday, that’s what the Genius Bar is for. There are of course commercial dynamic DNS updating services, but apart form costing money that needs to be set up beforehand and not just the moment your 92 year old uncle Harry calls you up from Duluth because “it’s no longer printing” and is expecting some magical solution from you sitting 1,500 miles away pronto.
I agree. But I think it’s not just software. In general, Apple can get all revved up about something only to then lose interest a while later. Once that happens things go stale really fast and you wonder about the contrast that displays compared to the OMG-what-the-holy-hoopla stance they displayed two years when they were launching the thing.
We don’t know, no, and won’t until Mojave ships.
And let’s not turn this into complaining about how Apple or software companies in general abandon software. It happens, and we don’t have to be happy about it, but there’s nothing new to say about it.
It’s much more interesting and positive to talk about what we’ll use to replace the missing capabilities.
I’ll be honest: I never understood what BTMM was supposed to do, and never bothered to figure it out. I would like to be able to remotely access things on my home 192… network behind a frequently changing ip. I do have dynamic dns set up with my dns provider and run a shell script on my mini to keep it updated. It’s a pain. Would be nice to have an easy secure way to get on my local network.
As the TidBITS survey shows, most people don’t use BTMM. And readers are much more likely to than newer Mac users. Apple hasn’t promoted the feature for some time.
I understand the disappointment from the community when a feature or application is sunsetted. Sure, it’s disruptive and upsetting. But I wish TidBITS would refrain from the “click-bait” headlines. “Abandons?” Seriously, shame on you TidBITS. As a paying member I expect higher editorial quality.
I used to purchase JollyFastVNC Home to use as a VNC client to connect to my Macs on my LAN. Then I discovered macOS came with a way to do screen sharing and file sharing without a third-party client. I stumbled across the syntax to use Finder’s Go > Connect to Server to launch the appropriate client and I have never looked back.
I have been given the responsibility of helping remote relatives with their Mac. Trying to explain something over the phone is not as good as screen sharing with them. I will need to find a low cost method for screen sharing with remote family members. Any suggestions beside the one mentioned in the article?
Sorry you feel that way, but seriously, you see “Abandoning” as click-bait? And one entirely accurate word in a title is enough to trigger a larger concern about our editorial quality?
We write titles that we think will attract attention, yes, because the entire point of the headline is to encourage someone to read the article. “Support Note Indicates Back to My Mac May Not Be Available in Mojave” is equally accurate but way more boring. But I don’t see "Apple Abandoning Back to My Mac in Mojave as click-bait.
Click-bait would be “Apple Rips Back to My Mac out of Mojave and Stomps on its Corpse to Spite You.”
BTW, I just spent 15 minutes replying to this instead of writing or editing TidBITS articles.
No, I’m sorry to have struck a nerve. “Abandoning” is a pretty emotional word. Abandoning a child, abandoning your post, abandoning ship? Did Apple “abandon” the PowerPC processors? Did they “abandon” iPhoto? To me language makes sense. I would have suggested “drops support” or even BTMM is “gone” in Mojave. “Abandon” is quite pejorative.
“Clickbait” was probably not fair, but “abandon” is inappropriately sensational. Best regards.
- cease to support or look after (someone); desert.
“her natural mother had abandoned her at an early age” <–
- give up completely (a course of action, a practice, or a way of thinking).
“he had clearly abandoned all pretense of trying to succeed”
You didn’t strike a nerve so much as your criticism came out of nowhere. And it seems really trivial and thus a waste of my time to deal with. We publish thousands of words per week, and we can’t vet every one of them for whether someone might consider it emotional. And many people do feel that Apple abandons them when it drops support for long-standing technologies, so it doesn’t seem inappropriate to acknowledge that in a small way.
Kind of! I know a lot of people affected in each migration Apple makes who feel left behind. Apple has what I think is a salutary habit of “killing their darlings.” The reason the company produces ever-better technology is that they don’t keep old stuff alive forever. Microsoft’s biggest technical debt in the 2000s, something that I think horribly weighted it down, was keeping Windows 95, 98, Me, and 2000 running. (They couldn’t just rip a bandaid off, but they had options of proceeding that they didn’t take, such as shifting to virtual machines for legacy support, etc.)
I receive email almost every week from iPhoto users who feel abandoned (in my capacity writing the Mac 911 column at Macworld). Folks try Photos and, three versions in, they still hate it or find features missing. There are a lot of bugs or broken features remaining. (Try to set up a slideshow in Photos and maintain the order of your pictures!)
If you don’t use BtMM, you don’t feel left behind. If you do, we’ve received emails and I’ve read messages on social media by people who really feel betrayed and left out, because this breaks the only viable method that worked for them and was free to boot.
Folks will get over it. But I don’t think the word “abandon” is as weighted as you feel.
[sarcasm]Adam, I fought for that headline! I still think it’s the good one.[/sarcasm]
The simplest is to use the ‘ask to share screen’ function in Messages on the Mac… assuming they have logged into it with their Apple ID successfully.
Screens for Mac is pretty painless with their Screens Connect and Screens Express add-ons, if you want a single purchase solution.
Teamviewer is fantastic, and can be used for personal use for free… but after that is a monthly license cost.
As I mentioned earlier in this thread; setting up dynamic dns (to find the ip of the remote computer), ssh/vpn tunnels to carry the traffic, holes in the firewall and Apple’s Screen Sharing app, all work very well together.
Nah…abandoned is an ok word but it doesn’t really work anyway. BTTM has always been broken for me and I switched to Screens long ago.