Ask the NAS manufacturers? I guarantee you SyncBackFree is passing your Destination path to the Windows APIs we use for copying exactly as you entered it.
Or, somehow your drive mappings sometimes point to one level deeper (though I can't think how - but that would be a Windows issue anyway. If you use a UNC path as Destination, you can prevent (rule out) that aspect at least. Simply substitute the
\\SERVER\SHARE
that S: is mapped to (instead of 'S:') in the Destination string.
Note that using mapped drives and UNC paths (at the same time) can lead to conflicts (especially if you try to use different credentials for each, which is generally not possible). If you get anomalies, try dropping the mapping (making sure it will not re-instate on reboot) and reboot to clear it.
(notice how absolutely no-one else is reporting this, BTW. Tends to suggest it;s something on your side...)
Or, somehow your drive mappings sometimes point to one level deeper (though I can't think how - but that would be a Windows issue anyway. If you use a UNC path as Destination, you can prevent (rule out) that aspect at least. Simply substitute the
\\SERVER\SHARE
that S: is mapped to (instead of 'S:') in the Destination string.
Note that using mapped drives and UNC paths (at the same time) can lead to conflicts (especially if you try to use different credentials for each, which is generally not possible). If you get anomalies, try dropping the mapping (making sure it will not re-instate on reboot) and reboot to clear it.
(notice how absolutely no-one else is reporting this, BTW. Tends to suggest it;s something on your side...)