[Discussion] Connection mechanism for Rsync (and others) - TOS7

[Gremlin]

While looking into an Rsync failure, I wondered why the connection mechanism in TOS7 demands (apparently)
the use of an IP address. In previous versions a network-share id was quite sufficient. In my use-case I do not apply fixed ip
addresses to desktop (windows) devices but they do have network shares available for certain scenarios. This works well enough for me.
However, since the dhcp IP address is not guaranteed in this scenario is seems that TOS7 is unnecessarily interfering with my methods
of working.

Similar applies for (eg) the mounting of remote folders.

An explanation would be appreciated - or am I missing something

[CursaYang]

When performing RSYNC backups in TOS 567, it is required to connect to the destination RSYNC backup server via IP. What early version are you referring to? For most customers, connecting via IP remains a relatively fast method.

[Gremlin]

Take a look at Latest TOS6 versions which use a network share id (at least in SMB) and other discussions that have taken place in this regard.
viewtopic.php?t=9976
Although this discussion is TOS7 (in title) it is really about the change in methodology between 6 and 7.
While discussing Rsync my be something of a red herring, it all relates to the way in which connections are initiated. More specific perhaps might be mounting of remote folders.

[CursaYang]

The customer encountered an issue where the source path was unavailable when mounting a remote folder; this is an SMB protocol compatibility problem. We are currently discussing further solutions internally.