Windows DHCP Server

I've three 2003 DC's in one Domain at three separate sites. I've been using a
router at each site to handle the DHCP server role. The routers are
configured to forward all DNS requests back to the sites DC. Without this,
my XP clients take forever to find the DC to authenticate with. I'm doing
this so that if the DC is down, the clients can still access the Internet.
The router will use the ISP as a backup DNS in case the server is down.

I'm wondering if this is the right way to go. One problem is I'm reliant on
a router that is capable of forwarding all DNS requests back to the server.
If my router should need to be replaced someday, I may not find a router that
has the ability to forward DNS requests back to the server and therefore the
XP clients will not be able to logon in a timely manner.

If I enable the DHCP server role on Window 2003, then I'm reliant on the
server to be running in order for the clients to get on the network.

If it were possible to have both the router and 2003 be DHCP servers on the
same network, then I guess that would be ideal. But I don’t know if that
will work or not. If it did, then could I have a second DC on the same
network as a DHCP server thus giving me three DHCP servers?

Any advice on how this should be configured?
---
Bob

Hello Bob,

Make all your DC's Active directory DNS server and Global catalog servers.
Also configure Sites and services to 3 different sites and move the server
to the equivalent site. So the clients just authenticate to the server in
theire own site.
Did you have an internet connection on each site or only one? The forwarder
should be configured to your ISP's DNS and your domain DNS servers should
point only to your own DNS domain.
Also configure on each site a DHCP server for the subnet from the site. The
clients should only get the primary DNS from it site and the secondary from
another site.

Best regards

Myweb
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.

> I've three 2003 DC's in one Domain at three separate sites. I've been
> using a router at each site to handle the DHCP server role. The
> routers are configured to forward all DNS requests back to the sites
> DC. Without this, my XP clients take forever to find the DC to
> authenticate with. I'm doing this so that if the DC is down, the
> clients can still access the Internet. The router will use the ISP as
> a backup DNS in case the server is down.
>
> I'm wondering if this is the right way to go. One problem is I'm
> reliant on a router that is capable of forwarding all DNS requests
> back to the server. If my router should need to be replaced someday,
> I may not find a router that has the ability to forward DNS requests
> back to the server and therefore the XP clients will not be able to
> logon in a timely manner.
>
> If I enable the DHCP server role on Window 2003, then I'm reliant on
> the server to be running in order for the clients to get on the
> network.
>
> If it were possible to have both the router and 2003 be DHCP servers
> on the same network, then I guess that would be ideal. But I don't
> know if that will work or not. If it did, then could I have a second
> DC on the same network as a DHCP server thus giving me three DHCP
> servers?
>
> Any advice on how this should be configured? --- Bob
>

Hi Myweb,

I am doing everything you write in your fist paragraph.

And yes, I have an internet connection at each site. (a h/w router and cable
modem).

Windows Server DNS has its forwarders configured to forward to the ISP's DNS.

I don't know how to have my domain DNS servers point to any domain other
than mine, so I guess that is fine too. (I only have one Domain).

I lost you at your last sentence where you write:

"Also configure on each site a DHCP server for the subnet from the site. The
clients should only get the primary DNS from it site and the secondary from
another site"

What DHCP server are you writing about? I only have the DHCP server that is
built into the h/w router. I have a $1K Symantec routers at each site, but
I'd rather have $50 Belkins.

So the question is: Can I use inexpensive Staples/OfficeMax routers as DHCP
servers or would I be much better off enabling the DHCP server built into
Windows 2003 Server? (especially when you consider that the routers are up
100% of the time whereas Windows Server could be down for a days for any
number of reasons). If the Window DHCP server is down, the users can't do
anything. But if I have a h/w router, the users can at least get to the
internet.

The other question is: Can I have the best of both worlds? Keep the the
router DHCP server + Windows DHCP server running at the same time? I suspect
this won't work, but I thought I'd ask just the same.

Thanks!
--
Bob

A common technique for running two DHCP servers on the same network is to
use the 80/20 rule.

http://www.microsoft.com/technet/pro....mspx?mfr=true

"Bob" <86c6c2e6-(E-Mail Removed)> wrote in message
news:03CB57D3-5F82-4BA0-8D10-(E-Mail Removed)...
> Hi Myweb,
>
> I am doing everything you write in your fist paragraph.
>
> And yes, I have an internet connection at each site. (a h/w router and
> cable
> modem).
>
> Windows Server DNS has its forwarders configured to forward to the ISP's
> DNS.
>
> I don't know how to have my domain DNS servers point to any domain other
> than mine, so I guess that is fine too. (I only have one Domain).
>
> I lost you at your last sentence where you write:
>
> "Also configure on each site a DHCP server for the subnet from the site.
> The
> clients should only get the primary DNS from it site and the secondary
> from
> another site"
>
> What DHCP server are you writing about? I only have the DHCP server that
> is
> built into the h/w router. I have a $1K Symantec routers at each site,
> but
> I'd rather have $50 Belkins.
>
> So the question is: Can I use inexpensive Staples/OfficeMax routers as
> DHCP
> servers or would I be much better off enabling the DHCP server built into
> Windows 2003 Server? (especially when you consider that the routers are
> up
> 100% of the time whereas Windows Server could be down for a days for any
> number of reasons). If the Window DHCP server is down, the users can't do
> anything. But if I have a h/w router, the users can at least get to the
> internet.
>
> The other question is: Can I have the best of both worlds? Keep the the
> router DHCP server + Windows DHCP server running at the same time? I
> suspect
> this won't work, but I thought I'd ask just the same.
>
> Thanks!
> --
> Bob

Thanks Bill,

You and Myweb gave me the courage to enable the DHCP server role.

In both my h/w router and Windows DHCP, I have reserved IP addresses for the
clients.

I left both the h/w and s/w dhcp servers running. Upon client power on, my
first test resulted in the client forgoing its prior IP address assigned by
the h/w router and taking the one reserved for it in Windows dhcp server.
This to me is ideal as it leaves the h/w dhcp as backup. I suspect this will
be random at best however.

One question: I noticed that "ipconfig /all" run on the client now states
that "IP Routing Enabled" is set to "Yes". Before this change, it was always
"No".

What is "IP Routing" (on the client)? How do I control this setting at the
Windows DHCP Server?
--
Bob

"Bob" <86c6c2e6-(E-Mail Removed)> wrote in message
news:0E1E8B4B-383E-4D87-998F-(E-Mail Removed)...
> Thanks Bill,
>
> You and Myweb gave me the courage to enable the DHCP server role.
>
> In both my h/w router and Windows DHCP, I have reserved IP addresses for
> the
> clients.
>
> I left both the h/w and s/w dhcp servers running. Upon client power on,
> my
> first test resulted in the client forgoing its prior IP address assigned
> by
> the h/w router and taking the one reserved for it in Windows dhcp server.
> This to me is ideal as it leaves the h/w dhcp as backup. I suspect this
> will
> be random at best however.
>
> One question: I noticed that "ipconfig /all" run on the client now states
> that "IP Routing Enabled" is set to "Yes". Before this change, it was
> always
> "No".
>
> What is "IP Routing" (on the client)? How do I control this setting at
> the
> Windows DHCP Server?
> --
> Bob
IP routing is one of the DHCP options. Enabling IP routing allows the
machine to forward traffic from one network to another (ie it can act as an
IP router). You do not need it on your client machines. Just change the
setting from enable to disable in your DHCP setup.

Thanks Myweb and Bill!

Mike Luo

Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security

================================================== ===
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.