I tried it, but not working for me:
/tool fetch address=“ip address” src-path=“2022-06-07.backup” user=“user” mode=ftp password=“password” dst-path=“/2022-06-07.backup” upload=yes port=2121
Is windows FTP server in your LAN or WAN? If WAN, then it may be necessary to use passive FTP due to some firewall on the way (use of non-standard port 2121 does indicate such device is in the way) … which doesn’t seem to be supported by fetch tool in ROS.
But /tool fetch mode=ftp doesn’t seem to support passive FTP … so you may have to start using another file transfer protocol (such as sftp) or configure a tunnel between your router and network where FTP server resides (to make connection transparent). Note that FTPS (FTP over SSL, supported by MS) is very much different than SFTP (file transfer over SSH).
BTW, use of plain FTP protocol over WAN is not a wise idea since it doesn’t offer any encryption and is hence susceptible to snooping (both passwords and file contents).
If your try to upload a file to a FTP server and the file do already exist (on the FTP server), you will get an error if user do not have delete access.
Well, documentation doesn’t offer selecting passive or active mode. So your observation indicates that it either works in passive mode only or thst it tries to select correct mode automatically.
Active mode is relict from the past, nothing made in this century should default to it. Fetch tool uses passive by default (or perhaps only, I’m too lazy to test it; but if I should guess, I’d expect there is fallback) and that’s good.
As for OP’s problem, there must be some difference between TC and ROS. Maybe different source address and some filtering on that? Do some debugging, logging rules, packet sniffer, if it happens all the time, it should be easy to find.