Routing table

I need some assistance in configuring some routing tables on a Windows
2003 Server. This server has two network cards.

NIC1 is assigned ip 172.16.31.x/255.255.255.0
NIC2 is assigned ip 172.32.2.x/255.255.0.0

I need to route anything in the 172.16.31.x network to NIC1 and
everything else to NIC2. Is this possible?

Let me know if you need more details. Thank you!

Open a Command Prompt and type "route print" to see what your current routing
table looks like. Seems to me Windows should already be routing correctly since
these are both Class B addresses on separate networks. You may need to set
172.32.2.x as the default gateway.

"Matt Scoff" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
>I need some assistance in configuring some routing tables on a Windows
> 2003 Server. This server has two network cards.
>
> NIC1 is assigned ip 172.16.31.x/255.255.255.0
> NIC2 is assigned ip 172.32.2.x/255.255.0.0
>
> I need to route anything in the 172.16.31.x network to NIC1 and
> everything else to NIC2. Is this possible?
>
> Let me know if you need more details. Thank you!
>

As Mike said, that is pretty much what would happen without adding any
routes. Any traffic arriving at the server for a 172.16.31 address would go
to the 172.16.31.x interface and be delivered directly to the client. (Leave
the default gateway setting on this NIC blank). If you want all other
traffic to go out the 172.32.2.x interface, set a default gateway on that
interface pointing to a "next hop" router.

Mike Lowery wrote:
> Open a Command Prompt and type "route print" to see what your current
> routing table looks like. Seems to me Windows should already be
> routing correctly since these are both Class B addresses on separate
> networks. You may need to set 172.32.2.x as the default gateway.
>
> "Matt Scoff" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
>> I need some assistance in configuring some routing tables on a
>> Windows 2003 Server. This server has two network cards.
>>
>> NIC1 is assigned ip 172.16.31.x/255.255.255.0
>> NIC2 is assigned ip 172.32.2.x/255.255.0.0
>>
>> I need to route anything in the 172.16.31.x network to NIC1 and
>> everything else to NIC2. Is this possible?
>>
>> Let me know if you need more details. Thank you!

It does not appear to be working that way. But maybe there is another
solution? I have a web server with two network cards. One NIC(NIC2)
is connected to a router that is connected to the internet. The other
NIC(NIC1) is conencted to a router/firewall that is connected to my
internal network that only allows specified traffic. When I enable
NIC1 then my web page hosted b ythe server who's traffic should be
routed through NIC1 does not operate correctly but NIC2 does operate
correctly. When I disable NIC2 and enable NIC1, then the NIC1
connection operates correctly.
It appears to be a routing problem but it could be something else I
suppose.



On Tue, 6 Jun 2006 14:42:30 +1000, "Bill Grant" <not.available@online>
wrote:

> As Mike said, that is pretty much what would happen without adding any
>routes. Any traffic arriving at the server for a 172.16.31 address would go
>to the 172.16.31.x interface and be delivered directly to the client. (Leave
>the default gateway setting on this NIC blank). If you want all other
>traffic to go out the 172.32.2.x interface, set a default gateway on that
>interface pointing to a "next hop" router.
>
>Mike Lowery wrote:
>> Open a Command Prompt and type "route print" to see what your current
>> routing table looks like. Seems to me Windows should already be
>> routing correctly since these are both Class B addresses on separate
>> networks. You may need to set 172.32.2.x as the default gateway.
>>
>> "Matt Scoff" <(E-Mail Removed)> wrote in message
>> news:(E-Mail Removed)...
>>> I need some assistance in configuring some routing tables on a
>>> Windows 2003 Server. This server has two network cards.
>>>
>>> NIC1 is assigned ip 172.16.31.x/255.255.255.0
>>> NIC2 is assigned ip 172.32.2.x/255.255.0.0
>>>
>>> I need to route anything in the 172.16.31.x network to NIC1 and
>>> everything else to NIC2. Is this possible?
>>>
>>> Let me know if you need more details. Thank you!
>

Sounds more like IIS isn't listening on both IP addresses. Try running
"WMSHttpSysCfg.exe" as mentioned in this article:
http://support.microsoft.com/kb/328728

"Matt Scoff" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> It does not appear to be working that way. But maybe there is another
> solution? I have a web server with two network cards. One NIC(NIC2)
> is connected to a router that is connected to the internet. The other
> NIC(NIC1) is conencted to a router/firewall that is connected to my
> internal network that only allows specified traffic. When I enable
> NIC1 then my web page hosted b ythe server who's traffic should be
> routed through NIC1 does not operate correctly but NIC2 does operate
> correctly. When I disable NIC2 and enable NIC1, then the NIC1
> connection operates correctly.
> It appears to be a routing problem but it could be something else I
> suppose.
>
>
>
> On Tue, 6 Jun 2006 14:42:30 +1000, "Bill Grant" <not.available@online>
> wrote:
>
>> As Mike said, that is pretty much what would happen without adding any
>>routes. Any traffic arriving at the server for a 172.16.31 address would go
>>to the 172.16.31.x interface and be delivered directly to the client. (Leave
>>the default gateway setting on this NIC blank). If you want all other
>>traffic to go out the 172.32.2.x interface, set a default gateway on that
>>interface pointing to a "next hop" router.
>>
>>Mike Lowery wrote:
>>> Open a Command Prompt and type "route print" to see what your current
>>> routing table looks like. Seems to me Windows should already be
>>> routing correctly since these are both Class B addresses on separate
>>> networks. You may need to set 172.32.2.x as the default gateway.
>>>
>>> "Matt Scoff" <(E-Mail Removed)> wrote in message
>>> news:(E-Mail Removed)...
>>>> I need some assistance in configuring some routing tables on a
>>>> Windows 2003 Server. This server has two network cards.
>>>>
>>>> NIC1 is assigned ip 172.16.31.x/255.255.255.0
>>>> NIC2 is assigned ip 172.32.2.x/255.255.0.0
>>>>
>>>> I need to route anything in the 172.16.31.x network to NIC1 and
>>>> everything else to NIC2. Is this possible?
>>>>
>>>> Let me know if you need more details. Thank you!
>>
>

I re-read Bill's message about leaving the gateway blank on the
172.16.13.x network and everything starting working correctly! Thank
you so much!

Yes, that can really foul up RRAS.


Matt Scoff wrote:
> I re-read Bill's message about leaving the gateway blank on the
> 172.16.13.x network and everything starting working correctly! Thank
> you so much!