=?Utf-8?B?UEwy?= <(E-Mail Removed)> wrote in
news:E3CD863D-AA03-4849-BB22-(E-Mail Removed):
> Hi,
>
> Our current setup has 2 DC's with DHCP running on both boxes. My
> predecessor has setup the same scope range on both DC's. Scope is
> 192.0.0.0 (it's not a valid class C address, but that's the way it was
> setup)
>
> I've read the tech artice from the Windows 2003 Tech Center (DHCP best
> practice).
> The article recommends a 80/20 split. We do sometimes get bad
> addresses shown in DHCP from one of the DC's. We also sometimes get IP
> conflicts on client desktops. I've been advised it's not possible to
> have the same scope on each of the DC's. However, that's the way it
> was setup
>
> Can you advise please? Should I split the scope? If so, how?
>
> thanks, PL
>
>
>
Hi there --
You can leave the scopes as-is but just add an exclusion range to each
scope.
A lot of customers prefer a 50-50 split rather than 80-20, so you might
consider this.
The way to do it is this:
On server 1, create an exclusion range of IP addresses from 192.0.0.1
through 192.0.0.125. Once you do this, the server will only renew or lease
addresses from the remaining address pool, which is 192.0.0.126 through
192.0.0.254.
On server 2, create an exclusion range of IP addresses from 192.0.0.126
through 192.0.0.254. Once you do this, the server will only renew or lease
addresses from the remaining address pool, which is 192.0.0.1 through
192.0.0.125.
If you do this, both servers are allocating IP addresses from the same
address range, but they are not allocating the same addresses.
--
James McIllece, Microsoft
Please do not send email directly to this alias. This is my online account
name for newsgroup participation only.
This posting is provided "AS IS" with no warranties, and confers no rights.
|