The windows sever VM as two vNICS. One with connected at 10GB with the default gateway and the other a 1 GB without a gateway. Here is the routing:
IPv4 Route Table
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 10.10.10.1 10.10.10.32 271
10.10.8.0 255.255.252.0 On-link 10.10.10.32 271
10.10.10.32 255.255.255.255 On-link 10.10.10.32 271
10.10.11.255 255.255.255.255 On-link 10.10.10.32 271
10.10.50.0 255.255.255.0 On-link 10.10.50.40 266
10.10.50.40 255.255.255.255 On-link 10.10.50.40 266
10.10.50.255 255.255.255.255 On-link 10.10.50.40 266
127.0.0.0 255.0.0.0 On-link 127.0.0.1 331
127.0.0.1 255.255.255.255 On-link 127.0.0.1 331
127.255.255.255 255.255.255.255 On-link 127.0.0.1 331
224.0.0.0 240.0.0.0 On-link 127.0.0.1 331
224.0.0.0 240.0.0.0 On-link 10.10.10.32 271
224.0.0.0 240.0.0.0 On-link 10.10.50.40 266
255.255.255.255 255.255.255.255 On-link 127.0.0.1 331
255.255.255.255 255.255.255.255 On-link 10.10.10.32 271
255.255.255.255 255.255.255.255 On-link 10.10.50.40 266
Persistent Routes:
Network Address Netmask Gateway Address Metric
0.0.0.0 0.0.0.0 10.10.10.1 Default
When a network scanner is run on the 10.10.50.0 subnet, traffic appears on the firewall indicating packets are being sent to the gateway instead going directly using the on-link. I thought on-link routes were always taking over the default route. In case this was wrong I manually set the metric to be lower for the 1 GB nic. The routing table shows the metric is lower than the rest.
It seems if I ping an existing IP address it does not use the gateway. If I ping an existing IP address, it doesn't use the gateway.
My question: Does the server use the gateway, if the device is not responding? Is there any circumstance where the server would use the gateway instead of a on-link connection?
Here is the ipconfig output:
Ethernet adapter Ethernet 12:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Hyper-V Network Adapter #6
Physical Address. . . . . . . . . : 00-15-5D-0A-E0-2F
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::a5f0:20fe:a7f:639c%13(Preferred)
IPv4 Address. . . . . . . . . . . : 10.10.50.40(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
DHCPv6 IAID . . . . . . . . . . . : 402658653
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-25-3A-10-76-00-15-5D-00-91-99
DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS over Tcpip. . . . . . . . : Enabled
Ethernet adapter Ethernet 11:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Hyper-V Network Adapter #5
Physical Address. . . . . . . . . : 00-15-5D-0A-E0-2E
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::c189:a031:82a0:52aa%14(Preferred)
IPv4 Address. . . . . . . . . . . : 10.10.10.32(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.252.0
Default Gateway . . . . . . . . . : 10.10.10.1
DHCPv6 IAID . . . . . . . . . . . : 268440925
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-25-3A-10-76-00-15-5D-00-91-99
DNS Servers . . . . . . . . . . . : 10.10.10.8
10.10.10.10
NetBIOS over Tcpip. . . . . . . . : Enabled
Tunnel adapter isatap.{B16B7A8C-8781-4A5C-8A21-65BEC4955296}:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter isatap.{AF16ECE1-DBD7-40DF-9CA6-DB071346C7F7}:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter #3
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes