Harold Feit

Relay servers. You're probably dealing with a case where one or more of your nodes cannot accept incoming connections normally.

There is no "DHT server". The D in DHT stands for Distributed. DHT nodes are run by basically everyone that uses DHT in sync. Neither the tracker nor any node in the DHT actually knows what files you have stored in the secrets. They ONLY have the secret's identifier code and a list of IP+port combinations running on the identifier.

Tracker communication, DHT, searching LAN, predefined hosts.

That's for Linux, not MacOS.

Secrets must be created and stored on a system running bittorrent sync. Not on servers run by BitTorrent inc.

You currently don't. All systems would need the secrets updated manually.

Did you actually replace the binary with the updated version yourself?

Your mac pro's timezone data may not have the correct daylight savings adjustments in it.

One of the two linux versions for x86 anx x64 are for older glibc versions (the ones flagged for glibc 2.3). Figure out what architecture you're running on using uname -a and try the regular version for that architecture.

uname -a shows what in that interface?

You have been warned multiple times by moderation and administration members. Drop it.

Using what specific versions of sync on what devices?

stanha: A suggestion to try: change the timezone on all your computers to GMT. It could be that one of your computers (more likely the mac) has incorrect daylight savings information in its operating system core. http://en.wikipedia.org/wiki/Energy_Policy_Act_of_2005#Change_to_daylight_saving_time

It's worth trying the other x86-64 version for linux, depending on what glibc version they have on it.

uname -a from the console of the nas?

Perhaps, but if you have more than 50 devices on a given secret, it's likely that you will end up with an interconnected blob of peers that will still be able to maintain sync beyond the 50 connection per node limit in much the same way that normal bittorrent clients do.

The current version as of this post can be found at http://forum.bittorrent.com/topic/28241-latest-1292-build/ If you installed sync on your nas via a package, you may need to check with the package provider for how to update to the current version.

Try with the DPI settings turned down on the problem screen then.

That's actually an artifact of the translation your system selected to use. You can probably use the tab key to navigate to the "I agree to the terms" checkbox and press the spacebar to select it and that would enable the "Next" button.

High resolution display isn't the same as high dpi display. Also, your screenshot is extremely low resolution and loses a lot of the detail we would need for troubleshooting.

In your case I would simply recommend pausing the sync on that machine and doing a copy-and-paste of the remaining files. Deleting files in a synced folder while a sync is in progress may cause unintended data loss.

segmented sha1 validation.

What version of sync are you using? Have you checked for .!sync temp files?

Which specific linux variant of sync did you use? The WD MyBook Live and WD My Cloud devices are Linux PowerPC

Synchronization is real time on all platforms other than Mac. On Mac, synchronization happens on 10 minute cycles. If your files are locked open by a program, they will be unable to be synched. Restarting of the sync client should not be needed to get it to work.