dns/dhcp setup

I know i'm missing something stupid here, but I'm playing around with windows
2003 enterprise edition, and I can't seem to get the settings right. I've
setup a few sbs2003 servers with no problem, but this one's a ___. Anyway,
I've setup the server behind a hardware firewall (just so I could give the
nic on the server a static IP), I've got 2 cards in the server. one going to
the firewall, and one going to a hub so that workstations can connect to the
server. Setup DHCP, no problem stations getting IP addresses. The server
gets on the internet no problem. Setup DNS as 10.0.0.1, which is the
internal card, setup the external to 192.168.2.50. Setup forwarders to
192.168.2.1 (which is the router's ip).Now... I can ping the server from a
workstation using 10.0.0.1. I can ping the second nic from workstations
using 192.168.2.50. I can't ping the router from the workstation which would
be going through the server and then to 192.168.2.1. I think if I can get it
to the point that the workstation can ping the router, then I'll be ready to
move on to testing the other things I'd like to explore on the server, but
right now, I just want to get the stations to be able to get to the internet.

Thx

The simplest way to do it is to enable RRAS on the server as a NAT
router. The machines on the 10.0.0.0 subnet will then share the server's
192.168.2.50 connection to the Internet. Set the 10.0.0.x machines to use
10.0.0.1 as their default gateway.

Without NAT, you would need to enable IP routing on the server and
change the routing on the 192.168.2.0 subnet, so that it would know which
router to use to find the 10.0.0.0 subnet.
(eg add a static route to the router at 192.168.2.1 to forward traffic for
10.0.0.0 to the RRAS router.

10.0.0.0 netmask 192.168.2.50 )

For DNS you can use the option in NAT to relay DNS requests. Set this
on, and set the client machines to use 10.0.0.1 as their DNS server.

If you want to use DNS forwarding instead, do not enable the option in
NAT. Set the DNS server to forward to a public DNS server.

Crown Royal wrote:
> I know i'm missing something stupid here, but I'm playing around with
> windows 2003 enterprise edition, and I can't seem to get the settings
> right. I've setup a few sbs2003 servers with no problem, but this
> one's a ___. Anyway, I've setup the server behind a hardware
> firewall (just so I could give the nic on the server a static IP),
> I've got 2 cards in the server. one going to the firewall, and one
> going to a hub so that workstations can connect to the server. Setup
> DHCP, no problem stations getting IP addresses. The server gets on
> the internet no problem. Setup DNS as 10.0.0.1, which is the
> internal card, setup the external to 192.168.2.50. Setup forwarders
> to 192.168.2.1 (which is the router's ip).Now... I can ping the
> server from a workstation using 10.0.0.1. I can ping the second nic
> from workstations using 192.168.2.50. I can't ping the router from
> the workstation which would be going through the server and then to
> 192.168.2.1. I think if I can get it to the point that the
> workstation can ping the router, then I'll be ready to move on to
> testing the other things I'd like to explore on the server, but right
> now, I just want to get the stations to be able to get to the
> internet.
>
> Thx

Thx, I figured that out after walking a way from it for a bit, I knew it
would be something I missed, I ran RRAS (can't beleive I missed that duh..).
Worked fine after that

"Bill Grant" wrote:

> The simplest way to do it is to enable RRAS on the server as a NAT
> router. The machines on the 10.0.0.0 subnet will then share the server's
> 192.168.2.50 connection to the Internet. Set the 10.0.0.x machines to use
> 10.0.0.1 as their default gateway.
>
> Without NAT, you would need to enable IP routing on the server and
> change the routing on the 192.168.2.0 subnet, so that it would know which
> router to use to find the 10.0.0.0 subnet.
> (eg add a static route to the router at 192.168.2.1 to forward traffic for
> 10.0.0.0 to the RRAS router.
>
> 10.0.0.0 netmask 192.168.2.50 )
>
> For DNS you can use the option in NAT to relay DNS requests. Set this
> on, and set the client machines to use 10.0.0.1 as their DNS server.
>
> If you want to use DNS forwarding instead, do not enable the option in
> NAT. Set the DNS server to forward to a public DNS server.
>
> Crown Royal wrote:
> > I know i'm missing something stupid here, but I'm playing around with
> > windows 2003 enterprise edition, and I can't seem to get the settings
> > right. I've setup a few sbs2003 servers with no problem, but this
> > one's a ___. Anyway, I've setup the server behind a hardware
> > firewall (just so I could give the nic on the server a static IP),
> > I've got 2 cards in the server. one going to the firewall, and one
> > going to a hub so that workstations can connect to the server. Setup
> > DHCP, no problem stations getting IP addresses. The server gets on
> > the internet no problem. Setup DNS as 10.0.0.1, which is the
> > internal card, setup the external to 192.168.2.50. Setup forwarders
> > to 192.168.2.1 (which is the router's ip).Now... I can ping the
> > server from a workstation using 10.0.0.1. I can ping the second nic
> > from workstations using 192.168.2.50. I can't ping the router from
> > the workstation which would be going through the server and then to
> > 192.168.2.1. I think if I can get it to the point that the
> > workstation can ping the router, then I'll be ready to move on to
> > testing the other things I'd like to explore on the server, but right
> > now, I just want to get the stations to be able to get to the
> > internet.
> >
> > Thx
>
>
>