Hi Everyone,

I have 2 DHCP servers on one LAN, the scope for both is 192.168.2.50-254.
The first DHCP server excludes addresses from 192.168.2.200-254 and the
second excludes addresses from 192.168.2.50-199. I want to know why does the
second DHCP server seems to be issuing all the new addresses when there are
plenty of ip addresses remaining on DHCP1. All of the clients gravitate
towards DHCP2 when there ip addresses are released. What can cause this, and
how can I force them to use DHCP1? Could the boot order of the servers have
something to do with it?

ps The clients can get ip addresses from DHCP1 but only when I take 2 off
the network. DHCP1 was the first server and they were all using it until I
recently configured a second.

They are both run on Domain controllers.
I have Windows 2000 server SP4

regards,
Sam

Sam wrote:
> Hi Everyone,
>
> I have 2 DHCP servers on one LAN, the scope for both is
> 192.168.2.50-254. The first DHCP server excludes addresses from
> 192.168.2.200-254 and the second excludes addresses from
> 192.168.2.50-199. I want to know why does the second DHCP server
> seems to be issuing all the new addresses when there are plenty of ip
> addresses remaining on DHCP1.

DHCP clients will always try to get the same IP address they had last
time...

> All of the clients gravitate towards
> DHCP2 when there ip addresses are released. What can cause this, and
> how can I force them to use DHCP1?

I'm not sure why it's important to do so - when DHCP2 has no more addresses
to hand out, the clients should get addresses from DHCP1. This is one reason
why it's nice to have more than one DHCP server....are you having any actual
problems, or are you just curious about why this is happening?

> Could the boot order of the
> servers have something to do with it?

Well, I suppose if you're rebooting your servers in the morning while users
are trying to boot up their workstations, they'll get an address from the
first DHCP server that answers their query.

>
> ps The clients can get ip addresses from DHCP1 but only when I take 2
> off the network. DHCP1 was the first server and they were all using
> it until I recently configured a second.

Is the DHCP1 server very busy? What's running on it?
>
> They are both run on Domain controllers.
> I have Windows 2000 server SP4
>
> regards,
> Sam

Hi Lanwench,

Thank you for replying. To answer your questions
1. I am not having any actual problems. I am just curious as to why DHCP2
is so popular.
2. DHCP1 is a global catalog server and a print server.

Regards

Sam

"Lanwench [MVP - Exchange]" wrote:

> Sam wrote:
> > Hi Everyone,
> >
> > I have 2 DHCP servers on one LAN, the scope for both is
> > 192.168.2.50-254. The first DHCP server excludes addresses from
> > 192.168.2.200-254 and the second excludes addresses from
> > 192.168.2.50-199. I want to know why does the second DHCP server
> > seems to be issuing all the new addresses when there are plenty of ip
> > addresses remaining on DHCP1.
>
> DHCP clients will always try to get the same IP address they had last
> time...
>
> > All of the clients gravitate towards
> > DHCP2 when there ip addresses are released. What can cause this, and
> > how can I force them to use DHCP1?
>
> I'm not sure why it's important to do so - when DHCP2 has no more addresses
> to hand out, the clients should get addresses from DHCP1. This is one reason
> why it's nice to have more than one DHCP server....are you having any actual
> problems, or are you just curious about why this is happening?
>
> > Could the boot order of the
> > servers have something to do with it?
>
> Well, I suppose if you're rebooting your servers in the morning while users
> are trying to boot up their workstations, they'll get an address from the
> first DHCP server that answers their query.
>
> >
> > ps The clients can get ip addresses from DHCP1 but only when I take 2
> > off the network. DHCP1 was the first server and they were all using
> > it until I recently configured a second.
>
> Is the DHCP1 server very busy? What's running on it?
> >
> > They are both run on Domain controllers.
> > I have Windows 2000 server SP4
> >
> > regards,
> > Sam
>
>
>

Sam wrote:
> Hi Lanwench,
>
> Thank you for replying. To answer your questions
> 1. I am not having any actual problems. I am just curious as to why
> DHCP2 is so popular.

It just happened to answer first. And clients will always attempt to get the
same IP address they had last time.

> 2. DHCP1 is a global catalog server and a print server.

Slower server in general?

I wouldn't worry about this, if it were me.

>
> Regards
>
> Sam
>
> "Lanwench [MVP - Exchange]" wrote:
>
>> Sam wrote:
>>> Hi Everyone,
>>>
>>> I have 2 DHCP servers on one LAN, the scope for both is
>>> 192.168.2.50-254. The first DHCP server excludes addresses from
>>> 192.168.2.200-254 and the second excludes addresses from
>>> 192.168.2.50-199. I want to know why does the second DHCP server
>>> seems to be issuing all the new addresses when there are plenty of
>>> ip addresses remaining on DHCP1.
>>
>> DHCP clients will always try to get the same IP address they had last
>> time...
>>
>>> All of the clients gravitate towards
>>> DHCP2 when there ip addresses are released. What can cause this,
>>> and how can I force them to use DHCP1?
>>
>> I'm not sure why it's important to do so - when DHCP2 has no more
>> addresses to hand out, the clients should get addresses from DHCP1.
>> This is one reason why it's nice to have more than one DHCP
>> server....are you having any actual problems, or are you just
>> curious about why this is happening?
>>
>>> Could the boot order of the
>>> servers have something to do with it?
>>
>> Well, I suppose if you're rebooting your servers in the morning
>> while users are trying to boot up their workstations, they'll get an
>> address from the first DHCP server that answers their query.
>>
>>>
>>> ps The clients can get ip addresses from DHCP1 but only when I take
>>> 2 off the network. DHCP1 was the first server and they were all
>>> using it until I recently configured a second.
>>
>> Is the DHCP1 server very busy? What's running on it?
>>>
>>> They are both run on Domain controllers.
>>> I have Windows 2000 server SP4
>>>
>>> regards,
>>> Sam

