It's a request to modify file timestamp. WinSCP does that to update the remote file to match that of source local file. Otherwise the file will have timestamp of the upload.
If you do not need that, you can turn this off using
put -nopreservetime ...
I have let the FTP site know of this.
But, thanks for the suggestion to turn it off. I will consider to put it in the script. So in doing this, the 450 error (or the timeout detected) will not be there anymore? And btw, I did change the timeout to 45 secs.
Thanks for your help Martin.
I have communicated and got response from our FTP provider. Here is what they are saying:
We have looked at your logfiles, and there appear to be 2 separate issues you brought up
• The MFMT requests failing. Our server does not honor file date/time modification requests. The reason is because of how our virtual filesystem is implemented. We update date/time stamps when a file is uploaded. So when you see this
> 2015-01-27 18:32:16.267 MFMT 20150127182335 ****.bak
< 2015-01-27 18:32:16.455 450 Could not perform action on file ****.bak.
That means that our server understood the MFMT request, but it is just not honoring it. That shouldn't pose a problem, and is unrelated to the timeouts.
• The general timeout issue you raised. I am going to attach our FTP connectivity troubleshooting guide. There is something in your logfile that definitely indicates a firewall issue:
2015-01-27 18:23:42.650 TLS connection established
2015-01-27 18:31:44.330 Timeout detected.
This likely means after the initial handshake, the FTP client tried to open a new port for data transfer, and it failed. The attached will give you some useful things to try.
We recommend that you try the following things in order and see if any of them resolve your issue.
1. Change active vs. passive mode. FTP clients and libraries have two modes of operation: Active mode and Passive mode. If the default doesn't work for you, try the other mode. As you try the other suggestions below, make sure to try each suggestion under both Active and Passive mode. Different firewalls work with different modes.
2. Try SSL. If you aren't using SSL, try switching to FTP-over-SSL on port 990 (implicit) or port 21 (explicit). In many cases, using SSL will get around any firewall blocking.
3. Try alternate ports. BrickFTP offers port 3021 as an alternate port for FTP. Often times, simply using port 3021 will allow your connection to work through your firewall.
Please let me know your thoughts.