Re: Default Gateway Setting not set after Reboot
From: David Morgan (david_at_davidmorgan.me.uk)
Date: 08/05/04
- Next message: Dimitri Moursellas: "Re: Connected but no access to network"
- Previous message: majoor: "NetBIOS over TCP/IP on modem connection"
- In reply to: Phillip Windell: "Re: Default Gateway Setting not set after Reboot"
- Next in thread: Phillip Windell: "Re: Default Gateway Setting not set after Reboot"
- Reply: Phillip Windell: "Re: Default Gateway Setting not set after Reboot"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 5 Aug 2004 09:30:57 +0100
Hi Phillip
Thanks for humouring me on this!
I think we're back to square one.now. I do have RRAS installed and
configured for another purpose but not running.
The fact remains that the server is connected to two subnets. I am not
interested in routing between them at this time. Each NIC has a default
gateway configured but when the machine boots up, one of the default
gateways is not set for one of the subnets on one of the NICs. This surely
is not how windows should behave as the dfg for the problematic interface is
set when the interface is disabled and enabled again.
Going to read through your posts again just in case I have missed anything.
>From your post below, I am not pinging from the same subnet as NIC2 and when
the DFG is set ok on that card I get a response. When it isn't, I don't.
All the time this is happening there is a DFG on NIC 1 which works fine.
Thanks
David M
"Phillip Windell" <@.> wrote in message
news:uUcbNumeEHA.1036@TK2MSFTNGP10.phx.gbl...
> "David Morgan" <david@davidmorgan.me.uk> wrote in message
> news:utP1g8leEHA.3124@TK2MSFTNGP09.phx.gbl...
> > With the DFG removed from NIC2 I get no reply to a ping. According to
> you,
> > this should come back directly from NIC2 (maybe via NIC1). It does not.
> It
>
> That's why I said in the last post that it matters where you are located
> when you try it. If you are pinging from machine in the same subnet as
NIC2
> then it will respond. If you are not, then "routing" must be enabled
before
> the NIC2 will communicate across subnets.
>
> > I should obviously point out again that I am running W2K, not XP.
>
> That doesn't matter.
>
> > (as there's no point going through a
> > firewall for requests initiated from the server or for replies),
>
> That doesn't make any sense.
>
> > although I
> > am convinced as per my situation above, if I remove the default gateway
on
> > one of the cards it will no longer respond at all.
>
> We are wasting our time here. You are getting this kind of behavior from
the
> machine because you have an over all bad design and are "covering" it with
> bad techniques.
>
> In the simplest form I can make it:...
>
> Barring a few extreme and unusual situations, there are only two reasons
to
> put more that one nic in a machine:
>
> 1. It is being used as a NAT device or Proxy Server
> 2. It is being used as a LAN Router
>
> In either case:
> A. RRAS must be running on the machine with "routing" enabled
>
> B. Only *one* Default Gateway exists.
>
> C. If there are "alternate" DFGs (for things like Dead Gateway
> Detection) then they must be all in the same subnet and be assigned at the
> same NIC as the normal Default Gateway.
>
> D. All other possible routes are handled by using Static Routes in the
> Routing Table or by the use of Routing Protocols such as RIP, IGRP, etc.
>
> E. If the machine acting as a Router is in the center of a "hub &
spoke"
> design, operating as a single Router, then there is no need for any Static
> Routes.
>
> --
>
> Phillip Windell [MCP, MVP, CCNA]
> www.wandtv.com
>
>
>
- Next message: Dimitri Moursellas: "Re: Connected but no access to network"
- Previous message: majoor: "NetBIOS over TCP/IP on modem connection"
- In reply to: Phillip Windell: "Re: Default Gateway Setting not set after Reboot"
- Next in thread: Phillip Windell: "Re: Default Gateway Setting not set after Reboot"
- Reply: Phillip Windell: "Re: Default Gateway Setting not set after Reboot"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