Hi Lanwench,

Thanks for the info.

Best regards
Sam

"Lanwench [MVP - Exchange]" wrote:

> Sam wrote:
> > Hi Lanwench,
> >
> > Thank you for replying. To answer your questions
> > 1. I am not having any actual problems. I am just curious as to why
> > DHCP2 is so popular.
>
> It just happened to answer first. And clients will always attempt to get the
> same IP address they had last time.
>
> > 2. DHCP1 is a global catalog server and a print server.
>
> Slower server in general?
>
> I wouldn't worry about this, if it were me.
>
> >
> > Regards
> >
> > Sam
> >
> > "Lanwench [MVP - Exchange]" wrote:
> >
> >> Sam wrote:
> >>> Hi Everyone,
> >>>
> >>> I have 2 DHCP servers on one LAN, the scope for both is
> >>> 192.168.2.50-254. The first DHCP server excludes addresses from
> >>> 192.168.2.200-254 and the second excludes addresses from
> >>> 192.168.2.50-199. I want to know why does the second DHCP server
> >>> seems to be issuing all the new addresses when there are plenty of
> >>> ip addresses remaining on DHCP1.
> >>
> >> DHCP clients will always try to get the same IP address they had last
> >> time...
> >>
> >>> All of the clients gravitate towards
> >>> DHCP2 when there ip addresses are released. What can cause this,
> >>> and how can I force them to use DHCP1?
> >>
> >> I'm not sure why it's important to do so - when DHCP2 has no more
> >> addresses to hand out, the clients should get addresses from DHCP1.
> >> This is one reason why it's nice to have more than one DHCP
> >> server....are you having any actual problems, or are you just
> >> curious about why this is happening?
> >>
> >>> Could the boot order of the
> >>> servers have something to do with it?
> >>
> >> Well, I suppose if you're rebooting your servers in the morning
> >> while users are trying to boot up their workstations, they'll get an
> >> address from the first DHCP server that answers their query.
> >>
> >>>
> >>> ps The clients can get ip addresses from DHCP1 but only when I take
> >>> 2 off the network. DHCP1 was the first server and they were all
> >>> using it until I recently configured a second.
> >>
> >> Is the DHCP1 server very busy? What's running on it?
> >>>
> >>> They are both run on Domain controllers.
> >>> I have Windows 2000 server SP4
> >>>
> >>> regards,
> >>> Sam
>
>
>

You're welcome.

Sam wrote:
> Hi Lanwench,
>
> Thanks for the info.
>
> Best regards
> Sam
>
> "Lanwench [MVP - Exchange]" wrote:
>
>> Sam wrote:
>>> Hi Lanwench,
>>>
>>> Thank you for replying. To answer your questions
>>> 1. I am not having any actual problems. I am just curious as to
>>> why DHCP2 is so popular.
>>
>> It just happened to answer first. And clients will always attempt to
>> get the same IP address they had last time.
>>
>>> 2. DHCP1 is a global catalog server and a print server.
>>
>> Slower server in general?
>>
>> I wouldn't worry about this, if it were me.
>>
>>>
>>> Regards
>>>
>>> Sam
>>>
>>> "Lanwench [MVP - Exchange]" wrote:
>>>
>>>> Sam wrote:
>>>>> Hi Everyone,
>>>>>
>>>>> I have 2 DHCP servers on one LAN, the scope for both is
>>>>> 192.168.2.50-254. The first DHCP server excludes addresses from
>>>>> 192.168.2.200-254 and the second excludes addresses from
>>>>> 192.168.2.50-199. I want to know why does the second DHCP server
>>>>> seems to be issuing all the new addresses when there are plenty of
>>>>> ip addresses remaining on DHCP1.
>>>>
>>>> DHCP clients will always try to get the same IP address they had
>>>> last time...
>>>>
>>>>> All of the clients gravitate towards
>>>>> DHCP2 when there ip addresses are released. What can cause this,
>>>>> and how can I force them to use DHCP1?
>>>>
>>>> I'm not sure why it's important to do so - when DHCP2 has no more
>>>> addresses to hand out, the clients should get addresses from DHCP1.
>>>> This is one reason why it's nice to have more than one DHCP
>>>> server....are you having any actual problems, or are you just
>>>> curious about why this is happening?
>>>>
>>>>> Could the boot order of the
>>>>> servers have something to do with it?
>>>>
>>>> Well, I suppose if you're rebooting your servers in the morning
>>>> while users are trying to boot up their workstations, they'll get
>>>> an address from the first DHCP server that answers their query.
>>>>
>>>>>
>>>>> ps The clients can get ip addresses from DHCP1 but only when I
>>>>> take 2 off the network. DHCP1 was the first server and they were
>>>>> all using it until I recently configured a second.
>>>>
>>>> Is the DHCP1 server very busy? What's running on it?
>>>>>
>>>>> They are both run on Domain controllers.
>>>>> I have Windows 2000 server SP4
>>>>>
>>>>> regards,
>>>>> Sam