tpeland wrote:

Nowadays SFTP is the default for Winscp. With SFTP the server time is always in UTC timezone so the default "Adjust remote timestamp to local conventions (unix)" seems a bit odd with it's summertime changes. Wouldn't "Preserve remote timestamp (unix)" be better default?

That's just matter of preference. As mentioned in the doc with option you propose, synchronization functions would not work. That's the reason for the default.

martin wrote:

Please read documentation. If that does not help, come back.

I admit I had not read that.

Nowadays SFTP is the default for Winscp. With SFTP the server time is always in UTC timezone so the default "Adjust remote timestamp to local conventions (unix)" seems a bit odd with it's summertime changes. Wouldn't "Preserve remote timestamp (unix)" be better default?

Please read documentation. If that does not help, come back.

While running winscp the fact that Windows thinks it is summertime or not affects the filetimes that are shown for remote files in winscp.

In server: (local)filetime 12:00
Winscp 3.7.6 - 4.1.6 & Windows in summertime: 13:00
Winscp 3.7.6 - 4.1.6 & Windows in wintertime: 12:00
Winscp 3.7.4 - 3.7.5 & Windows in summertime: 12:00
Winscp 3.7.4 - 3.7.5 & Windows in wintertime: 11:00

Problem was tested in both XP and Vista. Windows timezone used was "(GMT+2) Helsinki,...".

Both scp and sftp are affected. When copying files to remote server winscp tries to keep the modification time. The shown value is the same but the real value in the server is affected by this one hour problem. That makes determining "newest files" problematic when part of the transfers are not done with winscp.