File integrity check software: windows - unix

andy7789 used Ask the Experts™
Hi x-perts,

I need to compare Md5 sum on a local PC (windows) and a remote server (Centos). Are there any applications for that? I just don't want to check it and compare manually file-by-file

Please advise
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Most Valuable Expert 2015




I've done this and it works well to guarantee a good file transfer.
Top Expert 2010
Hi, you can use "rsync", in test mode (--dry-run), to build a list of the files that have differing MD5 checksums, or are missing, between a local and remote directory. It will also recurse into sub-directories, unless you tell it otherwise.

It a Unix tool, for which there are Windows ports, but personally I prefer running the unix version, under Cygwin, on Windows.


Thank you, but it is not exactly what i was asking. I have no problems to find MD5 sums on each of the remote PCs, but I am looking for an application which:

1) Logs to a remote Unix server from Windows local desktop via FTP or SFTP
2) Gets and compares MD5 values on remote and local machines, either in a batch mode or per single file.

it would save a lot of time, because now I am doing it manually.

I have found WS_FTP can verify MD5 etc check sums during uploading, but I cannot test check sums separatelly.

Any suggestions?

11/26 Forrester Webinar: Savings for Enterprise

How can your organization benefit from savings just by replacing your legacy backup solutions with Acronis' #CyberProtection? Join Forrester's Joe Branca and Ryan Davis from Acronis live as they explain how you can too.

Top Expert 2010

Per my last post rsync, in test mode will do this. Producing a list of the files that are different between the remote host and the local.
Top Expert 2010

For info / From (

-n, --dry-run
This makes rsync perform a trial run that doesn't make any changes (and produces mostly the same output as a real run). It is most commonly used in combination with the -v, --verbose and/or -i, --itemize-changes options to see what an rsync command is going to do before one actually runs it.


-c, --checksum
This changes the way rsync checks if the files have been changed and are in need of a transfer. Without this option, rsync uses a "quick check" that (by default) checks if each file's size and time of last modification match between the sender and receiver. This option changes this to compare a 128-bit checksum for each file that has a matching size. Generating the checksums means that both sides will expend a lot of disk I/O reading all the data in the files in the transfer (and this is prior to any reading that will be done to transfer changed files), so this can slow things down significantly.
The sending side generates its checksums while it is doing the file-system scan that builds the list of the available files. The receiver generates its checksums when it is scanning for changed files, and will checksum any file that has the same size as the corresponding sender's file: files with either a changed size or a changed checksum are selected for transfer.

Note that rsync always verifies that each transferred file was correctly reconstructed on the receiving side by checking a whole-file checksum that is generated as the file is transferred, but that automatic after-the-transfer verification has nothing to do with this option's before-the-transfer "Does this file need to be updated?" check.

For protocol 30 and beyond (first supported in 3.0.0), the checksum used is MD5. For older protocols, the checksum used is MD4.
Top Expert 2010


-I, --ignore-times
Normally rsync will skip any files that are already the same size and have the same modification timestamp. This option turns off this "quick check" behavior, causing all files to be updated.

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial