I've found some solutions to my own problems. I have a mix of linux, OS X, and Win 7 here. The biggest problem has been with going from OS X or linux to the windows 7 boxes. However, there have also been problems with OS X to OS X. I'll enumerate the issues and what I did to resolve them. 1. OS X to OS X.... file names were too long. In this case BTS was able to show me in the History tab that these files failed sync. This was on the receiving machine. The solution was to shorten the file names. They were indeed very very long. It's strange that the originating OS X machine had no problem creating the file..... but synching it was a problem. I also wrote script to find and identify the long file names. I shortened them manually. 2. OS X/Linux to Win7.... long file names NTFS is much more restrictive with file name lengths. I had to find long file names/paths and reduce their size. This was a bit of a task as the windows client for BTS didn't give me much indication of which files it was unable to sync. In fact, the windows boxes indicated that they were in sync. Only the OS X and Linux boxes were complaining that there were bytes left to sync. I used the script mentioned in (1) to find long file names and shorten them. 3. OS X/Linux to Win7.... special characters For sure I've had problems with : and \t (tab) in the file names. There were some others that I suspected but can not confirm. I wrote a script to strip out all the problem and suspected characters and rename the files on the originating OS X/Linux side. Once those file names were cleaned up, the sync with Windows completed. If BTS could identify both on the originating client and the recipient client exactly which file were failing due to file names I would be a happy camper!