Re: I'll explain it again :D
From: Phillip Windell (_at_.)
Date: 05/03/04
- Next message: Phillip Windell: "Re: DNS Resolving"
- Previous message: Dave Leonardi: "IE6 Rollout"
- In reply to: noobtech: "I'll explain it again :D"
- Next in thread: Phillip Windell: "Re: I'll explain it again :D"
- Reply: Phillip Windell: "Re: I'll explain it again :D"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 3 May 2004 09:46:15 -0500
There is a lot of small details in this message, do *not* blow through it
and ignore details.
"noobtech" <anonymous@discussions.microsoft.com> wrote in message
news:48DC3441-AED9-4795-87AA-98893679B1F5@microsoft.com...
> I have a winxp pro machine that's connected to the internet via dial-up.
ICS is enabled on the dial-up
> and the machine has a nic card installed. ICS gives my Nic card the ip of
192.168.0.1, changing the
> IP to something else and ICS does not work.
It didn't tell you to change the IP#s on *that* machine. I told you to make
them static on the 2-nic machine that you mention next. ICS doesn't assign
the whole 192.168.0.0 block,...it only assigns part of the block. If you
use IP#s above that range there won't be a problem. I don't remember the
cut-off point, so you can just start with 192.168.0.254 and work backward.
I have even heard of people assigning a static address that ICS does use and
it still worked because ICS makes sure the address isn't in use before it
assings it to something, but I would recommend that.
> I have another machine (let's call it B) B machine is a 2003 server with 2
nics. First nic has
> "automatically obtain IP". This nic gets it's Ip from the winxp machine
above. It allows this machine
> access to the internet. The second Nic has a static IP of 192.168.5.1
Change the "automatic nic" to a static 192.168.0.254, mask 255.255.255.0,
gateway 192.168.0.1, DNS 192.168.5.2. Just do it,...don't worry about the
"the World according to ICS".
> I have another machine (machine C) C machine has one Nic but it is a
window 2003 server that is a domain controller. It has a static Ip address
of 192.168.5.2 This machine also hosts DNS and DHCP for my local lan/domain.
The default gateway for this machine is 192.168.5.1 It is the IP address of
NIC 2 on machine B.
That's fine, I see no problem there.
> My client computers are set to "obtain ip automatically" and the DHCP on
machine B hands the ip's
> out. The default gateway for my client computers are set to the windows
2003 DC which is
> 192.168.5.2
That's fine, but that will only work for machines on the 192.168.5.0 subnet.
The machines on the192.168.0.0 subnet are at the "mercy" of ICS unless you
make them static.
> Locally my network is fine. All computers on the LAn can communicate with
each other and the DC.
> I can also ping Nic 2 on machine B from any machine in the local LAN. The
problem is that none of
> the client machines nor the DC on the local lan has access to the
internet. The only machine that has
> any access to the internet is Machine B. The machine that has the duel nic
installed.
> I was told that I can configure machine B as a ip router and route traffic
between nic 1's connection
> and nic 2's connection. But from what I read in books a machine that is
acting as a ip router between
> two segments can not have a default gateway on either of it's nics. Nic 1
on machine B has gateway
> information because it is set to "obtain ip automatically. Would IP
routing still work in this case?
**Every** machine in your system (both subnets) must point to the
192.168.5.2 machine as their DNS. For what to do on the ICS machine see
below.... Then in your DNS Server you need to create a Forwarders List
that lists the ISP's DNS Server. If you do not create the Forwarders List
then you are screwed and are just wasting you time.
On the ICS machine make sure that the Internal Nic is set to be the highest
priority nic and that the Internal NIC uses the 192.168.5.2 as the DNS
Server. Leave the rest of the network settings in the internal nic alone.
The ICS machine must also have a Static Route entered into the Routing Table
otherwise the 192.168.5.x subnet will be cut off. If you do not do this
then you are also screwed and wasting your time. If you used the
192.168.0.254 address for the one side of the duel-nic machine as I
suggested, then the route command would look like this:
c:\> Route Add -p 192.168.5.0 mask 255.255.255.0 192.168.0.254
-- Phillip Windell [MCP, MVP, CCNA] www.wandtv.com
- Next message: Phillip Windell: "Re: DNS Resolving"
- Previous message: Dave Leonardi: "IE6 Rollout"
- In reply to: noobtech: "I'll explain it again :D"
- Next in thread: Phillip Windell: "Re: I'll explain it again :D"
- Reply: Phillip Windell: "Re: I'll explain it again :D"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
