How to force win to set up an smb connection to only one of the two possible routes?

Given: two machines with win server with two possible communication paths
1) directly with a cable subnet 192.168.99.0/24
2) through the router to the subnet 172.16.1.0/24

When one machine tries to connect to another via smb at the network 192.168.99.0/24 is actually installed and the network 172.16.1.0/24.
Both machines are in domain, netbios is completely disabled, the DNS knows nothing about the network 192.168.99.0/24.
Stat net in the following picture:
TCP 172.16.1.17:49224 %servername%:microsoft-ds ESTABLISHED
TCP 172.16.1.17:49225 %servername%:microsoft-ds ESTABLISHED
TCP 172.16.1.17:49226 %servername%:microsoft-ds ESTABLISHED
TCP 192.168.99.3:49219 192.168.99.1:microsoft-ds ESTABLISHED
TCP 192.168.99.3:49220 192.168.99.1:microsoft-ds ESTABLISHED
TCP 192.168.99.3:49221 192.168.99.1:microsoft-ds ESTABLISHED
TCP 192.168.99.3:49222 192.168.99.1:microsoft-ds ESTABLISHED

Why win does that, and how to avoid it?

UPD:
%servername% resolvida, of course, as an address from the network 172.16.1.0/24.
All connections are of the form 172.16.1.0/24 -> 172.16.1.0/24 and 192.168.99.0/24 -> 192.168.99.0/24; compounds of kind 172.16.1.0/24 -> 192.168.99.0/24 or in the opposite direction is not. That is, there are not routing issues.
Win somehow determines that the target server is available at a different address than the one directly specified as the target address of the smb connection. How?
June 3rd 19 at 19:15
3 answers
June 3rd 19 at 19:17
See the routing.
netstat -rn
Routes with no problems, queries to the network 192.168.99.0/24 via an appropriate interface, all the others through the gateway in the network 172.16.1.0/24. - Keanu32 commented on June 3rd 19 at 19:20
June 3rd 19 at 19:19
Your two servers don't know anything about each other (netbios off), all they know is the fact that it gives the DNS server and as I understand he gives them 172ю get hooked.
Use for smb tamest names, specific addresses 192й subnet or a pointer in the hosts explicitly bind to the address of 192й subnet.

In General, it is not clear what for such perversion.
Contacting the destination server directly on the address from the network 192.168.99.0/24. The idea they have of each other's names in General should not know. - Keanu32 commented on June 3rd 19 at 19:22
Why is it they don't have to know names? - Keanu32 commented on June 3rd 19 at 19:25
,
From where, exactly? - earl.Weissnat commented on June 3rd 19 at 19:28
Well usually DNS, WINS. - Keanu32 commented on June 3rd 19 at 19:31
June 3rd 19 at 19:21
If you contact SBM server address from the subnet in which you are, the traffic will go directly.
If it doesn't directly means you are probably called by their first name, and the name gives a different IP address, the traffic goes through the default route on the router.
Conclusion - go via IP address or follow the mapping of names and addresses - who is involved in these DNS or WINS
I repeat: the appeal goes directly on the ip, and the traffic goes on both channels simultaneously. - Keanu32 commented on June 3rd 19 at 19:24
Why do you think so?

You brought -
TCP 172.16.1.17:49224 %servername%:microsoft-ds ESTABLISHED

Address to servername, the server name issued address 172.16.1.17, the connection is established.
Because this address lies in different subnet, then traffic goes through the router.

TCP 192.168.99.3:49219 192.168.99.1:microsoft-ds ESTABLISHED

The connection with the ip address 192.168.99.3 installed.

In the end not hesitate to named traffic goes through the router, go direct traffic goes directly.
What's the problem then? - Keanu32 commented on June 3rd 19 at 19:27
Win somehow determines that the target server is available at a different address
Well, of course, if this address is in the same subnet.
What are you doing masquerading on the router, no.

For example I have a file of the ball in three locations distributes through different cards and nothing. - earl.Weissnat commented on June 3rd 19 at 19:30
,
Please, read written fully, not in fits and starts.

Address to servername, the server name issued address 172.16.1.17, the connection is established.
Because this address lies in different subnet, then traffic goes through the router.

It was an appeal only to 192.168.99.1; initiative Venda arbitrarily set parallel connection to %servername%.

Well, of course, if this address is in the same subnet.

192.168.99.1 is in subnet 172.16.1.0/24? Breaking news. - Keanu32 commented on June 3rd 19 at 19:33
Connect to Orb you? The connection string give? Name?

Well, of course, if this address is in the same subnet.
In the same subnet as the client.

I can't understand what you do not like?
  • That the traffic goes through the router at the address 172.16.1.0/24 - then contact us directly and the problem will disappear.
  • That traffic comes directly - then disable the server to run at this address
- earl.Weissnat commented on June 3rd 19 at 19:36
,
then contact directly and the problem will disappear.

I repeat once again: the request is made directly. - Keanu32 commented on June 3rd 19 at 19:39
,
I repeat once again: the request is made directly.

If you are applying directly, then line connecting to the balloon you \\192.168.99.3\ so?

Then I just don't understand how you traffic can go on 172.16.1.17 is already fantastic then. - earl.Weissnat commented on June 3rd 19 at 19:42
,
\\192.168.99.1 to be extremely accurate.

it is fantastic what it is.

So and I about what?
Himself scratching his head. - earl.Weissnat commented on June 3rd 19 at 19:45
And address of the client is what?
And how is configured the server on which ball?
What sort of routes? - Keanu32 commented on June 3rd 19 at 19:48
And address of the client is what?

192.168.99.3 =/

And how is configured the server on which ball?

For incoming connections is only open 445/TCP; netbios is disabled on all interfaces; LLMNR disabled via policy.

What sort of routes?

The gateway to 172.16.1.1, 192.168.99.0/24 on the appropriate interface.

The question is not whether that traffic is wrong - the question is how the client learns all about the presence of the second address from the server.

Actually, I had a couple thoughts... the Client appears to the server c the computer account in the domain. I'll have to check how it handles authentication through Kerberos (although should not), or using ntlm; if the first - try to disable it.
Corny and try to cheat a customer, given a hostname in the hosts left, and try to connect it. - earl.Weissnat commented on June 3rd 19 at 19:51

Find more questions by tags Computer networksWindows Server