How top give one dhcp server preference

We had a rogue dhcp server that caused havoc for a few hours. our network
was a 10.1.50.x/24 and this dhcp server was serving 192.168.120.x. We
found it and turned it off. (wasnt intentional- just poor planning with a
print server)
Question, is there a method to force clients to look at a given dhcp
server? Im interested in what anybody else has done in similar scenario.
I was also wondering if a company gives public wifi, could anybody access
with a dhcp server and cause the same kind of problems??

Thanks in advance

--
Craig

"MSNews" <(E-Mail Removed)> wrote in message
news:esmA$(E-Mail Removed)...
> We had a rogue dhcp server that caused havoc for a few hours. our
> network was a 10.1.50.x/24 and this dhcp server was serving 192.168.120.x.
> We found it and turned it off. (wasnt intentional- just poor planning
> with a print server)
> Question, is there a method to force clients to look at a given dhcp
> server? Im interested in what anybody else has done in similar scenario.
> I was also wondering if a company gives public wifi, could anybody access
> with a dhcp server and cause the same kind of problems??
>
> Thanks in advance
>
> --
> Craig
>

No, there isn't really any way around the problem. DHCP requests are
issued at a very low level, so they can't be controlled by anything in the
OS. A request is sent out by broadcast and any DHCP server will reply with
an offer. The client usually accepts the first offer it receives.

That really sucks. While recent windows servers have the ability to
authorize a dhcp server, they have no way of telling clients not to listen
to any unauthorized dhcp server if it is NT or not MS..

craig
"Bill Grant" <not.available@online> wrote in message
news:%23RFSy$(E-Mail Removed)...
>
>
> "MSNews" <(E-Mail Removed)> wrote in message
> news:esmA$(E-Mail Removed)...
>> We had a rogue dhcp server that caused havoc for a few hours. our
>> network was a 10.1.50.x/24 and this dhcp server was serving
>> 192.168.120.x. We found it and turned it off. (wasnt intentional- just
>> poor planning with a print server)
>> Question, is there a method to force clients to look at a given dhcp
>> server? Im interested in what anybody else has done in similar
>> scenario.
>> I was also wondering if a company gives public wifi, could anybody access
>> with a dhcp server and cause the same kind of problems??
>>
>> Thanks in advance
>>
>> --
>> Craig
>>
>
> No, there isn't really any way around the problem. DHCP requests are
> issued at a very low level, so they can't be controlled by anything in the
> OS. A request is sent out by broadcast and any DHCP server will reply with
> an offer. The client usually accepts the first offer it receives.
>
>

"MSNews" <(E-Mail Removed)> wrote in message
news:%(E-Mail Removed)...
> That really sucks. While recent windows servers have the ability to
> authorize a dhcp server, they have no way of telling clients not to listen
> to any unauthorized dhcp server if it is NT or not MS..

What you want isn't possible.
It has nothing to do with MS,...MS didn't invent the DHCP System and the
standards it operates by.

There is no way to "tell" a client to use a certain DHCP because they don't
have an IP Address yet,...there is no way to communicate that information to
them,....once they have an IP it is too late because they have already
chosen a DHCP Server by that point.

--
Phillip Windell

The views expressed, are my own and not those of my employer, or Microsoft,
or anyone else associated with me, including my cats.
-----------------------------------------------------