Two NICs on different networks

[Thrax]

Having a bit of a conundrum, here.

I have a wireless card with the following configuration:

DHCP-Assigned Address: 10.3.1.x
DHCP-Assigned Gateway: 10.3.1.1

This network card accesses INTERNET functions only.

I have a wired card with the following configuration:

Static Address: 10.1.1.250
Static Gateway: 10.1.1.1

This network card access INTRANET functions only.

How do I set it up so any address that goes to 10.1.* or 172.* goes across my 10.1 interface, and everything else goes across my 10.3.*?

[primesuspect]

What are your subnet masks?

[Thrax]

/28 for 10.3
/24 for 10.1

[RyderOCZ]

Do you have 2 routers?

What is 10.1.1.1 and what is 10.3.1.1? Meaning what kind of equipment are they?

EDIT: What do you mean /28 and /24 for subnet masks?

[Thrax]

10.1.x.x and 10.3.x.x are separate VLANs on our corporate network. That's just the addressing scheme that they use.

/28 means 255.255.255.128, 255.255.255.0 is /24.

[RyderOCZ]

Yep.... understood about Vlans.

Same question though... are 10.1.1.1 and 10.3.1.1 two separate routers, since they are the default gateways?

Anyway...is it not working right now? Based on what you have posted...it should be doing it already.

If I type 10.1.x.x into the browser, the 10.3.x.x gateway isn't going to know what to do with it, the request will go out over all network connections automatically, so the 10.1.1.1 gateway will answer and send you on your way.

When I have done 2 separate NIC's...I never had to specifically configure anything, the routing table just updates itself accordingly.

Can you post a SS showing the results of the command: Start > Run > CMD > Route Print.

[Thrax]

When I enable both network cards at the same time, I don't get any internet connectivity, or it is very erratic. Sometimes 10.1 responds, sometimes 10.3 responds.

<pre>
===========================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x10005 ...00 16 cb 0a d4 3e ...... Bluetooth Device (Personal Area Network)
0x160003 ...00 16 cb b5 f3 60 ...... Atheros AR5006X Wireless Network Adapte
0x170002 ...00 16 cb 8a aa 5a ...... Marvell Yukon 88E8053 PCI-E Gigabit Eth
t Controller
===========================================================================
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 10.1.1.1 10.1.1.250 10
0.0.0.0 0.0.0.0 10.3.1.1 10.3.1.52 25
10.1.1.0 255.255.255.0 10.1.1.250 10.1.1.250 10
10.1.1.250 255.255.255.255 127.0.0.1 127.0.0.1 10
10.3.1.0 255.255.255.128 10.3.1.52 10.3.1.52 25
10.3.1.52 255.255.255.255 127.0.0.1 127.0.0.1 25
10.255.255.255 255.255.255.255 10.1.1.250 10.1.1.250 10
10.255.255.255 255.255.255.255 10.3.1.52 10.3.1.52 25
12.120.1.254 255.255.255.255 10.3.1.4 10.3.1.52 1
64.12.25.218 255.255.255.255 10.3.1.4 10.3.1.52 1
64.12.31.225 255.255.255.255 10.3.1.4 10.3.1.52 1
64.156.13.20 255.255.255.255 10.3.1.4 10.3.1.52 1
64.233.163.83 255.255.255.255 10.3.1.4 10.3.1.52 1
64.233.167.99 255.255.255.255 10.3.1.4 10.3.1.52 1
66.77.165.210 255.255.255.255 10.3.1.4 10.3.1.52 1
66.77.165.211 255.255.255.255 10.3.1.4 10.3.1.52 1
66.77.165.219 255.255.255.255 10.3.1.4 10.3.1.52 1
66.77.165.225 255.255.255.255 10.3.1.4 10.3.1.52 1
66.151.152.143 255.255.255.255 10.3.1.4 10.3.1.52 1
69.20.62.196 255.255.255.255 10.3.1.4 10.3.1.52 1
69.20.62.201 255.255.255.255 10.3.1.4 10.3.1.52 1
69.26.180.10 255.255.255.255 10.3.1.4 10.3.1.52 1
72.14.203.99 255.255.255.255 10.3.1.4 10.3.1.52 1
72.21.210.11 255.255.255.255 10.3.1.4 10.3.1.52 1
72.247.201.51 255.255.255.255 10.3.1.4 10.3.1.52 1
77.67.126.66 255.255.255.255 10.3.1.4 10.3.1.52 1
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
194.129.79.22 255.255.255.255 10.3.1.4 10.3.1.52 1
204.15.20.49 255.255.255.255 10.3.1.4 10.3.1.52 1
205.128.92.124 255.255.255.255 10.3.1.4 10.3.1.52 1
205.188.8.196 255.255.255.255 10.3.1.4 10.3.1.52 1
205.188.248.150 255.255.255.255 10.3.1.4 10.3.1.52 1
207.46.106.21 255.255.255.255 10.3.1.4 10.3.1.52 1
209.85.133.166 255.255.255.255 10.3.1.4 10.3.1.52 1
209.85.159.166 255.255.255.255 10.3.1.4 10.3.1.52 1
209.124.56.70 255.255.255.255 10.3.1.4 10.3.1.52 1
209.170.75.187 255.255.255.255 10.3.1.4 10.3.1.52 1
216.38.163.117 255.255.255.255 10.3.1.4 10.3.1.52 1
216.73.86.74 255.255.255.255 10.3.1.4 10.3.1.52 1
216.73.87.52 255.255.255.255 10.3.1.4 10.3.1.52 1
216.185.214.2 255.255.255.255 10.3.1.4 10.3.1.52 1
224.0.0.0 240.0.0.0 10.1.1.250 10.1.1.250 10
224.0.0.0 240.0.0.0 10.3.1.52 10.3.1.52 25
255.255.255.255 255.255.255.255 10.1.1.250 10.1.1.250 1
255.255.255.255 255.255.255.255 10.3.1.52 10.3.1.52 1
255.255.255.255 255.255.255.255 10.3.1.52 10005 1
Default Gateway: 10.1.1.1
===========================================================================
Persistent Routes:
None

