Network binding order

[Sydney IT guy]

I learned that the network interface binding order has been deprecated from windows 2016 and above. However, the question is how do I know the 'real default route' used by windows when I have two network cards set with a default gateway? (yes the 'metrics' for both the routes are the same.)


Some discussions here (pre windows 2016 servers)

Default gateways: TCP/IP

docs.microsoft.com

(If multiple interfaces of the same speed have the same lowest interface metric, then, based upon the binding order, the default gateway of the first network adapter is used. The default gateway for the second network adapter is used when the first is unavailable.)

---------------------------------------------


(1) Pls note that I know how to influence the real' default routes by setting up the metric manually. But my problem is that, I have a PRODUCTION server with two default gateways with the same metrics. So I am curious which is the 'real default gateway'

IPv4 Route Table
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 10.150.17.1 10.150.17.21 261
0.0.0.0 0.0.0.0 10.100.1.1 10.100.14.45 261

(2) In previous versions of the windows, I will look at the network binding order to know the real 'default gateway'. This server is windows server 2016 and the 'binding order' is gone :-(

Continue reading...