Return to Answer

added 61 characters in body

Source Link

edited Oct 3 at 18:51

7.4k
2
21
32

I can ping the Security Router (10.212.69.3), so that is working fine, but Windows is chosing the wrong path for the target behind the Security Router

Routers route based on their routing table, not the routing table of the client. You can only specify next hop, you can't instruct upstream routers what to do.

Thus your route should be 100.102.1.136 via 10.0.0.97.

I can ping the Security Router (10.212.69.3), so that is working fine, but Windows is chosing the wrong path for the target behind the Security Router

Routers route based on their routing table, not the routing table of the client. You can only specify next hop, you can't instruct upstream routers what to do.

I can ping the Security Router (10.212.69.3), so that is working fine, but Windows is chosing the wrong path for the target behind the Security Router

Routers route based on their routing table, not the routing table of the client. You can only specify next hop, you can't instruct upstream routers what to do.

Thus your route should be 100.102.1.136 via 10.0.0.97.

Source Link

created Oct 3 at 18:46

vidarlo

7.4k
2
21
32

I can ping the Security Router (10.212.69.3), so that is working fine, but Windows is chosing the wrong path for the target behind the Security Router

Routers route based on their routing table, not the routing table of the client. You can only specify next hop, you can't instruct upstream routers what to do.