Kenneth Close wrote:
It's maddening that in order to get full functionality outside of a fully Mac environment, we need to replace the built-in VNC service with something else.
Traditional VNC is not Apple's central focus. The fact that they will talk to a traditional VNC server is just a side effect of having most of the protocol there already, but they are not going out of their way to make it perfect.
Mac-to-Mac Screen Sharing "is" one of Apple's focal points. And when you have a direct connection, it works seamlessly.
But you did not do straight Mac-to-Mac connections, you stuck something in the middle that forces traditional VNC, and thus you broke away from Apple's focus and confused things.
Re: etresoft, we (as in the members of my group at work) have struggled with VNC copy & paste with Linux system for the past 17 years, and I've gone though a lot of different clients. I've personally tried every Rube Goldberg trick I could think of, even if the end result was worse, just to see if I could find a loop-hole. No Joy.
At least the more recent TigerVNC and RealVNC clients offer some satisfaction.
On the other hand, at work, they new-and-improved the Linux servers so much (as in paired them down to the smallest boot disk they could get away with, so they could have more VM's) that I found I could not get a decent Linux desktop running, so I abandoned using VNC in favor of ssh to a tmux session and do everything that way. I was already living in terminal emulators, the main switch was having the terminal emulator running on my Mac (iTerm2) as apposed to the terminal emulator running on Linux and my access via VNC.
tmux keeps my remote sessions alive, so I can connect/disconnect as needed, such as the company mandatory VPN must disconnect after 24 hours rule, or Mac reboots, Mac going to sleep, etc... tmux does not care if I come or go, it just keeps my remote session alive.
Granted this is not helpful for Kenneth Close (our OP), but my days of using VNC may have been useful.