How to force win to establish smb connection only on one of two possible routes?

Question

Computer networks

Given: two machines with a win server with two possible communication paths
1) directly by cable with a subnet of 192.168.99.0/24
2) through a router with a subnet of 172.16.1.0/24
When one machine tries to connect to another via smb at the network address 192.168.99.0 /24 - in fact, a connection is also established on the network 172.16.1.0/24.
Both machines are in the domain, netbios is completely disabled, DNS knows nothing about the 192.168.99.0/24 network.
In net stat the following picture:
TCP 172.16.1.17:49224 %servername%:microsoft-ds ESTABLISHED
TCP
172.16.1.17:49225 %servername%:microsoft-ds ESTABLISHED
192.168.99.3:49219 the ESTABLISHED 192.168.99.1:microsoft-ds the TCP the TCP 192.168.99.3:49220 192.168.99.1:microsoft-ds the
ESTABLISHED the
TCP 192.168.99.3:49221 192.168.99.1:microsoft-ds the ESTABLISHED
the TCP 192.168.99.3:49222 192.168. 99.1:microsoft-ds ESTABLISHED
Why does win do this, and how can I avoid it?
UPD:
%servername% resolves, of course, as an address from the 172.16.1.0/24 network.
All connections look like 172.16.1.0/24 -> 172.16.1.0/24 and 192.168.99.0/24 -> 192.168.99.0/24; there are no connections like 172.16.1.0/24 -> 192.168.99.0/24 or vice versa. That is, there are no routing problems.
Win somehow determines that the target server is also available at a different address than the one that is directly indicated as the target address of the smb connection. How?

Answer 1

See routing.
netstat -rn

Answer 2

Your two servers do not know anything about each other (netbios off), all they know is what the DNS server gives them, and as I understand it, it gives them 172th to get hooked.
Use for smb a name override, a specific address on the 192nd subnet, or a pointer to hosts to explicitly bind to addresses from the 192nd subnet.
And in general it is not clear why such a perversion.