Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I am running Windows 7, and need to route DNS traffic to over a separate network interface without it passing through the primary (wired) interface. No other traffic should be routed through the second interface (3G) - partially due to speed and partially due to servers in the 10.x.x.x range. How can I configure Windows to route my traffic?

In particular, how can I configure Windows to not find a route to when the second interface is not plugged in or disabled?

Result of running route print with second interface enabled:

Interface List
 11..1c 6f 65 38 15 c3 ......Realtek PCIe GBE Family Controller
 20...8a 4e 09 12 1f 35 ......Remote NDIS based Internet Sharing Device
 1...........................Software Loopback Interface 1
 12...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter
 13...00 00 00 00 00 00 00 e0 Teredo Tunneling Pseudo-Interface

IPv4 Route Table
Active Routes:
Network Destination        Netmask          Gateway       Interface  Metric
    266         On-link    266         On-link    266         On-link    266         On-link    306         On-link    306         On-link    306         On-link    266         On-link    266         On-link    266         On-link    306         On-link    266         On-link    266         On-link    306         On-link    266         On-link    266
Persistent Routes:
share|improve this question

migrated from Feb 12 '13 at 23:42

This question came from our site for system and network administrators.

You do realise that we don't generally consider windows 7 'server' to be topical here don't you. Super User is a better place for that kind of question. – Iain Feb 9 '13 at 9:41
@Iain I had not realized it - the question is about workstation configuration in a large corporate office. As such I felt that it struck points 1 and 3 on the faq page. As you point out, since my issue could also be generalized to include home use, it also meets Super User posting standards ("specific issues with computer ... networking"). Would you be able to migrate it over? – Iiridayn Feb 11 '13 at 22:15
up vote 3 down vote accepted

I have a partial success by running:

route -p add mask metric 1000 if 11
route -p add mask metric 1 if 20
route -p change mask metric 1000 if 20

The last line doesn't influence the standard value of 266 when I plug the second interface back in, and I have had to re-run it each time. Although traffic does not pass through the primary interface to reach when the second interface is plugged in and configured, the routing table still permits connections to over the standard interface. I verified these results using Wireshark, which I verified by manually providing the first interface to ping.

Posting this in case a partial answer is good enough for similar cases.

share|improve this answer
Marking as accepted as the solution was adequate and I don't need it now. Willing to accept a better answer. – Iiridayn Jan 8 '14 at 13:18

The NIC priority could be incorrect. With both NICs connected open

Control Panel\Network and Internet\Network Connections

Now press Alt + n to open the Advanced menu and click on Advanced Settings. Now select the NIC that you want to be the primary interface and move it to the top using the arrow buttons.

share|improve this answer
I no longer work at that company, though I could probably set up the situation again from home. How would adjusting NIC priority prevent Windows from routing traffic to when only 1 NIC is found? – Iiridayn Jul 10 '15 at 14:19

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

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