mikedr

Members
  • Content Count

    17
  • Joined

  • Last visited

About mikedr

  • Rank
    Member
  1. I am having this exact same issue with Mac. Running Mac Sierra 10.12.6. Now do I get the new version -- and why can't I just automatically download it?
  2. Interestingly, I've yet to get sync'ing to work with my DS214 . . . if memory serves in working with support, I thought it was a limitation of the Synology architecture? I'm running 2.4-1 . . . It appears the latest version is 2.4.2-1. Will that fix the issue?
  3. When you just leave them on and use the remote, I assume the Macs are awake and remain in a logged-in state? That is, when you say that you've "got to log into them," does this mean you just have to use the Macs via keyboard/mouse, or that you first have to enter in a password via a log-in screen? If you *don't* have to enter in a password via a log-in screen, then the issue is something having to do with the listening port and things not getting forwarded properly from the router. UPNP *should* work (does your router let you see what UPNP reservations have been made?), but worst case is you could set up port forwarding and make sure the Macs are on a static IP.
  4. I had this problem, which support walked me through. When connecting back to Ethernet from Wi Fi, disable Wi Fi. The wrong IP address is being pushed to your router.
  5. I'm wondering if anyone else is experiencing this issue. I have an ongoing open ticket with tech support, but I don't believe tech support is based in the US -- I only get replies overnight, which means that getting anything even looked at is a multiple-day process (I send an email during business hours, get a reply overnight, and then reply the next day). We have two Macs remote from one another, both running Yosemite, and one Synology that is local to one of the Macs. All are running 2.4 (sadly, I so wish I hadn't upgraded from the last version of 1.X, which was rock solid stable). The remote Mac will go to sleep on and off during the day (it's a laptop for a remote worker). When it is waked up and reconnects to the Internet, sometimes it won't show as being connected to the other Mac, and other times it won't show as being connected to the Synology. To get it to show, I have to stop and restart the Synology Resilio program, or quit and relaunch Resilio on the other Mac. Whatever process Resilio is using so peers can discover one another is clearly broken. And tech support . . . is there any way that you could work business hours in the US? Maybe for us paid users?
  6. I upgraded our DS214 from DSM5.2 to DSM6 over the weekend. Was running a very old version of BTSync that was bullet proof. I decided to start from scratch after upgrading v2.3.8 (sadly, the old version didn't work with DSM6) -- creating new folders, and waiting for the initial sync to occur. Now, syncing is unreliable to the point that I pulled the DS214 from the production environment, and am considering ditching the DS214 and/or BTSync (although I'm a paid business customer of the latter). (1) With one folder, syncing is only one way even though read/write has been checked (that is, everything is configured appropriately). Anything changing on the NAS doesn't get pushed to the other clients until a reindexing occurs. There is no system notification of immediate changes, in other words. (2) With the other folder -- 2 Mac clients and the NAS -- very strange things happen. Files deleted on a Mac client will reappear. Sometimes files will disappear. Obviously, for a production environment, this is totally unacceptable. If I pull the DS214 from the environment, everything works flawlessly. In my estimation, it appears that v.2.38 for Synology is very unreliable on DSM6. If others come across this thread, all I can say is beware -- it's not ready for prime-time.
  7. (bump) Having this exact same problem. Any changes to the DS214 do not make their way to other clients until a rescan occurs, which is unacceptable. I think it's a bug with the latest version of BTSync.
  8. Ahhh, very good. I just removed those things from the StreamList /white list and all appears well.
  9. Basically, previously files were being ignored, but now they're not. Here's my ignore list on both my computer and the computer I'm syncing with. # .SyncIgnore is a UTF-8 encoded .txt file that helps you specify single files, paths and rules # for ignoring during the synchronization job. It supports "?" and "*" wildcard symbols.### OS generated files #.DS_Store.DS_Store?._*.Spotlight-V100.Trashes*.FinderInfoehthumbs.dbdesktop.iniThumbs.dbIcon*.ResourceForkcom.apple.ResourceFork.ResourceFork.FinderInfocom.apple.FinderInfo.com.apple.ResourceFork.com.apple.FinderInfo*.apple.ResourceFork.apple.ResourceFork*com.apple.ResourceFork*.ResourceFork*.FinderInfo*com.apple.FinderInfo*.com.apple.ResourceFork*.com.apple.FinderInfo*.apple.ResourceFork@eaDir_gsdata_And yet, files matching these names are still being synced! See attached as a snippet. How do I fix this? I should note when I upgraded, BT Sync simply renamed .SyncIgnore as IgnoreList . . . .
  10. Very interesting! When's the ETA for 1.4 on both Mac and Synology?
  11. There's also sadly little information available on the Synology forums. I'm hoping that once BTSync becomes an official package on Synology, this will change.
  12. My application is similar to, but on a much smaller scale, than poemtree's. I am a solo attorney that uses a Mac. Half the year I'm in Az, the other half in Wa. My paralegal is in Minnesota, also on a Mac. Setting up central file server at my location, even with my relatively speedy 100/20 Internet (and her 80/15), just was god awful slow, even for small Word documents (directory refreshing seemed to be the big problem actually). Now, we each keep a local version of the files, and they're synced back and forth instantly. We never work on the same file, so that's not an issue. I migrated to BT Sync after pulling my hair out with GoodSync. GS worked well enough, but we started getting HTTP timeout errors that caused a complete re-sync, multiple times a day each workday, which was intolerable. We have had no such issues with BTSync, although bandwidth usage seems to be a bit higher than with GS.
  13. For what it's worth, I have had the same problem, on a ds214, to the extent that I just uninstalled BT Sync. The problem I was having was like yours, and also that BTSync wasn't listening to the ignore file list (even after removing the relevant folders on both Mac and the Synology, updating the ignore list, and then readding), which was causing hanging on various "ResourceFork" type files.
  14. That's great! Thus far, I've been pleased with BT Sync. It replaced a commercial solution that was getting buggy. The implementation of BT Sync on my Synology box seems to be slow, but I'm slogging through that part.
  15. I have four computers that are syncing the same folder, at three locations. I'm somewhat familiar with BT technology. Therefore, I'm wondering how syncing works in practice. I just added a new computer, computer 1 at location 1 we'll call it, and it has to sync around 100 gb of data. My question is, where does it "get" the files from? There is computer 2 at location 2, and computers 3 and 4 at location 3. Computers 2, 3, and 4 are all already synced. Does computer 1 get pieces of files from all of computers 2, 3, and 4 to make things faster? That is, as I add more computers to the sync, does the initial sync typically go faster for the new computers? Most of these computers are on 100/20 Internet connections, so a new computer can download at up to 100 mbps, but no other computer can upload faster than 20 mbps. In theory, if a newly added computer can get pieces of files from five other computers, say, then it can fully realize its 100 mbps connection to get up to sync.