I have a Windows Server Box with 2 NICs sitting in 2 Networks with a Gateway Router to a 3rd: e.g.:

A: - Remote Network
B: - "DMZ" with GW Router to Network A on IP
C: - Local LAN - Default Gateway

NIC1 is in Network B:
NIC2 is in Network C: - gets settings via DHCP

I want to have access to/from network A. When I set the default gateway on NIC1 to I can reach network A, but a config with 2 different default gateways is considered problematic/broken.

How to best solve this?

My first intuition was to set a route to network A via the router on network B:

route add mask


  • The route gets ignored. The command answers with OK!, a subsequent 'route print' does not list that route

You can't have two default gateways because it's an oxymoron. Another phrase for Default Gateway would be "Gateway of Last Resort", and two things can't be last.

It may help you visualise this if you remember that Windows routing (And that includes your default gateway(s)) is a global setting for all NICs, IP's and interfaces.

You may need to add the metric and interface option to the command. Please try with those options and then post the results of route print here if that doesn't help. Additionally, if you want this setting to persist across reboots, you will need to add -p after route:

  • I know that only one of them will be used, its just a lookup in a flat table, it was meant more or less tongue in cheek. – AndreasT May 17 '13 at 13:02
  • @AndreasT I thought so, given the rest of your post, but I see it on a worryingly common basis! – Dan May 17 '13 at 13:03

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.