Default Gateway Metric 0?
Hi,I need to use a different gateway for a specific address. I have used the following command successfully on an XP computer:route add a.b.c.d mask 255.255.255.255 w.x.y.z metric 1Where a.b.c.d is the IP address of the remote server and w.x.y.z is the gateway IP address.
When I try the same on a Vista computer the command completes ok but when I do;
tracetr a.b.c.d
It routes via the default gateway. If I then do a;
route print
the route for 0.0.0.0/0 has a metric equal to the interface metric.
Either:
As it is not possible to give a route a metric of 0 but the default gateway has a metric of 0, how do I add routes that will be used?
Or:
Why does the default gateway have a metric of 0 and how do I change this for a DHCP connection.
Thanks in advance,
Norman
February 5th, 2010 3:49pm
Hi, I had a similar problem: the default gateway has a too low metric by default; for now, I manually solve with this: route change 0.0.0.0 mask 0.0.0.0 GATEWAY-IP metric 100 so other routes will have a lesser metric. If you want to set DHCP metrics, you have to open TCP/IPv4 settings, then Advanced, and uncheck automatic metric and set a high value as 100 or more. An high metric on a default gateway is not important, because when you use it, it's simply because there are no other specific routes.
Free Windows Admin Tool Kit Click here and download it now
February 20th, 2010 2:14am
Hi, I had a similar problem: the default gateway has a too low metric by default; for now, I manually solve with this:
route change 0.0.0.0 mask 0.0.0.0 GATEWAY-IP metric 100
so other routes will have a lesser metric.
If you want to set DHCP metrics, you have to open TCP/IPv4 settings, then Advanced, and uncheck automatic metric and set a high value as 100 or more.
An high metric on a default gateway is not important, because when you use it, it's simply because there are no other specific routes.
Great !!!
SO it is possible to assigna different priority for each NIC.
Thank you !!!
Giulaino
February 2nd, 2011 6:31am