Subnet Mask for Scope Different Than Subnet for Network

[CHANGE USERNAME to westes]

On our lab's Windows 2000 RC2 Adv Server domain controller, the subnet mask
for the DHCP scope is showing up as 255.255.255.128. The subnet for the
network is 255.255.255.0. What is mysterious is that the subnet mask for
the scope is set to a *read-only* field, and we cannot change it, inside of
the DHCP scope properties.

What would cause the above to happen, and how do we reset the DHCP's scope
to the same subnet mask as the network that it serves?

--
Will

NOTE: To reply, CHANGE the username to westes AT uscsw.com

[Dean Wells]

Hi CHANGE USERNAME to westes ... or maybe Will just jokin' :-)

The subnet mask of a scope cannot be changed via the GUI after creation. I
would imagine your subnet mask is outside the definition of a standard class
(one bit past class C) because during it's creation the Administrator
clicked the subnet mask length "up" button one too many times.

Just a guess.

--
Deano

"CHANGE USERNAME to westes" <junk...@uscsw.com> wrote in message
news:uFGGzbSQ$GA....@cppssbbsa02.microsoft.com...

[CHANGE USERNAME to westes]

What is the logic that makes this permanent? It certainly doesn't allow
for errors.

--
Will

NOTE: To reply, CHANGE the username to westes AT uscsw.com

"Dean Wells" <dwe...@msetechnology.com> wrote in message
news:efspLeeQ$GA.273@cppssbbsa05...

[James Humphreys]

Do you want to start over with your IP addressing ?

To do this :

1. Stop your scope
2. Delete your scope
3. Reboot your server
4. De-Authorize the dhcp
5. reboot the server
6. Create a new scope with your new settings
7. Activate the scope
8. Authorize the server
9. Reboot the server

DNS will automatically re-write new (A) pointers for the new scope / IP
leases, but you can delete the old IP leases that may still be in DNS.

You may also want to create a reverse lookup in DNS.

i.e. your IP= 10.10.1.1, reverse zone will be 10.in-addr.arpa, (you can
basically copy the 127.0.0.1 reverse lookup, but with you server IP)