Ignoring the most specific route?

Question

Server has two interfaces (192.168.101.19 with netmask 255.255.255.0 and 192.168.151.253 with netmask 255.255.255.0).
If I ping a client 192.168.126.14 from the server, packets go through default route (192.168.101.1).

Why?

Route to host 192.168.126.14 is the most specific and therefor it should be top priority.
Also route's metric is lower than default's route.

Answer 1

Well, it's quite interesting how Windows works...

The problem was at host level (running ESXi) where a Port Group was missing correct VLAN ID.

So Windows was able to ping gateway but not able to pass packets through the gateway.
Maybe Windows is able to detect that situation hence it was trying to push packets via different gateway.

Answer 2

Hi,

Thanks for posting here.

Normally, if the specific route entry to a host was added and the metric was smaller than the default, then the route to this host should be go through the specific route.

Please try to delete the specific route entry and then add this entry again to see if the issue was resolved. If the issue is still existed, please help to provide screenshot of the error message for us further troubleshooting.

I have tested in my lab and here is the result for your reference.

A server with 2 NICs:
NIC A: 192.168.0.1 255.255.255.0
NIC B: 192.168.2.1 255.255.255.0

Route print result of this server:

Then ping host 192.168.126.14, the gateway 192.168.0.1 responded

Add a specific route entry of host 192.168.126.14 to go through gateway 192.168.2.1

Then ping 192.168.126.14, the gateway 192.168.2.1 responded

Hope my answer will help you!

---Please Accept as answer if the reply is helpful---

Best Regards,
Sunny