1

I have a friend who works from home. He produces files that he needs to upload to the company's server. He uses a Cisco AnyConnect VPN to connect, and then drags/drops the files to the server. To reduce transfer time, he typically compresses them with ZIP. People complain that they cannot open the files because they are corrupt.

I had him create a test file by ZIPping some random files. The test file was about 2MB. I had him transfer the file to the server and then transfer it back. The file transferred back did not match the transferred file. Looking at both files, they have the exact same number of bytes and match for the first 700KB or so. After that, chunks of the file differ. The data hasn't been replaced by zeroes or subtly corrupted -- in the chunks that differ, the data in the server-side file is just completely different.

His machine is a Mac. The server is Linux. He drags/drops the files to transfer them. They're just ZIP files, so I don't think it's a resource fork issue.

This used to work, but it's not exactly clear when it started not working, so it's hard to track down what might have changed. Any ideas for possible avenues to pursue?

3
  • Can you use other protocols? Does SFTP successfully transfer the file, or does the stream corrupt part way and terminate the connection? Dec 23, 2011 at 22:24
  • Other protocols work fine. His temporary workaround is emailing the files to someone else (from that same machine) and having them put the files on the server. But unfortunately, to keep his workflow sane, he needs to be able to drag&drop files. Dec 23, 2011 at 22:26
  • I'm not sure if email runs over the VPN, though. If not, can you test another protocol that runs over the VPN? Dec 24, 2011 at 18:50

0

You must log in to answer this question.

Browse other questions tagged .