Connected device Addresses set on "dynamic" for local sync almost never works

I have a connection between a Windows Server 2019 laptop acting as the backup machine connected on the ethernet, and a Windows 10 machine that uses the WiFi network. Both machines are on the latest versions on SyncTrayzor and Windows updates.

The connections seem to not be able to find the device in the local network, they will often go through a relay if the option is enabled. Setting the address from dynamic to the statically assigned ones on the devices works pretty much 100%, but it is not an option since if the W10 machine switches from WiFi to ethernet, the IP changes, whilst using a relay destroys the purpose of having a local-only syncing.

In “dynamic” mode, the program yells about “NAT type: Port restricted NAT” and refuses to connect locally.

Enabled settings: Enable NAT traversal, Local Discovery - Updated: now only Local Discovery is on with the static addresses

Version on all devices: 1.20.3

This sounds like a problem with your network configuration. You should probably look up “port restricted NAT”.

However, if hard-coding IP addresses works, then you could probably try to hard-code hostnames (aka computer names in Windows), e.g. instead of hard-coding tcp:// use tcp://hostname, etc.

Which is the host name exactly? Just the system’s name? The one found in Settings > About > System ?

It isn’t yelling about the port restricted NAT, it’s just providing info that NAT traversal/STUN discovered about your NAT. That is relevant for getting direct connections over the internet, but not within your LAN.

Typically local discovery between LAN and wifi fails because either the subnets are segregated or the router doesn’t propogate broadcast messages from one to the other. If that’s not the case, then device firewalls also often get in the way.

1 Like

Yes, that’s the one. For example, if your computer name is “desktop-pc”, then you could connect to it using tcp://desktop-pc.

That might be better than static IPs then

But why does it sometimes work? If its a setting problem on the router or firewall, then shouldnt it always have an issue connecting? That also doesnt explain why if its set to the static ip given to the device, or by the name of the computer- it always works…

It does - I was talking about discovery. Anyway I gave you pointers what to investigate, you are free to do that or not, and go with the static device name option instead.

Fair enough, thanks

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.