C:\Documents and Settings\Robert></pre>

[primesuspect]

Sounds like you want static routes. (http://en.wikipedia.org/wiki/Static_routing)

There are more elegant ways to do this using routing on the domain controller (is this even on a domain?), but to get it to work, you should just google a quick windows static routing primer.

[RyderOCZ]

Really odd Thrax...that route print looks good.

You can see the entries: 10.1.1.0 meaning anything with that scheme...goes through 10.1.1.250.
10.3.1.0 goes through 10.3.1.52.

That in itself should be getting your requests to the right place.

Have you tried a tracert to an internet destination and an intranet destination?

BTW... according to this... you are on /24 and /25 not 28: http://en.wikipedia.org/wiki/Subnet_mask

Try flushing the route cache: route -f

[Thrax]

Yeah, I meant 25. Sorry, was in a hurry, not terribly fast at binary in my head. ;D

And that's what's pissing me off, I know that the route print looks good, which is what stumps me.

//EDIT: Prime, I have no control over the routes, just my interfaces. :(

[RyderOCZ]

Do internet names resolve, but basically get no page in the browser?

I am assuming others in the company have similar network configs and they don't have issues?

[Thrax]

No, I'm the first one attempting to make this work. Most people just work from two separate computers, one on 10.3 and the other on 10.1.. But I really don't feel like desk clutter.

I get straight timeouts or destination unreachable when both networks are running.

[kryyst]

why not drop one network card and assign a second IP to your primary network card?

[Park_7677]

Try this:

On the INTRANET card, remove the gateway. Then enable both NICs and you should be able to reach the internet and anything on 10.1.1.0/24 network (but not 172.*) Adding a static route to 172.* would fix that.

Gateways are "last resorts" so having one on both NICs is a toss up for where "unknown" (non-local) network requests get sent. By removing the gateway from the INTRANET you should force all non-local network requests to be sent out the INTERNET NIC.

Also make sure DNS is reachable on both NICs or you might have to adjust settings for that too.