unusable screen sharing / vnc protocol remote desktop control


i had an i an iMac 27" x86 setup in the house before and now its been replaced by an iMac 24" m1 setup.


In both cases i enabled the recommended system preferences | screen sharing | vnc password for unattended access option to facilitate remote desktop access from my windows device to those iMac setups using real vnc viewer protocol clients, e.g. the realvnc and ultravanc viewer clients.


This is all happening over 192.168.*.* private network address space home network 450Mbs wifi5 connections.


Trouble is the performance of that out of the box screen sharing enabled remote desktop control solution is abysmal, to the point of being unusable. Also i don't get the expected context sensitive mouse pointer icons when connected and instead just a little square.


Based on what i read the alternative system preferences | sharing | remote management story only works for macOS remote desktop client connections and its finder integrated support for use of it.


Lots of hits for others who are getting this unexpected result. I looked up to see if i could install the linux/unix xrdp daemon on macOS the hits all say that due to some macOS specific modifications to that daemon/service package cannot be installed. The teamviewer QuickSupport agent enables a very efficient remote desktop connection from windows but requires someone on the receiving end to approve connection startup every time.


q1 - Might there be some aspect of system preferences | sharing | screen sharing vnc tcp/5900 protocol based remote desktop option that i need to tweak for it to be usable?


q2 - If its a well know issue that system preferences | sharing | screen sharing remote desktop connection option is really only usable for macOS remote desktop client connections what 3rd party solution are folks finding is expected to be fast and efficient?

Posted on Aug 30, 2022 9:29 PM

Reply
6 replies

Sep 7, 2022 3:31 PM in response to BobHarris

One would expect everything to perform without any issues when doing operating a vnc client remote desktop connection from a current windows 11 setup to a current m1 macOs monterey setup's sharing | screen sharing / vnc server over a fast home network wifi5 and wifi6 connection respectively.


That said i've had this issue with both an iMac x86 27" and iMac m1 24" both running monterey. I did a search on 'macos screen sharing vnc client configuration setting to fix performance' where this hit https://apple.stackexchange.com/questions/437555/macos-networking-brutally-slow-using-vnc-or-apple-remote-desktop and some background on source of issues and resolution. The issue called out there was one i seem to recall finding and trying to make this remote desktop connection scenario work well against my outgoing iMac x86 27" setup.


I ran the recommended `sysctl -a net.inet.tcp.delayed_ack` which output 3 followed by `sudo sysctl net.inet.tcp.delayed_ack=0 && sysctl -a net.inet.tcp.delayed_ack` which output 0 commands and after that my windows 11 vnc client connection to macos sharing | screen sharing / vnc server was not passably usable. The screen painting of bitmaps, e.g. desktop background, is still terribly slow and mouse motion is not anywhere like teamviewer/macos or xrdp/linux remote desktop experiences but its much better.


So i wonder why do i need to make that change to get into a not great but at least usable state for this windows to macos remote desktop connection scenario while yourself and some others do not.

Sep 7, 2022 2:18 PM in response to myusrn

I just did a RealVNC to a Mac in my basement (I used my Mac laptop to run the RealVNC viewer).


I have an eero 6E Pro mesh network. The basement Mac is connected to Ethernet via a 16 port switch to the eero router unit, and the Mac laptop running RealVNC Viewer was using WiFi and connected to one of the eero mesh nodes (not the router but one of the other nodes).


While VNC was not as responsive as macOS Screen Sharing between 2 Macs, it was only a few milliseconds of lag. Everything worked just fine in my home.


I connected to Mac_computer_name.local (as specified in System Preferences -> Sharing -> Computer Name) and it connected up just fine. I was even able to use my macOS username and password, as RealVNC understands macOS credentials. That is to say, I did not need to set an insecure VNC password.


I would expect a bit slower responses if I was at a coffee shop attempting to connect back to my home, as my ISP only gives me 6 megabits/sec out-bound speeds, and that is the direction all the screen repainting would travel over. But inside the house, it was really just fine.


