DHCP scopes not being deleted?

Hi all,

I have one DHCP server on a Windows Server 2003 box.

I am making some changes to the architecture of the small business network.
I want *my* PC's to have a specific range, and I will actually create
reservations for them. The "regular" user PCs can get other IPs as needed,
same for incoming VPN connections.

I first deleted the existing scope. I then created a new scope with a
limited number of IP addresses (from .190 to .199). I assigned reservations
for my machines and excluded the IP addresses that were not in use (so as to
avoid user machines taking my IPs).

I then wanted to create another scope (.100 to .189), but I can't because
the DHCP server says that the address range and mask conflict with an
existing scope. Months ago, I did indeed configure a scope that used
something like that range on that box, but have long since deleted that
scope. So, then I tried to configure the range I had previously (.200 to
..249), and that doesn't work either, it fails with the same error.

Reconciling doesn't help the issue. Stopping and restaring the DHCP service
doesn't help either.

How can I fix this?

--


Sven.

OK, that's an RTFM issue ;o)

--


Sven.

"SA" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Hi all,
>
> I have one DHCP server on a Windows Server 2003 box.
>
> I am making some changes to the architecture of the small business
network.
> I want *my* PC's to have a specific range, and I will actually create
> reservations for them. The "regular" user PCs can get other IPs as needed,
> same for incoming VPN connections.
>
> I first deleted the existing scope. I then created a new scope with a
> limited number of IP addresses (from .190 to .199). I assigned
reservations
> for my machines and excluded the IP addresses that were not in use (so as
to
> avoid user machines taking my IPs).
>
> I then wanted to create another scope (.100 to .189), but I can't because
> the DHCP server says that the address range and mask conflict with an
> existing scope. Months ago, I did indeed configure a scope that used
> something like that range on that box, but have long since deleted that
> scope. So, then I tried to configure the range I had previously (.200 to
> .249), and that doesn't work either, it fails with the same error.
>
> Reconciling doesn't help the issue. Stopping and restaring the DHCP
service
> doesn't help either.
>
> How can I fix this?
>
> --
>
>
> Sven.
>
>

"SA" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> I first deleted the existing scope. I then created a new scope with a
> limited number of IP addresses (from .190 to .199). I assigned
reservations
> for my machines and excluded the IP addresses that were not in use (so as
to
> avoid user machines taking my IPs).

You shouldn't do it that way to begin with. Use the full IP Range when
creating the Scope. Use Exclusions to limit which IP# are given out. If you
don't do it that way you will have to completely delete and recreate the
scopes everytime you make a change.

Example: [desire.192 to .199 as usable range]

192.168.1.1 -- 192.168.1.254 (full range used)
Exclusion = 192.168.1.1 -- 192.168.1.191
Exclusion = 192.168.1.200 -- 192.168.1.254


You decide later that you also need .100 to .189, then you just adjust the
first listed Exclusion which would give you this:

192.168.1.1 -- 192.168.1.254 (full range used)
Exclusion = 192.168.1.1 -- 192.168.1.99
Exclusion = 192.168.1.200 -- 192.168.1.254

--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com