Screen sharing broken in Sonoma

Thanks Luis, yes it has to do with an external display. I tried screen sharing from my LG external screen with several Laptop users (Macbook Air, Macbook Pro). No success, no matter who invited whom.

Then I tried screen sharing from my Macbook Air screen to the other Laptop users who were also using their laptop screens. Each connection attempt was sucessful!

This might explain why some of you report success (connections via native screens) and other don't (external screen at least by one user).

Hopefully, the update will come soon. My workmates are on the fence about going Mac, this isn't helping when I have to rely on others (with non-Macs) to present. I can connect through Apple TV but the mouse is impossibly laggy once connected.

We (our MSP) are "trying" to use Screen Connect as we always have through LiveDesktop in Addigy, but after Sonoma, the Screen Sharing app either gives us the colored beachball or straight up disconnects us every few seconds or so.

In short, it has literally made Screen Sharing unusable in our business, it's that bad. We are now using ConnectWise screenconnect as a workaround.

Currently running Sonoma 14.1.1 using Screen Connect 4.1. It's been behaving like this since day one of Sonoma, and it is still not fixed.

Not great...

Have had the same issue with Sonoma.

Have tested one workaround several times that seems to be working:

In Finder open Locations and if network machine is showing there through File Sharing, open a folder then open Screen Sharing. Seems that the File Sharing connection re-establishes Screen Sharing.

You mean Mac (it's not an acronym, it's just short for Macintosh), but it could be a LOT of things. We would need to know much more, and it might be best to start your own question about that since it includes a third party device.

The inability to remotely control another Mac on my network is causing so many headaches and wasting so much time I wish I had never upgraded to Sonoma on my main workstation. Upgrading (downgrading) to Sonoma was a GIGANTIC MISTAKE. What ever happened to QA and critical bug fixes before release? Whoever the QA manager was on the Sonoma project should be terminated immediately.

Has anyone else updated to Sonoma 14.2? I just updated both my computers today and I've been able to use High Performance screen sharing between the two for several hours (before, it would 1) not work at all or 2) work for just a couple of minutes before the input would stop working from the remote computer to the target computer; I tried using both standard and high performance connections).

I hope this will stick, and that Crapple have finally gotten the thumb out and actually address severe issues like this, which prevents their users from using basic services that have been a part of their platform for aeons.

Please note that the Sharing settings looked very iffy on the target computer (the only "shared" items were the two public folders for the two users on that machine. I removed those and added the entire drive, allowing the default (administrators only) to access the shared folder(s). I also disable the firewall since you are not able to use screen sharing and an encrypted drive. Don't forget to reboot after changing settings like this, just to be safe.

I just did the update on both my iMac and Macbook Pro. Can't believe it doesn't work anymore.. I'm with support on the phone while writing this and they want me to bring my mouse thinking the mouse is the problem... smh I'm changing back to Ventura write away hoping they find a fix soon! I won't go back in 2005 with 2 keyboards!

Updated MBP M1 16" and Mac mini M1 to Sonoma 14.2 and Screen Sharing is now partially working. Connection can be made, yet remote Mac mini stops responding intermittently from MBP, requiring restart of Mac mini.

What is even more puzzling about this ongoing issue is that RealVNC has been working flawlessly from remote MBP and iPhone app. Maybe Apple needs to be in touch with them to learn how to make Screen Sharing work like RealVNC?

After reading your post, I attached a display to the Mac mini and screen sharing started to work more reliably. Normally, this is a headless Mac mini. When the mini is in the headless state, and you do get a screen sharing session, the screen responses are slow and fuzzy. Attached to a monitor, the viewer receives crisp and responsive feedback. Logging out the remote user on the mini does not result in a locked mini with a black screen. The mini is behaving much better with a screen attached. This leaves me to believe Apple has some issues with virtual screen management. As if the screen buffer is not created, managed in session , nor destroyed properly at the end of the session. We use headless minis for various reasons and attaching monitors to them is a terrible option to get things working well.

This has completely been destroyed now that Apple has apparently been dedicating resources to the "Screen Sharing.app"

I finally had to succumb to a couple of counter measures to get things back to a "working order..."

The first thing I realized, or should I say the last? was about 50 times every time I had a problem the machine I wanted to access had "Copying Clipboard" from such-n-such machine. And I like a dummy refused to turn off iCloud Handoff, because I use this very very frequently. But I just could handle this any more. So I turned off Handoff. This fixed problems with older machines that would stop sharing/managment. But in the end the only fix was:

If I go in and I can't get a machine going with remote managment, I have to ssh into the machine, and run this command 1st:

`sudo /System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/Resources/kickstart -deactivate -stop`

then this command 2nd:

`sudo /System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/Resources/kickstart -activate -configure -allowAccessFor -allUsers -restart -agent`

After that I can control the screen with remote management.

But man having to ssh into a machine so I can "VNC" is a pain!

Especially, when I do this to start some music from the Music.app on one of my servers (in the house) with 96/192 lossless audio files stored. So I don't have to stream them from phone or internet while working!!!

Pain in the rear for over a year!!

Laters... 2¢

On our ICT Lab in our school which has 28 mac mini M2 and 1 mac mini M2 for ICT Teacher, 3 student's mac mini upgraded into sonoma, mac mini for teacher also upgraded into sonoma and the rest 25 mac mini M2 stil using ventura and when we share screen to all 28 student's mac mini 3 sonoma will pop up crash message and other 25 ventura mac mini will blank screen, but if we share screen only to those 25 ventura mac mini all are working well. Please fix this ASAP since share screen on day to day education process is a must for us. thanks

VNC into a brand new iMac M3 with Sonoma 14.2.1 works for 10 to 30 seconds and then the iMac disconnects, the Screen Sharing feature crashes and I can no longer connect to the iMac remotely until I physically go sit in front of the iMac, turn off Screen Sharing, then turn it back on. It's ridiculous. It's impossible to do any serious work with an iMac M3.

I recently updated to Sonoma 14.3. Screen Sharing is not functioning properly. It will connect to a client for a few seconds, then it will quickly disconnect. The connection lasts for 10 seconds to a minute at best. If I connect to a client with multiple displays, the mouse only works on Display 1.

I was using Screen Sharing daily to connect to remote clients around the world. I hope Apple is aware and will fix for 14.3.1.

I have three headless mini Mac’s. After upgrading two of the to Sonoma, remote access became problematic. What I have done.

1) granted screen sharing to specific user even though administrators were granted access.

2)turned off FileVault.

3)turned off screenlock

4)put hdmi ghost plugs in hdmi slot

Without the ghost plugs fixing, the client screen would be fuzzy and slow to respond.

With FileVault turned on, a reboot of a headless configuration would result in the inability to establish an ip. On a subsequent reboot, I was presented with a recovery screen. After FileVault was turned off, the machine would establish a valid ip and boot properly.

screen lock is just in the mix somehow as it has the ability to turn off your monitor. I just disabled it to get it out of the mix.

I now have two accessible Mac minis, somewhat less secure, but accessible.