Reliability and speed do trump an initial set up phase of VNC Connect still. And in my case, I needed to open a port on my router, and to set up Dynamic DNS-something that you wouldn't normally do when using TeamViewer, for example. One notable solution was AnyDesk, which worked quite well for me, but RealVNC's VNC Connect took the crown as it was more customizable for my needs and faster too.ĭo note though, that VNC Connect requires more effort to set up as well. But what to do when they both fail at the same time?
So I have been using these 2 services concurrently to have a backup when 1 of them fails. The same, in my experience, was true with Chrome Remote Desktop-sometimes it would fail me. For NAS-supported Mac workstations, you can download a VNC client called TigerVNC from the TigerVNC website. TeamViewer was not working reliably for me and sometimes I was not able to connect to my desktop when I needed to. For NAS-supported Linux workstations, a VNC client viewer (RealVNC version 4.1.2) should be installed in /usr/bin/vncviewer. I switched to RealVNC's VNC Connect from TeamViewer, and Chrome Remote Desktop for purpose of connecting to my desktop computer remotely and RealVNC's solution works very well for me.
