cz2000

Members
  • Content Count

    13
  • Joined

  • Last visited

Everything posted by cz2000

  1. @RomanZ the following is my nslookup result: Non-authoritative answer: Name: config.usyncapp.com Addresses: 54.225.196.38 54.225.100.8 54.225.92.50 This result appears to be correct, however, 1.3.109 still does not work on my windows 7. BTW, I can use IE to download the file from http://config.usyncapp.com/sync.conf on my disk(This indicates that this link is not blocked by GFW.);In addition, I did icmp ping and tcp ping test for config.usyncapp.com, the result is ok. I really do not understand where is blocked, leading to not communicate in 1.3.109.
  2. @RomanZ All versions do not work after 1.2.92 in China. Currently 1.2.92 version + the correct hosts file are worked and fine in China. Use the same way to 1.3 and 1.4, do not work. Pls help... Thanks @RomanZ I do not know what happened? Is the new version(1.3 or 1.4) uses new ip address or hostname outside 1.2.92?
  3. 1.3 and 1.4 is not to be used in China, now 1.2 version can work in China, can you teach me new test method used to determine what is being blocked by GFW of China, thank you
  4. Currently, I have encountered the same problem with you, do I also need to install DNSCrypt in my windows server? BTW, I am wondering how to do by GFW, it actually can be a priority of my local hosts file, and misled me into 59.24.3.173 [2014-05-07 00:29:49.157] Requesting peers from tracker 59.24.3.173:3000 via UDP [2014-05-07 00:29:49.157] Sending broadcast ping for share [2014-05-07 00:29:49.162] Requesting peers from tracker 59.24.3.173:3000 via UDP [2014-05-07 00:29:49.162] Sending broadcast ping for share [2014-05-07 00:29:49.167] Requesting peers from tracker 59.24.3.173:3000 via UDP [2014-05-07 00:29:49.167] Sending broadcast ping for share [2014-05-07 00:29:49.173] Requesting peers from tracker 59.24.3.173:3000 via UDP [2014-05-07 00:29:49.173] Sending broadcast ping for share [2014-05-07 00:29:49.178] Requesting peers from tracker 59.24.3.173:3000 via UDP [2014-05-07 00:29:49.179] Sending broadcast ping for share [2014-05-07 00:29:49.183] Requesting peers from tracker 59.24.3.173:3000 via UDP [2014-05-07 00:29:49.183] Sending broadcast ping for share [2014-05-07 00:29:49.188] Requesting peers from tracker 59.24.3.173:3000 via UDP
  5. Currently, I have encountered the same problem with you, do I also need to install DNSCrypt in my windows server? BTW, I am wondering how to do by GFW, it actually can be a priority of my local hosts file, and misled me into 59.24.3.173 [2014-05-07 00:29:49.157] Requesting peers from tracker 59.24.3.173:3000 via UDP [2014-05-07 00:29:49.157] Sending broadcast ping for share [2014-05-07 00:29:49.162] Requesting peers from tracker 59.24.3.173:3000 via UDP [2014-05-07 00:29:49.162] Sending broadcast ping for share [2014-05-07 00:29:49.167] Requesting peers from tracker 59.24.3.173:3000 via UDP [2014-05-07 00:29:49.167] Sending broadcast ping for share [2014-05-07 00:29:49.173] Requesting peers from tracker 59.24.3.173:3000 via UDP [2014-05-07 00:29:49.173] Sending broadcast ping for share [2014-05-07 00:29:49.178] Requesting peers from tracker 59.24.3.173:3000 via UDP [2014-05-07 00:29:49.179] Sending broadcast ping for share [2014-05-07 00:29:49.183] Requesting peers from tracker 59.24.3.173:3000 via UDP [2014-05-07 00:29:49.183] Sending broadcast ping for share [2014-05-07 00:29:49.188] Requesting peers from tracker 59.24.3.173:3000 via UDP
  6. Hello, RomanZ It seems to be working now. I need to observe a few days, very grateful !
  7. Hello, RomanZ I can directly get the config file, but still can not find other peer.
  8. Hello, RomanZ China DNS indeed done the dirty action, which I have gotten in the last r.usyncapp.com too, so I've previously resolved the three correct address(54.225.92.50, 54.225.196.38, 54.225.100.8) for config.usyncapp.com, and write into my hosts file, however, the fault persists, and display same error. I suspect this period of ip address (54.225.92.50, 54.225.196.38, 54.225.100.8) has blocked by China GFW. BTW, are you still able to make r.usyncapp.com work in 1.3.XX?
  9. Hello, Admin Chinese users can not access config.usyncapp.com, keep trying, that is not found in any other machine. Version 1.2.92 uses r.usyncapp.com, do not have this problem [2014-04-01 00:49:59] bind port is 21498[2014-04-01 00:51:00] Requesting folder config from config.usyncapp.com[2014-04-01 00:51:30] Requesting folder config from config.usyncapp.com[2014-04-01 00:52:00] Requesting folder config from config.usyncapp.com[2014-04-01 00:52:27] NAT-PMP: Unable to map port with NAT-PMP.[2014-04-01 00:52:30] Requesting folder config from config.usyncapp.com[2014-04-01 00:53:00] Requesting folder config from config.usyncapp.com[2014-04-01 00:53:30] Requesting folder config from config.usyncapp.com[2014-04-01 00:53:48] NAT-PMP: Unable to map port with NAT-PMP.[2014-04-01 00:54:00] Requesting folder config from config.usyncapp.com[2014-04-01 00:54:30] Requesting folder config from config.usyncapp.com[2014-04-01 00:55:00] Requesting folder config from config.usyncapp.com[2014-04-01 00:55:30] Requesting folder config from config.usyncapp.com[2014-04-01 00:56:00] Requesting folder config from config.usyncapp.com[2014-04-01 00:56:30] Requesting folder config from config.usyncapp.com[2014-04-01 00:57:00] Requesting folder config from config.usyncapp.com[2014-04-01 00:57:30] Requesting folder config from config.usyncapp.com[2014-04-01 00:58:00] Requesting folder config from config.usyncapp.com[2014-04-01 00:58:30] Requesting folder config from config.usyncapp.com[2014-04-01 00:59:00] Requesting folder config from config.usyncapp.com[2014-04-01 00:59:30] Requesting folder config from config.usyncapp.com[2014-04-01 00:59:59] SyncFilesController: started periodic scan
  10. I personally think China GFW has been blocked tcp and udp 3000... :\Users\Administrator>telnet 37.61.54.158 3000onnecting To 37.61.54.158...Could not open connection to the host, on port 3000: Connect failed C:\Users\Administrator>telnet 67.215.229.106 3000Connecting To 67.215.229.106...Could not open connection to the host, on port 3000: Connect failed
  11. [2013-12-20 21:31:56.219] Got 1 tracker ips [2013-12-20 21:31:56.219] ip 37.61.54.158:3000 [2013-12-20 21:31:56.219] Got 1 tracker ips [2013-12-20 21:31:56.219] ip 37.61.54.158:3000 [2013-12-20 21:31:56.219] Got 2 relay ips [2013-12-20 21:31:56.219] ip 67.215.229.106:3000 [2013-12-20 21:31:56.219] ip 67.215.231.242:3000 [2013-12-20 21:31:56.244] Got 1 tracker ips [2013-12-20 21:31:56.244] ip 37.61.54.158:3000 [2013-12-20 21:31:56.244] Got 1 tracker ips [2013-12-20 21:31:56.244] ip 37.61.54.158:3000 [2013-12-20 21:31:56.244] Got 1 tracker ips [2013-12-20 21:31:56.244] ip 37.61.54.158:3000
  12. it was working and now it is blocked yes, it was working and now it is blocked in beijing CT and UT Are you already concerned about this post http://forum.bittorrent.com/topic/24852-btsync-blocked-in-china/ I personally think China GFW has been blocked tcp and udp 3000...
  13. BitTorrent Sync has blocked by Beijing Teletron