Post a reply

Add an Attachment

If you do not want to add an Attachment to your Post, please leave the Fields blank.

(maximum 10 MB; please compress large files; only common media, archive, text and programming file formats are allowed)


Topic review


Re: Local client sees remote file timestamps ahead by 1 hour

Please attach a full log file from the problematic client as well as an equivalent log from other client for comparison.

To generate log file, use /log=path_to_log_file command-line argument. Submit the log with your post as an attachment. Note that passwords and passphrases not stored in the log. You may want to remove other data you consider sensitive though, such as host names, IP addresses, account names or file names (unless they are relevant to the problem). If you do not want to post the log publicly, you can mark the attachment as private.

Local client sees remote file timestamps ahead by 1 hour

Hello. I have several clients using winscp 5.7.2 that pull files from an ubuntu box running proftpd. All of my clients are seeing the correct timestamp of the remote files except for one which sees the remote file timestamps that are exactly 1 hour ahead. All of my clients are using Windows Server 2008R2 and all are on EST with DST enabled. All of my clients use a .cmd file that calls, so they never actually touch the winscp.exe gui. I looked into the winscp.ini file and saw a few values that are "might" be related to timestamps but I wasn't sure as I didn't find any documentation online.

If I want all of the clients to always accept the remote file timestamp, would I need to add this line to my script?
option preservetime

This is the winscp relevant portion of my .cmd script:

echo option batch abort>> batch.bat

echo option confirm on>> batch.bat
echo open sftp://%Username%:%Password%@%FTPAddress%>> batch.bat
echo option transfer binary>> batch.bat
echo lcd %Local% >> batch.bat
echo cd %Remote% >> batch.bat
echo put * >> batch.bat
echo exit>> batch.bat /script=batch.bat /nointeractiveinput