Networks

Ask something
Discussion Locked

Adding a Win2k DC to small network

0 helpful
3 replies

by x7jrgms

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Current Network:
1)Router assigned static IP/PD/SD/Gateway etc. from ISP. Static IP is tied to an internet domain name. Router sits behind a Cisco 675 DSL modem.

2) Several XP Prof. workstations in a workgroup and an NT4.0 server (stand-alone) getting IPs from the router.

3) Want to nuke the NT4.0 server and replace with a Win2k server.

Would like the New Network to be:
Win2k server is DC/DNS to manage User database and act as file/application server. Would also want this server to host a website(s) that would be passed through the router. The router would have the static IP which is mapped to the internet domain name for website. The router will pass thru port 80 to the Win2k IIS server.

My question is: How do I configure the Win2k server IP-wise.
1) Do I assign a static IP/internal subnet so the other internal client machines can see it as a DC and get a dynamic IP from the router for NAT and internet access for the win2k server?

2) Do I install 2 NIC's and assign1 of them a static IP/configure for internal subnet and use the other NIC for the internet using DHCP from the router?

3) If I create an interanl subnet, do I need another router configured as a bridge or switch?

I've seen many possibilities surfing around, but all have been bits and pieces and not a total solution to what I'm looking to do.

Still surfing...

THX-

3 replies

by timwalsh

Here's the best way to do this:

When you create your Win2K DC, give it a static IP address using one of the private IP address ranges (most common is usually 192.168.x.x). For Primary DNS, have the DC point to itself.

Install DNS on this server and create a lookup zone for your domain. Set up your ISP's DNS server(s) in the forwarders section.

Install DHCP on your DC and disable this function on the router.

Point all clients to your DC as the primary DNS server.

Here is the endresult:

Although your router will no longer act as a DHCP server, it will still act as a NAT box and your default Gateway. The reason that you don't want the router to handle DHCP is that it will pass DNS info from your ISP ans opposed to DNS info related to your internal network.

All DNS queries related to domain resources will be resolved by your internal DNS server and will not be forwarded. All DNS queries relating to external resources (i.e. the Internet) will be forwarded to the ISP's DNS server for resolution.

You won't need dual NICs. You won't need another router. A static IP need only be assigned to your DC (and webserver if it is hosted on a different server. You can use the registered domain name as your internal domain name.

If your ISP is currently hosting a website for your, make sure they make the appropriate DNS changes when you start hosting the website.

Hoppe this answers your questions.

by x7jrgms

Thanks for the info. It took me a couple stabs to get it right, but generally the info you supplied with a generous dose of support.microsoft.com KB articles got it working.

This discussion is closed to new replies.