Re: 2003 - multiple nics multiple subnets

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: Phillip Windell (_at_.)
Date: 03/25/04 

Date: Thu, 25 Mar 2004 15:08:14 -0600

There should only be one Default Gateway. You should not have a Default
Gateway on more than one NIC. Default Gateways are "global" in nature and by
definition there can be only one. It should be placed on the one NIC that
has either a direct route out of the private system or the route to some
other router that does have a direct route out of the system.

Default Gateways are only for "unspecified routes",.... that is routes to
places you don't own and don't have defined in a Routing Table,...such as
the Internet. All other destinations are "specified routes" and use Routing
Table entries and don't use Default Gateways.

If this represents a "hub & spoke" design with this machine being the
"hub"... , and your description indicates this is true, ...then there simply
are no other gateways because every subnet is a "directly-connected-network"
and so the route to it is already established. But, if there are other
routers scattered through out the network then either you must create static
routes for them in the OS's routing table or enable and use "Routing
Protocols" such as RIP and allow it time to automatically build its Route
Table.

You should use RRAS (Routing and Remote Access) as the "service" and the
"interface" to make the routing "happen". 

--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com
"Brian Graham" <brian.graham2@ntlworld.com> wrote in message
news:eCz4u6oEEHA.3040@TK2MSFTNGP12.phx.gbl...
> We have currently a windows 2000 advanced server with 4 NICs each having
an
> ip address on 4 different subnets, and each configured with the gateway
for
> its own subnet, this has been a convienent arrangment in this environment
as
> there are only 4 subnets and this made RIS and DHCP work far better. There
> is only the one server in this ADS domain.
>
> I have come to install Windows 2003 enterprise edition onto a spare Compaq
> ML370 with an onboard network card and I have installed 3 additional 3com
> cards to make 4 in total, ie to duplicate the current structure.  However,
> 2003 seems to take offence to me trying this.  And sure enough does not
> function correctly.
>
> I have looked and cant find any document or advice as to how to configure
> multilple network cards in a windows server environment, only that
relating
> to fault tolerence situations.
>
> Any ideas folks?
>
> Thanks
>
> Brian
>
>
>

Relevant Pages

  • Re: Two NICS - Windows XP - I dont want any traffic between them
    ... I don't know that IP routing has changed much since NT. ... difference in XP is the Automatic metric feature which may be of some help ... All NICs in a Windows machine will use the same default gateway ... Both are set for different default gateways. ...
    (microsoft.public.windowsxp.network_web)
  • Re: 2003 - multiple nics multiple subnets
    ... Brian ... > has either a direct route out of the private system or the route to some ... > places you don't own and don't have defined in a Routing Table,...such as ... > Table entries and don't use Default Gateways. ...
    (microsoft.public.windows.server.networking)
  • RE: How to switch between two network paths?
    ... Add a persistent route in the routing tables of the machines for the others respective networks ... Machine 1 is located, through the gateway, routed into a VPN tunnel, out ... Then I set the metric for the default gateways of both Machines (these are the routes for the ...
    (microsoft.public.win2000.networking)
  • Re: adsl + cable multiple connection problem
    ... >> But when the ADSL connection fails, ... the whole multipath route. ... probably alive gateways). ... The benefit is only the proper routing for NAT connections over ...
    (comp.os.linux.networking)
  • Re: SBS Firewall
    ... > gateways be 10.0.0.1, the hard firewall. ... > SO change routes in DHCP or manually GateWay the workstations? ... So I usually do the "single NIC, hardware firewall appliance" route ...
    (microsoft.public.windows.server.sbs)