As I have wrote already, to correct timestamp for SCP protocol you should also set appropriate value for "server timezone offset" on SCP tab.

My "Server timezone offset" is 0 & 0. My "Daylight saving time" is "Server adjusts DST". My colleague was using SFTP, so that was the difference. We verified that the SFTP protocol applies the correct timestamp only when "Server adjusts DST" is chosen, and that the SCP protocol will not apply the correct timestamp regardless of which DST option is chosen.

My colleague using the same WinSCP version does not have the problem, so it may be isolated to me.

Check if you are using the same protocol (SCP/SFTP). Also check value of the two options adjusting the timestamps: "Daylight saving time" on Environment tab of login dialog and "Server timezone offset" on SCP tab.

WinXP, SSH v2, Explorer style. My timezone is set to Central Time with "Automatically adjust clock for daylight saving changes" checked. My local system time is correct and matches appropriately to the local file timestamps. Ditto for the remote Linux system when I SSH in. My colleague using the same WinSCP version does not have the problem, so it may be isolated to me.

I am not really asking for help, just reporting a potential bug that I wondered if others were seeing. I can certainly work around it with the awareness that my client will show an hour off.

Would you mind providing me ANY information about your environment? Have you read How to ask for support?

My client v.3.6.1 (build 221) shows a timestamp on remote files that is one hour later than the actual time on either my local workstation or on the remote system.