Go Premium for a chance to win a PS4. Enter to Win

x
?
Solved

help with Windows Routes and Metrics

Posted on 2013-10-26
3
Medium Priority
?
505 Views
Last Modified: 2014-07-02
i have a single device sitting on a network with a firewall (cisco asa) between it and a device that sends data to it.  For an example (not real IP's) here is info

Destination device = 10.10.10.100
source device network card 1 = 192.168.10.10, firewall gateway 192.168.10.1
source device network card 2 = 192.168.20.10, firewall gateway 192.168.20.1

there are basically two routes for the firewall that we want to prioritize to always go over card 1 unless it is down.  In the route tables on windows we issued these commands

route add -p 10.10.10.100 mask 255.255.255.255 192.168.10.1 metric 1
route add -p 10.10.10.100 mask 255.255.255.255 192.168.20.1 metric 2

after the persistent route tables show the correct entries as expect.

what we expected was for the route to take metric 1 on card1 if available and if card 1 fails to automatically pick communications using card 2 which has a metric of 2 (more expensive)

it doesn't work, we disconnected the cable off of card 1 and ping to device fails
if we make them both metric 1, it looks like it at least pings and gets through, but how do we prioritize using the metric then??

Any help would be appreciated, maybe i'm expecting too much from Windows networking.
Do you think just disconnecting the card is not enough for windows to take the next metric?

thanks
0
Comment
Question by:rkneal
  • 2
3 Comments
 
LVL 71

Accepted Solution

by:
Qlemo earned 1500 total points
ID: 39603855
It should work that way. As soon as you disconnect the physical network connection for card 1, all according routes should get invalid, even if persistent. But no dice, proper routing is only done with non-persisting routes, because those are dismissed (of course) as soon as the associated network connection has gone. A workaround is to to use non-persistent routes, and set those on a regular base in case the connection comes back again.

Anyway, is it likely the connection to the ASA will fail? More probably the connections behind ASA are down, and that would not help you at all.
0
 
LVL 44

Expert Comment

by:Darr247
ID: 39604640
Try
route add -p 0.0.0.0 mask 0.0.0.0 192.168.10.1 metric 1
route add -p 0.0.0.0 mask 0.0.0.0 192.168.20.1 metric 2

instead.
0
 
LVL 71

Assisted Solution

by:Qlemo
Qlemo earned 1500 total points
ID: 39604930
Default gateway failover doesn't work for the same reason, so I don't think that makes any difference.
0

Featured Post

Ask an Anonymous Question!

Don't feel intimidated by what you don't know. Ask your question anonymously. It's easy! Learn more and upgrade.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Have you ever set up your wireless router at home or in the office to find that you little pop-up bubble in the bottom right-hand corner of Windows read "IP Conflict - One of more computers on the network have been assigned the following IP address"…
Trying to figure out group policy inheritance and which settings apply where can be a chore.  Here's a very simple summary I've written which might help.  Keep in mind, this is just a high-level conceptual overview where I try to avoid getting bogge…
Michael from AdRem Software explains how to view the most utilized and worst performing nodes in your network, by accessing the Top Charts view in NetCrunch network monitor (https://www.adremsoft.com/). Top Charts is a view in which you can set seve…
Is your data getting by on basic protection measures? In today’s climate of debilitating malware and ransomware—like WannaCry—that may not be enough. You need to establish more than basics, like a recovery plan that protects both data and endpoints.…

885 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question