Setting up multiple network adapters (Internet sharing)

  • Thread starter Thread starter Ivan
  • Start date Start date
I

Ivan

Can anyone help me setting up this network?

Server (Win2k)
- Adapter 1: connected to cable modem using dynamic IP
- Adapter 2: connected to client '2' (Win2k)
- Adapter 3: connected to client '3' (Win2k)

I wish to share the internet to the clients.
Please tell me step by step how to setup such a network.
Many thanks.
 
Ivan said:
Can anyone help me setting up this network?

Server (Win2k)
- Adapter 1: connected to cable modem using dynamic IP

If you use RRAS you can add this interface to NAT as a PUBLIC interfact and
the other interfaces as PRIVATE interfaces.

If you have an internal DNS server then you may need to record the DNS
server
address given you by the DHCP server and then OVERRIDE it manually to
point to the actual internal DNS.
- Adapter 2: connected to client '2' (Win2k)
- Adapter 3: connected to client '3' (Win2k)

Why do you have two NICs on the server for just two clients? A simple hub
with
all of the internal machines connected to it might be simpler (and allows
for additional
PCs.)

BUT your method above does work. Give each NIC a different address and use
another
address from that range for the additional PC, i.e.,

172.16.8.1 mask 255.255.255.0 with the other machine using 172.16.8.2
172.16.9.1 mask 255.255.255.0 with the other machine using 172.16.9.2
All machines would use MASK 255.255.255.0 and the other machines will
specify
the address of the NAT machine 172.16.8.1 or 9.1 as their "Default Gateway."
I wish to share the internet to the clients.
Please tell me step by step how to setup such a network.
Many thanks.

What else do you wish to know?
 
Thanks for you reply.

Actually what I was worrying about is that for adapter 1,
do I need to check the box "Enable Internet Connection
Sharing"? If yes, I need to choose which network to share
to, i.e. adapter 2 OR adapter 3. The problem is that I
can choose only one, so the other one cannot get access to
the internet.

P.S. I need to use 2 NICs for 2 clients because I just
bought a Gigabit LAN card, but don't want to spend bucks
on a Gigabit hub. =)
 
Internet Connection Sharing won't work for you here, you need to follow the
steps Herb recommended and set up RRAS and NAT instead.

--

Thanks,
Marc Reynolds
Microsoft Technical Support

This posting is provided "AS IS" with no warranties, and confers no rights.
 
With Windows 2000 Pro you don't have the RRAS/NAT option. Your best bet is
to follow Roland's advice and set the GB NIC down to 10/100 and use a hub.
You can then enable ICS.

--

Thanks,
Marc Reynolds
Microsoft Technical Support

This posting is provided "AS IS" with no warranties, and confers no rights.
 
:
: Hm... I know nothing about RRAS and NAT. Would you kindly
: tell me how to set them up?

Ivan...he already gave you the information you needed. If you need to know
how to install RRAS, etc. then a little investigation on your own might be
warranted. (see Help File)

You said you purchased a Gb NIC but didn't want to fork over for the Gb hub.
That is understandable. However, doesn't this NIC also do, 10/100 as well
as 1000? You could use a 10/100 switch, for now, only use one of the 2
client NICs in the server, connect it to the hub, setup ICS on that NIC in
the server and set your workstations to autodetect IP/DNS. Or, do it the
way Herb suggests. (O;=

--
Roland

This information is distributed in the hope that it will be useful, but
without any warranty; without even the implied warranty of merchantability
or fitness for a particular purpose.
-Technet Knowledge Base-
http://support.microsoft.com/default.aspx?scid=fh;EN-US;kbhowto&sd=TECH&ln=EN-US&FR=0
-Technet Script Center-
http://www.microsoft.com/technet/treeview/default.asp?url=/technet/scriptcenter/default.asp
-WSH 5.6 documentation download-
http://www.microsoft.com/downloads/...48-207D-4BE1-8A76-1C4099D7BBB9&displaylang=en
-MSDN Library-
http://msdn.microsoft.com/library/default.asp
 
The reason that ICS (enable network connection sharing) won't work is
because you have TWO INTERNAL NICs/Networks.

ICS has almost all the features of NAT
(which is really the same software but is configured at part of RRAS)

Pro (You said Server initially) doesn't have NAT -- just ICS.
XP can do "bridging" which joins two (e.g., internal) NICs into one virtual
NIC/net
but you have Win2000.

ICS lacks these features of NAT:
Configuration -- NAT is highly configurable; ICS is not
Multiple internal or external NICs/Nets
Multiple IP addresses on the external NIC
Fully configurable DHCP server (can also be disabled completely in NAT)

Since you have two NICs internally -- my question remains, "Why"? you must
use
Server/NAT or find a third party (probably small hardware router) solution.
 
Roland Hall said:
That was a good call on your original post. I completely misread the 2 NIC
external setup and would have flubbed my first response. (flubbed is a
variable) (O:=

I only pay attention to that because I tend to recommend "NAT" over ICS if
it
is a choice.

The main reason is for the CONFIGURATION.

Many people think that NAT does a "lot of stuff" that ICS won't do but that
isn't
really true. There are differences but it is mostly in "confiriguratin",
especially if
we consider the "multiple NICs/multiple IPs externally" to be part of
"configuration."
 
That was a good call on your original post. I completely misread the 2 NIC
external setup and would have flubbed my first response. (flubbed is a
variable) (O:=

Roland
 
Back
Top