When looking at speed it is actually sending data between 4.5 and 8.5MBps on a 14MBps up- and down connection. You guess or you know from own experience and testing?Īs in my case it isn't doing too bad really.

Possibly the same also applies when trying to add remote systems when using Tailscale? Or even VPN? But wouldn't have guessed CMS was also to be regarded as one of these Internet services?

The DSM Help states about setting the Advanced External Access option : ' If you would like Internet services (such as Google Docs or Pixlr) to access your Synology NAS, you can specify the public, external hostname and port number at Control Panel > External Access > Advanced. The Synology KB nor CMS help ( ) were helpful in pointing out how to properly deal with, let's call it, a VPN (even though solutions like Zerotier or the similar Tailscale are actually different in their approach). Not sure if logging in to the central CMS Host on its ZT interface instead its the local lan interface also made a difference on top of that?īut compared to for example setting up Hyperbackup, this wasn't a walk in the park and I still have no clear idea why or what actually is causing the issue screwing up things with CMS, but as the remote CMS client also needs to talk back to the CMS Host, by the looks of it, this External Access seems to actually arrange that it communicates with the correct IP after the other host? So once that was done on both the CMS Host and the remote CMS client, the client could be successfully added. So each Synology needs its own Zerotier IP stated in the field 'Hostname or static IP'. Only after I added the ZT IP of a Synology into the Advanced tab of the External Access in the DSM Control Panel > Connectivity. Also the CMS entry in the DSM Control Panel > Services of the remote Synology was never created, unlike with other locally CMS managed Synologies. The newly added CMS client remained in the status 'Joining' and therefor never completing. Heck, it even prompted to input for the 2FA of the admin account of the remote system. It made some connection when specifying the ZT IP of the remote system. But getting it added to CMS proved to be rather problematic. Also performing Hyperbackups or rsync over the ZT interfaces of my primary Synology at home to the one I put at a friend's place, was working flawlessly. I can login just fine to a remote Synology using its Zerotier virtual network connection from a PC or laptop running also Zerotier.

I did not have any issue adding local systems, except when trying to do so with a remote system over a Zerotier (ZT) virtual networking connection. Was fiddling way too long to get it to work to have a remote system added to CMS (Central Management System to manage other Synologies).

Best way to remote into mac