Could you also post screenshots of the expanded “Folders” panels on both the ReadyNas and Windows 10 machines?
According to the ReadyNAS, the Windows 10 machine is using a Syncthing relay so local discovery didn’t work for some reason. Is the Windows 10 device on a wireless connection while the ReadyNAS is wired? Is the Windows 10 or ReadyNAS got a firewall enabled?
Is the Windows 10 device on a wireless connection while the ReadyNAS is wired?
No, they’re both wired. Plugged in to a simple 8-port switch.
Is the Windows 10 or ReadyNAS got a firewall enabled?
Win10 does for sure, and I assume ReadyNAS does as well. But I’m thinking that shouldn’t make a difference, since these are both outgoing connections. For example, Win10 to my Android phone (on WiFi) works just fine.
I’ve tried removing both devices from each other’s config and re-adding them, but they still fail to see each other.
That’s great. Best way to start because it keeps the network configuration simple.
Technically speaking, software such as Syncthing that provide a network service requires the ability to receive inbound connections (Syncthing is both a server and a client).
So to work around requiring users to punch holes in their firewall(s), a NAT traversal technique is used where two peers – e.g., your ReadyNAS and Windows 10 machine – first connect to an internet accessible server. The internet server then helps the two peers exchange their respective public IP addresses (as provided by the ISPs).
At least one issue I see is that for the “ReadyNAS” folder, its folder ID is “default” and it’s being shared with device C52893-F. However, in the screenshots from device C52893-F, there’s no matching folder ID. There’s only device fvaw5-4pis6 and 9c57d-fnstx. In order to sync a folder, its folder ID must match on every peer device.
