Very simple subnet mask question

Good evening to everyone in the Networking world!

I am more of an Active Directory person so please pardon what I am sure is a
really simple question. I am a bit embarrassed to ask this. Anyway, here
goes:

What device or software/service is responsible for handing out to the DHCP
Clients the subnet mask?

Here is what is happening.

I have inherited several environments. Most of them are Windows Server 2003
but there are a couple of Windows 2000 Server. The DHCP Server is in all
cases running on a Domain Controller. In fact, in most environment there is
only one Server (I know, I know....).

I have one client, for example, who has a 10.10.4.x range with a
255.255.252.0 subnet mask. DHCP hands out an IP lease which includes an IP
Address from 10.10.4.100 - 10.10.4.199. There are something like 45
computers in this environment. All of the clients (WIN2000 SP4 primarily
but some WINXP SP2) get all of the IP Address Lease information correctly
but have a Subnet Mask of 255.255.255.0 (and NOT the 255.255.252.0 that is
listed on the server).

I have not looked at the networking hardware yet.

Thanks all,

--
Cary W. Shultz
Roanoke, VA 24012

Hey Cary,

The DHCP "server" itself is responsible for giving out the proper
subnet. If you go to the dhcp administration and right click on the
scope and go to properties you will see the scope ip properties. Down
towards the bottom should be the mask. If it is not correct then you
have your culprit.

It is possible that the mask is greyed out. What you can do is then
either 1. Delete the existing scope and create a new one (right click,
new scope..) or add a scope.. either way it should let you put in
correct subnet.

If it shows the correct subnet, check the subnet of the servers NIC,
and are there any other DHCP servers?

gregg


On Tue, 28 Feb 2006 22:35:48 -0500, "Cary Shultz" <(E-Mail Removed)>
wrote:

>Good evening to everyone in the Networking world!
>
>I am more of an Active Directory person so please pardon what I am sure is a
>really simple question. I am a bit embarrassed to ask this. Anyway, here
>goes:
>
>What device or software/service is responsible for handing out to the DHCP
>Clients the subnet mask?
>
>Here is what is happening.
>
>I have inherited several environments. Most of them are Windows Server 2003
>but there are a couple of Windows 2000 Server. The DHCP Server is in all
>cases running on a Domain Controller. In fact, in most environment there is
>only one Server (I know, I know....).
>
>I have one client, for example, who has a 10.10.4.x range with a
>255.255.252.0 subnet mask. DHCP hands out an IP lease which includes an IP
>Address from 10.10.4.100 - 10.10.4.199. There are something like 45
>computers in this environment. All of the clients (WIN2000 SP4 primarily
>but some WINXP SP2) get all of the IP Address Lease information correctly
>but have a Subnet Mask of 255.255.255.0 (and NOT the 255.255.252.0 that is
>listed on the server).
>
>I have not looked at the networking hardware yet.
>
>Thanks all,

Greg,

You know something...I told everyone that I was embarrassed about this
question.

I have set up literally 1000 DHCP Servers in my time. Can not believe that
I missed this. DOH! I guess that I was simply 'too close' to the problem.
You know, overlooking the obvious and having a brainfart at the same time.

Thank you!

And, no, there are no other DHCP Servers....well, not any running on any
Windows systems. It would not surprise me if a Router or Firewall somewhere
in this specific place were running DHCP also. Do not think that there is.
I have been there only three times and have dealt with a bunch of other
issus (none of which would have been affected by DHCP). Like I said, I have
yet to get to the 'networking hardware' yet. There are too many software
problems at the moment!

Again, Thank you!

--
Cary W. Shultz
Roanoke, VA 24012

"Gregg K" <(E-Mail Removed)> wrote in message
news(E-Mail Removed)...
> Hey Cary,
>
> The DHCP "server" itself is responsible for giving out the proper
> subnet. If you go to the dhcp administration and right click on the
> scope and go to properties you will see the scope ip properties. Down
> towards the bottom should be the mask. If it is not correct then you
> have your culprit.
>
> It is possible that the mask is greyed out. What you can do is then
> either 1. Delete the existing scope and create a new one (right click,
> new scope..) or add a scope.. either way it should let you put in
> correct subnet.
>
> If it shows the correct subnet, check the subnet of the servers NIC,
> and are there any other DHCP servers?
>
> gregg
>
>
> On Tue, 28 Feb 2006 22:35:48 -0500, "Cary Shultz" <(E-Mail Removed)>
> wrote:
>
>>Good evening to everyone in the Networking world!
>>
>>I am more of an Active Directory person so please pardon what I am sure is
>>a
>>really simple question. I am a bit embarrassed to ask this. Anyway, here
>>goes:
>>
>>What device or software/service is responsible for handing out to the DHCP
>>Clients the subnet mask?
>>
>>Here is what is happening.
>>
>>I have inherited several environments. Most of them are Windows Server
>>2003
>>but there are a couple of Windows 2000 Server. The DHCP Server is in all
>>cases running on a Domain Controller. In fact, in most environment there
>>is
>>only one Server (I know, I know....).
>>
>>I have one client, for example, who has a 10.10.4.x range with a
>>255.255.252.0 subnet mask. DHCP hands out an IP lease which includes an
>>IP
>>Address from 10.10.4.100 - 10.10.4.199. There are something like 45
>>computers in this environment. All of the clients (WIN2000 SP4 primarily
>>but some WINXP SP2) get all of the IP Address Lease information correctly
>>but have a Subnet Mask of 255.255.255.0 (and NOT the 255.255.252.0 that is
>>listed on the server).
>>
>>I have not looked at the networking hardware yet.
>>
>>Thanks all,