I built three Pi Model 2 configurations, each with a USB hard drive partitioned into two, and running SAMBA and syncthing. The set-up is such that each site has a partition to use as a server, of which a copy is maintained off-site.
I built and tested them on my local network, using fixed IP addresses for simplicity when running rsh to modify config files. It eventually worked a treat! Let us call the three systems A, B & C.
I had no chance to perform local off-site tests, so took a long gamble and shipped B to its owner, where it works a treat, and was checkable by viewing the syncthing web page at both ends, as B’s server partition is backed-up onto A, which remained here.
Encouraged by this, I posted C off to its owner. No luck: he has altered the default allocation of IP addresses; I failed to foresee this one, and had not reverted the IP address management to dhcp. I was just lucky with B.
I talked the new owner - a good friend, fortunately! - through adjusting the config to suit. SAMBA now works a treat.
However, syncthing, whilst running there, does not show up in a browser window there, neither does it show any sign of activity here, which is where C’s partition would be backed-up.
I am at a loss to understand this, and can presently see no alternative but to visit him and see if I can characterise the problem on site. It is time we socialised, but I’d be glad of things to check for when I get there!
Any ideas, please, good people?
And thank you for reading this rather long story!
Ben
P.S. I know what will happen - the minute I post this, the answer will appear in my head! Maybe…