ripley

Members
  • Posts

    4
  • Joined

  • Last visited

Everything posted by ripley

  1. Still no luck with this. Anyone have any input?
  2. I have two machines that I am trying to get data to sync between. One machine is my home desktop. The other is a work machine. My home machine has a port opened in the firewall that is externally accessible. My work machine does not as I do not control the firewall. I have verified that the port is accessible from my work machine via telnet. So far I have not been able to get anything to sync. My main goal is to sync a large media folder, about 450GBs, one way to my office. To speed the process I copied the majority of the data manually to the work machine. I took the one way key from my home machine and pointed the sync to the folder on my work machine that has the data in it. Nothing has happened. When I add the folder it spends less then 15 seconds indexing and then lists 0 files despite there being over 25k files. My home machine spent several hours indexing everything. I have tried enabling DHT. I have tried adding my home IP address as a predefined host. Neither works. I enabled debugging, the log on both machines are empty. I tried creating a different folder on my home machine with just 3 small files in it and doing a two way sync with the work machine to an empty folder, same results. The sync.log from the work machine seems like its connecting to trackers: [2014-02-03 11:35:49.095] Got 3 tracker ips[2014-02-03 11:35:49.095] ip 54.225.100.8:3000[2014-02-03 11:35:49.095] ip 54.225.196.38:3000[2014-02-03 11:35:49.095] ip 54.225.92.50:3000[2014-02-03 11:35:50.070] Sending broadcast ping for share 3A67AA81157CAFB6C90313BA160C9BB9E505121F[2014-02-03 11:35:50.070] Requesting peers from tracker 54.225.100.8:3000 via UDP[2014-02-03 11:35:51.072] Sending broadcast ping for share 3A67AA81157CAFB6C90313BA160C9BB9E505121F[2014-02-03 11:35:52.072] Sending broadcast ping for share 3A67AA81157CAFB6C90313BA160C9BB9E505121F[2014-02-03 11:35:53.072] Sending broadcast ping for share 3A67AA81157CAFB6C90313BA160C9BB9E505121F[2014-02-03 11:35:54.072] Sending broadcast ping for share 3A67AA81157CAFB6C90313BA160C9BB9E505121F[2014-02-03 11:35:55.072] Sending broadcast ping for share 3A67AA81157CAFB6C90313BA160C9BB9E505121F[2014-02-03 11:35:56.072] Sending broadcast ping for share 3A67AA81157CAFB6C90313BA160C9BB9E505121F[2014-02-03 11:35:57.072] Sending broadcast ping for share 3A67AA81157CAFB6C90313BA160C9BB9E505121F[2014-02-03 11:35:58.072] Sending broadcast ping for share 3A67AA81157CAFB6C90313BA160C9BB9E505121F[2014-02-03 11:35:59.072] Sending broadcast ping for share 3A67AA81157CAFB6C90313BA160C9BB9E505121F[2014-02-03 11:36:00.072] Sending broadcast ping for share 3A67AA81157CAFB6C90313BA160C9BB9E505121F[2014-02-03 11:36:00.072] Requesting peers from tracker 54.225.100.8:3000 via UDP[2014-02-03 11:36:01.073] Sending broadcast ping for share 3A67AA81157CAFB6C90313BA160C9BB9E505121F[2014-02-03 11:36:02.076] Sending broadcast ping for share 3A67AA81157CAFB6C90313BA160C9BB9E505121F[2014-02-03 11:36:03.076] Sending broadcast ping for share 3A67AA81157CAFB6C90313BA160C9BB9E505121F[2014-02-03 11:36:04.085] Sending broadcast ping for share 3A67AA81157CAFB6C90313BA160C9BB9E505121F[2014-02-03 11:36:05.085] Sending broadcast ping for share 3A67AA81157CAFB6C90313BA160C9BB9E505121F[2014-02-03 11:36:06.085] Sending broadcast ping for share 3A67AA81157CAFB6C90313BA160C9BB9E505121F[2014-02-03 11:36:07.087] Sending broadcast ping for share 3A67AA81157CAFB6C90313BA160C9BB9E505121F[2014-02-03 11:36:08.087] Sending broadcast ping for share 3A67AA81157CAFB6C90313BA160C9BB9E505121F[2014-02-03 11:36:09.079] Sending broadcast ping for share 3A67AA81157CAFB6C90313BA160C9BB9E505121F[2014-02-03 11:36:10.094] Sending broadcast ping for share 3A67AA81157CAFB6C90313BA160C9BB9E505121F[2014-02-03 11:36:10.094] Requesting peers from tracker 54.225.100.8:3000 via UDPAs does my home machine: [2014-02-03 12:10:57.089] Got 3 tracker ips[2014-02-03 12:10:57.089] ip 54.225.100.8:3000[2014-02-03 12:10:57.089] ip 54.225.92.50:3000[2014-02-03 12:10:57.089] ip 54.225.196.38:3000[2014-02-03 12:10:58.092] Sending broadcast ping for share 3A67AA81157CAFB6C90313BA160C9BB9E505121F[2014-02-03 12:10:59.095] Sending broadcast ping for share 3A67AA81157CAFB6C90313BA160C9BB9E505121F[2014-02-03 12:11:00.104] Sending broadcast ping for share 3A67AA81157CAFB6C90313BA160C9BB9E505121F[2014-02-03 12:11:01.109] Sending broadcast ping for share 3A67AA81157CAFB6C90313BA160C9BB9E505121F[2014-02-03 12:11:02.113] Sending broadcast ping for share 3A67AA81157CAFB6C90313BA160C9BB9E505121F[2014-02-03 12:11:03.120] Sending broadcast ping for share 3A67AA81157CAFB6C90313BA160C9BB9E505121F[2014-02-03 12:11:04.124] Sending broadcast ping for share 3A67AA81157CAFB6C90313BA160C9BB9E505121F[2014-02-03 12:11:05.134] Sending broadcast ping for share 3A67AA81157CAFB6C90313BA160C9BB9E505121F[2014-02-03 12:11:06.139] Sending broadcast ping for share 3A67AA81157CAFB6C90313BA160C9BB9E505121F[2014-02-03 12:11:07.142] Sending broadcast ping for share 3A67AA81157CAFB6C90313BA160C9BB9E505121F[2014-02-03 12:11:07.144] Requesting peers from tracker 54.225.100.8:3000 via UDP[2014-02-03 12:11:08.149] Sending broadcast ping for share 3A67AA81157CAFB6C90313BA160C9BB9E505121F[2014-02-03 12:11:09.153] Sending broadcast ping for share 3A67AA81157CAFB6C90313BA160C9BB9E505121F[2014-02-03 12:11:10.165] Sending broadcast ping for share 3A67AA81157CAFB6C90313BA160C9BB9E505121F[2014-02-03 12:11:11.173] Sending broadcast ping for share 3A67AA81157CAFB6C90313BA160C9BB9E505121F[2014-02-03 12:11:12.179] Sending broadcast ping for share 3A67AA81157CAFB6C90313BA160C9BB9E505121F[2014-02-03 12:11:13.185] Sending broadcast ping for share 3A67AA81157CAFB6C90313BA160C9BB9E505121F[2014-02-03 12:11:14.193] Sending broadcast ping for share 3A67AA81157CAFB6C90313BA160C9BB9E505121F[2014-02-03 12:11:15.207] Sending broadcast ping for share 3A67AA81157CAFB6C90313BA160C9BB9E505121F[2014-02-03 12:11:16.216] Sending broadcast ping for share 3A67AA81157CAFB6C90313BA160C9BB9E505121F[2014-02-03 12:11:17.219] Sending broadcast ping for share 3A67AA81157CAFB6C90313BA160C9BB9E505121F[2014-02-03 12:11:17.222] Requesting peers from tracker 54.225.100.8:3000 via UDPI'm at a loss. I don't know what else to try.