Granted I would not want to play a fast twitch game via RealVNC, but for performing remote maintenance and light GUI activities it is perfectly acceptable to me.


I know a co-worker that has a company Mac which was kept in the office, and from home the used the company VPN to gain access to the company network, and then used RealVNC on their personal Windows PC to remotely connect to the work Mac and did software development via the RealVNC viewer window. Their work Mac had 2 external monitors and the 13" MacBook Pro monitor that were all being exported. At least the company's out-bound bandwidth was a lot better they what my ISP gives me 😁. So once the co-worker figured out all the connection details, they never reported any other issues using RealVNC to do their job.

Sep 7, 2022 8:34 PM in response to myusrn

I do not know.


Try booting your Mac into Safe mode

Boot macOS Safe Mode: hhttps://support.apple.com/guide/mac-help/start-up-your-mac-in-safe-mode-mh21245/mac


And then see if it still behaves strangely. Safe mode will not load any 3rd party additions, and you should be running just Apple software.


Or you could backup your Mac, then do a clean install and try it to the vanilla system. Or if you can create an external boot disk with a clean macOS install, or create an alternate boot partition on your internal disk, can try it that way without disturbing your existing customized system (still do the backup first, just in case).


Your an always restore you backed up data after you have performed the experiments.

Aug 31, 2022 8:59 AM in response to myusrn

It has been a while (years), but I was able to put TeamViewer into a mode where it allowed me to connect without a user at the remote system giving permission each time. I was able to use TeamViewer in this mode to remotely manage my Mom's iMac from 300 miles away. I no longer use TeamViewer and I do not know if this feature still exists.


Remote performance via VNC vs other screen sharing services has never been an issue, but rather feature compatibility has been the issue. Such as Copy & Paste issues, drag & drop files, etc... But whatever is on the screen should still be on the screen at the VNC viewer end of the connection.


Performance can be affected by low bandwidth up-link speeds, as most cable TV based ISPs give very slow up-link speeds, like 300 megabits down-link, and 6 megabits up-link speeds. Your VNC session needs to send via the up-link the screen and changes happening on the screen. That takes bandwidth, which many cable companies are not giving to their customers.


Also the more colors you include, the slower it is going to go. If you can limit your client so it asks for fewer colors, then that can reduce the amount of data that needs to be sent over a slow up-link.

Aug 31, 2022 1:06 PM in response to BobHarris

@BobHarris, thanks for the response.


I am making these remote desktop control connections from windows to macOs over my home network powered by an eero 6 mesh network router with wifi6 + wifi5 capable of speeds up to 900Mbs in either direction. This is not happening over my cable modem network operators uplink and downlink on the other end using some vnc protocol rendezvous service like remote.it .


I can see everything on the macOS screen when i establish the windows vnc client remote desktop control connection. The issue is that the screen repaint and mouse pointer tracking performance is terrible. In addition the mouse pointer is a little square box not the context sensitive mouse pointers you get when parked physically in front of macOS or remoting in via TeamViewer quicksupport.


I am trying get things working, in a usable way, using out of box system preferences | sharing | screen sharing vnc tcp/5900 protocol story vs having to add a 3rd party vendor end2end solution like TeamViewer.


There are others who state that this simple to enable on macOS side and simple to install client on Windows/Linux side of things is exhibiting performance issues as well. Since you don't seem to be experiencing the issues i and others are i'm wondering what might be unique about either your macOS setup side of things or on the windows/linux vnc client caller side of things.

Sep 8, 2022 7:11 AM in response to BobHarris

Thanks for the additional suggestions. This is a clean imac m1 24" device straight from Apple only a few months back with nothing added except for skype and wechat. No macos customizations made only mouse pointer speed and monterey updates applied as they come out.


The fact that this repros for me on both fresh macos x86 and m1 installs I've tried this on over past year suggests there shouldn't be anything going on with that side of the equation.


I'll have to see if I can stage a repro of this unecpected result against a neighbor's m1 macbook air and from a different windows [ or linux or android] vnc client.

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

unusable screen sharing / vnc protocol remote desktop control

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.