Routing GURU? Need to route 1 network upstream and 1 downstream

[Bo Kelleher]

Hello all,

I am looking for some advice on configuring routes in w2k advanced
server. I have two NICS bound to two separate ISPs. I want to use
one for downstream and one for upstream (in a nutshell).

Windows will arbitrarily (or so it seems) pick a network when I open a
browser and make a reuqest, and all of the traffic for that browser
session will go over one network.

One of the networks that I have is Cable Modem. The other is DSL. I
am hosting a website on the DSL network and I don't want to impinge on
the ability to serve content from that address. I would like to be
able to have all sessions initiating from the host PC go over Cable
(much faster), and all inbound requests come in on DSL (DNS pretty
much determines this).

Each of the networks is on its own external router, but I am wondering
if I can configure Windows (via static routes, etc.) to use the Cable
modem when I initiate an outbound request.

Your advice is greatly appreciated!

Bo

 

[Matt P.]

-----Original Message-----
Hello all,

I am looking for some advice on configuring routes in w2k advanced
server. I have two NICS bound to two separate ISPs. I want to use
one for downstream and one for upstream (in a nutshell).

Windows will arbitrarily (or so it seems) pick a network when I open a
browser and make a reuqest, and all of the traffic for that browser
session will go over one network.

One of the networks that I have is Cable Modem. The other is DSL. I
am hosting a website on the DSL network and I don't want to impinge on
the ability to serve content from that address. I would like to be
able to have all sessions initiating from the host PC go over Cable
(much faster), and all inbound requests come in on DSL (DNS pretty
much determines this).

Each of the networks is on its own external router, but I am wondering
if I can configure Windows (via static routes, etc.) to use the Cable
modem when I initiate an outbound request.

Every time you need to make a network connection Windows
will use the routing table to determine what interface to
use. If the route isn't listed in the routing table the
request will be sent to the default gateway. If the two
NICs are on the same subnet (they aren't, are they?) then
it will pick one seemingly at random. Type 'route print'
at the command prompt and post back together with the
output from the command 'tracert hostname' where hostname
is the name of a site on the Net, repeat this a few times
to see how/if it changes.

Cheers,
Matt P.

 

[Herb Martin]

Hello all,

I am looking for some advice on configuring routes in w2k advanced
server. I have two NICS bound to two separate ISPs. I want to use
one for downstream and one for upstream (in a nutshell).

It is easy to setup but difficult to get the true effect in
practice...

"Client programs" typically pick the FIRST IP address defined,
so you must ensure that the Public Address you wish to user is
considered the first, on the first NIC. Clients control the return
address mostly.

If you use NAT don't share this NIC/address. This is the one
we want clients to use for return addresses.

Then make sure that all of your routes go through the OTHER
NIC/IP address -- no default gateway on the "client" NIC and
all routes through the upstream NIC.

In theory, the Clients will bind to a published "incoming" address
and the routing will send everything up the outgoing NIC.

Responses will be routed (by the outside world) to the "incoming
address."

You might run afoul of filters at the ISP or all sorts of other
weird problems since either system can have glitches that stop
the outgoing OR the return packets respectively.

I did this mostly to route all "RoadRunner" nets up the
RoadRunner cable and other requests up the DSL so that
reaching RoadRunner (etc) address didn't require going
all the way out through DSL to the "Internet backbone"
and back into RoadRunner....etc.