Andy+

Members
  • Posts

    581
  • Joined

  • Last visited

Posts posted by Andy+

  1. As follows :

    Just to clear things up - I guess/hope you mean that you want to get rid of the ports BitTorrent Sync is currently using and bring in new ports that your company supports?! Right?

    Yes, because if only ports 80 and 443 are used, other ports are not possible to use, this only is possible, if the ports are considered in a firewall.

    Companies usually have smarter firewalls that detect what kind of protocol it is and block it then (BitTorrent protocol in our case) it won't bring you much if it is a SSL connection. Also BitTorrent Sync is based on the BitTorrent protocol which is.. well it's own protocol.

    Thats true. And because of I visit much companys during my activities sometimes it seems that your part of name - sorry for this - "torrent" it seems very sensible, I don´t know why. I think it´s because of the torrent downloads in the Internet. E.g. in the company I visit today, the website http://www.bittorrent.com or http://forum.bittorrent.com is blocked because is registered as "peer to peer". Now your new http://forum.getsync.com in this case is no problem.

    BUT. What you can do to still use BitTorrent Sync in a company environment: You can set a proxy,if it is allowed by policies, Firewall etc or you can VPN out of the guest network if you want and then be able to establish a connection to your peers.

    That with the proxy settings is correct of course I have already tested. But alone with this feature unfortunately I can not connect. When I try to remove the hook at port, this is not possible. I can try another port no. but again no port 80.

  2. To work in company environments there is no solution implemented to work without ports. Because in the most of companys only the ports 80 and 443 are open, as visitor there is no possibility to connect to the own BTsync network, also not over Relay servers.

  3. Normaly this is no problem. Which DS you have? BTW I have a issue with v2.3-1 

    and go back to v2.2.7, which is running perfectly. If you have problems to use the package from Synology package center, you also can try

     

  4. I use the Synology server DS412+, DS1512+, DS712+ (with DSM 6 Beta) and DS414.

    As the new v2.3.0 is coming, I install this version on all servers and my Windows computers. Up to this time I use v2.2.7 and I can only say, it was a perfect running on all devices. Unfortunately the v2.3.0 doesn´t run well. Normally, up to v2.2.7 the client on Windows in a very short time is transfering data to the other devices if any changes happen. But not with v2.3.0 and it becomes clear, that no or only a partly transfer was done, also over hours and days. Also a mixed situation with v2.2.7 and v2.3.0 doesn´t run. Also no difference I have if I use the client as service or "normal". Or new installations are also without success.

    Now I goe back on all devices to v2.2.7 - and - I´m happy as before. All is running smoothly and well. What is the difference in the software or what can I doe in a other way?

  5. In this time I test the Synology DSM 6 Beta 1+2 on a Synology DS712+ and up to Beta 1 I can use the current BTsync. From yesterday the Beta 2 can be load from Synology to install on the DS´s and I load the Version: 6.0-7274 from 21.1.2016.


     


    During installation I get a message, that the current version 2.3.100 of BTsync is not compatible to this and must be delete, if I want to update to Beta 2. I cancel this.


     


    What can I due?


  6. In this time I test the Synology DSM 6 Beta 1+2 on a Synology DS712+ and up to Beta 1 I can use the current BTsync. From yesterday the Beta 2 can be load from Synology to install on the DS´s and I load the Version: 6.0-7274 from 21.1.2016.

     

    During installation I get a message, that the current version 2.3.100 of BTsync is not compatible to this and must be delete, if I want to update to Beta 2. I cancel this.

     

    What can I due?

  7. No, because it´s seperate. Also it´s better, to have no conflicts, to stop the version 1.4. At the end, if 2.2.1 is running it´s not needed the parallel installation. In this moment I also have still there, because before of version 2.2.1 I also use the great 1.4.111-11 version. But I stopped 1.4 so 2.2.1 is running. If you want to use the same folders in both versions, the stop of 1.4 is "must" because the ID is not the same. This is the conflict.

  8. Up to version 2.2 there was a limitation with 10 folders. With the version 2.2.1 for Synology

     

    http://help.getsync.com/customer/portal/articles/1888507-synology

     

    there is no longer a limitation in this case. It means, people which use up to now version 1.4.111, which is the best of Beta, now can use version 2.2.1 with some more functions and updates for future.

     

    Only Sync Private Identity & Linking (PKI) is a good thing, but a Pro feature. Also there are some more good Pro´s, but I think now must´s. Everybody can choose or not. For me all is not required.