Setting up a DC to server client machines with internet connection sharing.

[1stuk]

I've had very little luck configuring 'internet connection sharing' (ICS) on
a Win2k Server Domain Controller (DC) to server the client machines.

Various articles from informative and well know book sources and websites on
allowing a win2k
server to share the internet connection, and distribute the internet acces
to the
client machine, have proves fruitless in getting the solution to work.

Correct me if am wrong but configuring 'routing and remote access' should do
the trick as various articles have suggested this with DHCP also setup.

But so far am hiting a brick wall and the client machines can get any
internet access at all, even though I can see in DHCP the addresses been
leased out to each individual machines and users can logon to the domain
controller using the user accounts.

Is there a fool proof walkthrough that explains in the queens english 'how
to
set up internet connection sharing to client machines on a win2k server?'

SBS 2000 is so much easier to setting up ICS than win2k. /me sighs

Thx

 

[Steven L Umbach]

Since your are using Server version, you should be using NAT instead which is
configurable in the rras Management Console. Under ip routing/general select
action/new protocol and select NAT and go from there. The built in help files should
help you set it up. If you have a high speed connection, you might want to consider a
internet appliance firewall. Netgear makes true certified SPI firewall that would
work fine for a small network for less than $100. That way you can keep the internet
traffic off of your domain controller. All you would have to do is configure your
dhcp server options to point to the device as the default gateway. --- Steve

http://www.netgear.com/products/prod_details.asp?prodID=140&view=

 

[Herb Martin]

I've had very little luck configuring 'internet connection sharing' (ICS)
on

a Win2k Server Domain Controller (DC) to server the client machines.

It's actually very easy and a bad idea.

Correct me if am wrong but configuring 'routing and remote access' should do
the trick as various articles have suggested this with DHCP also setup.

Maybe this is part of your misunderstanding -- Technically ICS and NAT are
two different things (very similar but they are configured differently.)

ICS exists on servers but NAT is a better choice when you can use it. ICS
is setup on the NICs (or dial interfaces) in Win2000. Turn this off.

NAT is in RRAS -- add the NAT service to IP\General. Add the two interfaces
to NAT (the one that reaches external is the PUBLIC interface) and the one
that
is one your net is the PRIVATE interface.

Is there a fool proof walkthrough that explains in the queens english 'how

We try to avoid that sort of language here <grin> -- but will help you
anyway.

You might try the above and describe what actually happens next time....