Windows Server 2016 sends trafic to wrong network interface when connected to two networks
Running Windows Server 2016 Standard with Desktop Experience on a server with two network cards.
- the 1st network card is connected to the internet and receives the configuration via DHCP server on the network 193.136../24
- the 2nd card is manually configured as a private network with a fixed IP 192.168.1.254 and netmask 255.255.255.0 without gateway or DNS, this card is connected only to a network switch that is not connected to anything else.
Configured another machine with a fixed IP 192.168.1.1 that is connected to the switch, the server and client can ping each other just fine.
On the server a tracert 192.168.1.1 works fine but if I do a tracert to a non-existing machine like 192.168.1.10 instead of getting "reports: Destination host unreachable." or something like that tracert shows that packages are sent to the gateway of the first network interface!!!
The exact same setup on older Windows servers didn't to that, I did several searches and coudn't find anything saying that this is a new behavior so i think this is a BUG!
Tracing route to 192.168.1.10 over a maximum of 30 hops
1 1 ms <1 ms 1 ms router.domain.com [193.136..]
2 <1 ms <1 ms <1 ms router-world.domain.com [193.137.xx.xx]
3 3 ms 3 ms 3 ms Router13.ispdomain.domain2.com [193.***.x.x]