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

  • Thread starter Thread starter 1stuk
  • Start date Start date
1

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
 
Sorry to say that I don't have a step by step instructions for this. Just a
few thing you might want to check:
1. Is your DNS server on your DC as well? You will need to configure your
DNS server to use your ISP DNS server as the forwarder.
2. Can you ping an external IP on your DC? This will helps to determine if
your forwarding is set up properly. If you can, the problem most probably
lies between the client and the DC.
3. Run 'route print' on your DC and check if your routing table is
configured properly. Do the same for your client machines.
4. On the client machine, ping (a) the DC internal NIC IP, (b) the DC
external NIC IP, (c) the default gateway (and DNS) provided by your ISP.
Each of these will help you to zoom down the problem.
5. Each machine can only have one default gateway. The default gateway for
the internal NIC should be EMPTY and the dafault gateway for the external
NIC should be pointing to the one given by your ISP.

Please also provide a 'ipconfig/all' and 'route print' for one of the client
and the DC so that it's easier for others to help you.

rgds.
 
ys@work said:
Sorry to say that I don't have a step by step instructions for this. Just a
few thing you might want to check:
1. Is your DNS server on your DC as well? You will need to configure your
DNS server to use your ISP DNS server as the forwarder.
Click to expand...

Yes, the forwarder tab has the isp dns servers in there.
While the servers IP address points to its self in the TCP/IP DNS primary
record.
In other words the DC's IP xxx.xxx.xxx.123 points back to it-self as the DNS
record ==> DNS 1 xxx.xxx.xxx.123, while the ISP's DNS server IPs are in the
forwarding tab.
2. Can you ping an external IP on your DC? This will helps to determine if
your forwarding is set up properly. If you can, the problem most probably
lies between the client and the DC.
Click to expand...

The domain controller work fine with internet connectivity, it has exchange
2000 running on it and emails can be retrieved and sent out. Web browser
within the server works fine and all other internet reliant applications
also work fine.
 
Back
Top