XP Client cannot access internet through WS 2003 with NAT

I have WS 2003 set up in my office with 5 other computers around the house.
All of them run XP pro (except my MAC). I have Active Directory installed
and use WS 2003 set up as a DNS Server, DHCP server, File Server, Print
Server, and Remote Access /VPN Server. I have 2 NICs in the server. One is
connected to my cable modem (labeled Public) and the other is connected to a
switch with all PC's connected to the switch (labeled Private). I am able to
log onto my domain from my client computers and access my network just fine,
but my client PC's cannot access the internet for some reason. I can only
get on the internet from my WS 2003 machine. I'm sure there is a simple
explaination, but I cannot figure it out. Could someone please lend me a
hand with this?

Thanks,

Tim Cummings

Tim Cummings wrote:
> I have WS 2003 set up in my office with 5 other computers around the
> house. All of them run XP pro (except my MAC). I have Active
> Directory installed and use WS 2003 set up as a DNS Server, DHCP
> server, File Server, Print Server, and Remote Access /VPN Server. I
> have 2 NICs in the server. One is connected to my cable modem
> (labeled Public) and the other is connected to a switch with all PC's
> connected to the switch (labeled Private). I am able to log onto my
> domain from my client computers and access my network just fine, but
> my client PC's cannot access the internet for some reason. I can
> only get on the internet from my WS 2003 machine. I'm sure there is
> a simple explaination, but I cannot figure it out. Could someone
> please lend me a hand with this?
>
> Thanks,
>
> Tim Cummings

Multihomed DCs can be a real PITA and I don't recommend them.
I strongly suggest you get rid of one & get yourself a decent hardware
firewall/gateway appliance that does NAT. You can pick up an FR114P for
about $80, last time I checked.

I agree with Lanwench. Running an AD DC as a multihomed router is not a
great idea. Using some other machine/device as the router is better.

If you want to make the current setup work, there are two things to
consider. Routing and DNS.

The Internet router will not know how to reach your private subnet
unless you tell it how. The simplest way is to add a static route to this
router (if you can) to forward traffic for the private LAN to the RRAS
router.

Internet
|
router
10.0.0.1
|
10.0.0.2 dg 10.0.0.1
router
192.168.0.1 dg blank
|
workstations
192.168.0.x dg 192.168.0.1

In this case, the static route would be
192.168.0.0 255.255.255.0 10.0.0.2

As you are running AD, your clients should be configured to use the
local server for DNS. For the client machines to resolve "foreign" URLs,
you will need to enable forwarding on your DNS server, to send these
requests on to a public DNS server (such as your ISP).

"Tim Cummings" <(E-Mail Removed)> wrote in message
news:78BCB8D9-9A4A-42CA-BF7B-(E-Mail Removed)...
>I have WS 2003 set up in my office with 5 other computers around the house.
> All of them run XP pro (except my MAC). I have Active Directory installed
> and use WS 2003 set up as a DNS Server, DHCP server, File Server, Print
> Server, and Remote Access /VPN Server. I have 2 NICs in the server. One
> is
> connected to my cable modem (labeled Public) and the other is connected to
> a
> switch with all PC's connected to the switch (labeled Private). I am able
> to
> log onto my domain from my client computers and access my network just
> fine,
> but my client PC's cannot access the internet for some reason. I can only
> get on the internet from my WS 2003 machine. I'm sure there is a simple
> explaination, but I cannot figure it out. Could someone please lend me a
> hand with this?
>
> Thanks,
>
> Tim Cummings