# Post a reply

Options

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)

Options

# Topic review

martin

## Re: Synchronize Directories

This bug has been added to the tracker:
https://winscp.net/tracker/1162

I have sent you an email with a development version of WinSCP to address you have used to register on this forum.
jdperry

## Re: Synchronize Directories

Full log was sent.

Thank you,
JD
martin

## Re: Synchronize Directories

Please attach a full session log file showing the problem (using the latest version of WinSCP).

To generate log file, set Session.SessionLogPath. 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 may email it to me. You will find my address (if you log in) in my forum profile. Please include link back to this topic in your email. Also note in this topic that you have emailed the log.
jdperry

## Synchronize Directories

I am attempting to synchronize with a particular folder on a remote SFTP server.

When I run the following:
SynchronizationResult result = session.SynchronizeDirectories(
SynchronizationMode.Local,
@"\\path\to\local",
"/Remote",
false,
false,
SynchronizationCriteria.None,
null);

It consistently downloads/overwrites every single file that is in the remote folder (so 50 files in my case) even though files of the same name already exist. The log seems to suggest that the synchronize sees the files as being "updated". This particular sFTP server suppresses file attributes like file size and modified dates, which is why I am using SynchronizationCriteria.None. When I run the synchronize through the client directly it only downloads the new files that don't exist locally which is the desired behavior.

Am I missing something?

Thanks,
JD