Please read documentation first.

I have the exact same problem as the previous posters in this thread, except now it's 2005 and I'm using version 3.7.5 (Build 294). It was also happening in 3.7.4.

Remote file time stamps are shown to be one hour later than they actually are. In my case, I can't "just use SFTP" because it is not available on the server I need to upload files to, SCP is the only option.

This is a really painful problem because it's not just the display that's wrong. It also makes it impossible to "keep remote directory up to date," a feature I have come to rely upon heavily (using other servers which have SFTP). Locally edited files are not 'eligible' for update until an hour after they've been edited (when their timestamp finally becomes newer than the incorrect remote timestamp).

Thanks for your attention,
Cameron

I'm using WinSCP 3.7.1 (Build 257), using either of the two interfaces. Files which I have transferred to one particular remote server are displayed on the remote side one hour too far forward, so that a file which should say 15:00 is displayed as 16:00.

For the same server, this problem does not occur
(a) when listing files using WinSCP's terminal
(b) when using SSH Secure Shell Client
(c) when using SSH Secure Shell File Transfer client.

Further, although it consistently happens when using WinSCP on this one particular server, I have not noticed the problem when using WinSCP on other servers. Indeed, I can access the *same* remote filestore with WinSCP using a different server, and the time displays correctly!

Yes, that's solved it for me, too. Thanks!

martin wrote:

Either or there is problem with SCP protocol. Try SFTP. Why do you prefere SCP?

I had similar problems as Anton. Choosing SFTP solved it, so thanks for the hint!

--
Z

Anton P. wrote:

Perhaps the bad server hasn't got its DST configuration set correctly...?

Either or there is problem with SCP protocol. Try SFTP. Why do you prefere SCP?

What protocol? SCP or SFTP?

With the problematic server, it's SCP (my preferred protocol). With the `good' server which also maps my filestore, it's SFTP with SCP Fallback. I seem to remember that when I set up my profile for this good server, it didn't then support SCP.

What is your setting of "Daylight saving time" option (Environment tab)

With both servers, it's "Server adjusts DST".

"Server timezone offset" (SCP tab)?

With both servers, it's 0hrs 0mins.

Perhaps the bad server hasn't got its DST configuration set correctly...?

What protocol? SCP or SFTP? What is your setting of "Daylight saving time" option (Environment tab) and "Server timezone offset" (SCP tab)?

I'm using WinSCP 3.7.1 (Build 257), using either of the two interfaces. Files which I have transferred to one particular remote server are displayed on the remote side one hour too far forward, so that a file which should say 15:00 is displayed as 16:00.

For the same server, this problem does not occur
(a) when listing files using WinSCP's terminal
(b) when using SSH Secure Shell Client
(c) when using SSH Secure Shell File Transfer client.

Further, although it consistently happens when using WinSCP on this one particular server, I have not noticed the problem when using WinSCP on other servers. Indeed, I can access the *same* remote filestore with WinSCP using a different server, and the time displays correctly!

I can supply further details if required.

Cheers,
Anton