Win32 Btsync Doesnt Reconnect Over Vpn After Vpn Reconnected

[psla]

I have a windows btSync client syncing over a VPN to a linux btsync client.

 

When i start my windows box the vpn is not connected but btsync is started automatically.

 

If i don't login to my vpn, btsync says its lost connection to peer, which is fine, but then i connect up the vpn, so i have access to the server again, but win32 btsync does not reconnect. I left for hours, but it never connected to peer until i restarted win32 btsync client.

 

note: on both btsync clients, I have turned off relay server, tracker server, search lan and search DHT, but i have turned on "use predefined hosts" and have added the host to the list (192.168.5.60:8888)

 

here is the log file on win32 btsync client before connection of vpn

 

[2014-08-01 15:56:06] ping 192.168.5.20:32982

[2014-08-01 15:56:06] Failed to open tunnel to 192.168.5.60:49575:TCP

[2014-08-01 15:56:06] Failed to open tunnel to 192.168.5.20:32982:TCP

[2014-08-01 15:56:07] Lost peer for folder \\?\C:\Users\Mathew\Documents

[2014-08-01 15:56:07] Lost peer for folder \\?\C:\Users\Mathew\Documents

 

 

here is log after connection of vpn

[2014-08-01 15:59:08] Send ping to peer (0000000000000000000000000000000000000000) for 

[2014-08-01 15:59:08] ping 192.168.5.60:8888

[2014-08-01 15:59:09] Send ping to peer (0000000000000000000000000000000000000000) for 

[2014-08-01 15:59:09] ping 192.168.5.60:8888

[2014-08-01 15:59:10] Send ping to peer (0000000000000000000000000000000000000000) for 

[2014-08-01 15:59:10] ping 192.168.5.60:8888

[2014-08-01 15:59:11] Send ping to peer (0000000000000000000000000000000000000000) for 

[2014-08-01 15:59:11] ping 192.168.5.60:8888

[2014-08-01 15:59:12] Send ping to peer (0000000000000000000000000000000000000000) for 

[2014-08-01 15:59:12] ping 192.168.5.60:8888

[2014-08-01 15:59:13] Send ping to peer (0000000000000000000000000000000000000000) for 

[2014-08-01 15:59:13] ping 192.168.5.60:8888

 

 

then if i restart win32 btsync

 

[2014-08-01 16:12:41] Got ping (broadcast: 0) from peer 192.168.5.20:32982 (100F6E6A88A15EFCB11BF701357995E92563CE85) for share 

[2014-08-01 16:12:41] Incoming connection from 192.168.5.20:32982

[2014-08-01 16:12:41] Incoming connection from 192.168.5.20:2098

[2014-08-01 16:12:41] Got tunnel to 192.168.5.20:32982:TCP, total tunnels: 1

[2014-08-01 16:12:41] Best tunnel now is 192.168.5.20:32982:TCP

[2014-08-01 16:12:41] Found peer for folder \\?\C:\Users\Mathew\Documents\Market Analyst 7 100F6E6A88A15EFCB11BF701357995E92563CE85 192.168.5.20:32982 direct:1 transport:1

[2014-08-01 16:12:41] Failed to open tunnel to 192.168.5.60:49575:TCP

 

but it does sync the files from this point on.

 

[Helen]

psla,

 

What is the actual IP and listening port of your Linux? You tell your win to connect to 192.168.5.60:8888 (please, note that 8888 - is not the listening port of Sync, it's the WebUI port), and it fails, because it seems to be not the linux node: 
 

here is the log file on win32 btsync client before connection of vpn

 

[2014-08-01 15:56:06] ping 192.168.5.20:32982

[2014-08-01 15:56:06] Failed to open tunnel to 192.168.5.60:49575:TCP

[2014-08-01 15:56:06] Failed to open tunnel to 192.168.5.20:32982:TCP

[2014-08-01 15:56:07] Lost peer for folder \\?\C:\Users\Mathew\Documents

[2014-08-01 15:56:07] Lost peer for folder \\?\C:\Users\Mathew\Documents

here it sends pings to all nodes in the network (these are sent during first 10 seconds after Sync is loaded), including 192.168.5.20:32982. Fails. 

 

here is log after connection of vpn

[2014-08-01 15:59:08] Send ping to peer (0000000000000000000000000000000000000000) for 

[2014-08-01 15:59:08] ping 192.168.5.60:8888

when network is available, it pings the wrong IP:port. again - fails. 

 

 

Ithen if i restart win32 btsync

 

[2014-08-01 16:12:41] Got ping (broadcast: 0) from peer 192.168.5.20:32982 (100F6E6A88A15EFCB11BF701357995E92563CE85) for share 

[2014-08-01 16:12:41] Incoming connection from 192.168.5.20:32982

[2014-08-01 16:12:41] Incoming connection from 192.168.5.20:2098

[2014-08-01 16:12:41] Got tunnel to 192.168.5.20:32982:TCP, total tunnels: 1

[2014-08-01 16:12:41] Best tunnel now is 192.168.5.20:32982:TCP

[2014-08-01 16:12:41] Found peer for folder \\?\C:\Users\Mathew\Documents\Market Analyst 7 100F6E6A88A15EFCB11BF701357995E92563CE85 192.168.5.20:32982 direct:1 transport:1

[2014-08-01 16:12:41] Failed to open tunnel to 192.168.5.60:49575:TCP

now when the network is available and Sync is reloaded, it will again send pings (again those 10 seconds) to all nodes and discover Linux (I suppose it's Linux) on192.168.5.20:32982 address. 

 

So, in predefined hosts on win32, please, put 192.168.5.20:32982, or please, recheck the correct  IP and listening port of your Linux peer. Listening port can be found in Sync settings. Port 8888 that you used is not the one you need to "predefine".