Force workstation to use a specific DHCP server ?

[Tang]

Hello!

Does anyone know of a way to force a workstation to use a specific DHCP
server ? I'm just into a situation where a Windows Server 2003 have DHCP
server active and the phone system also have DHCP server active.

Several workstations keeps getting their IP information from the phone DHCP
server rather than the Windows 2003 DHCP server.

I know the real fix is to kill the DHCP server on the phone system but our
phone provider need to use the DHCP server for the phone configuration.

Any ideas are welcome.

Thank you !

Tanguy Brasseur

[Ace Fekay [MCT]]

"Tang" <Ta...@discussions.microsoft.com> wrote in message
news:51AC41F5-1EF9-4E31...@microsoft.com...

You already know the answer. And no, you can't make a machine use a specific
DHCP. You can play around with DHCP vendor and other options, but to please
the phone vendor? Ask the phone vendor what specifically is the phone system
looking for DHCP options-wise.

If they can't answer that question, then your only course of action is to
put the phone system on a separate switch with their own subnet. I think I
would have probably done that just to keep them separate, however I've
worked in environments with an Avaya phone system on the same subnet as
other machines, and we simply used Windows DHCP and set specific vendor
options at Avya's direction in regards how to set it up.

--
Ace

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

Please reply back to the newsgroup or forum for collaboration benefit among
responding engineers, and to help others benefit from your resolution.

Ace Fekay, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007, MCSE & MCSA
2003/2000, MCSA Messaging 2003
Microsoft Certified Trainer

For urgent issues, please contact Microsoft PSS directly. Please check
http://support.microsoft.com for regional support phone numbers.

[Meinolf Weber [MVP-DS]]

Hello Tang,

You can't do it. The client doesn't know if there is a DHCP server, it broadcasts
"i need an ip address" and then first come, first serve, is the way it is
handled.

What you can do in Windows server 2008 R2 is to define a delay for the answer
in a split scope environment, but only for Windows server 2008 R2 DHCP servers.
http://technet.microsoft.com/en-us/library/ee405264(WS.10).aspx

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

[Bill Kearney]

> I know the real fix is to kill the DHCP server on the phone system but
> our
> phone provider need to use the DHCP server for the phone configuration.

You cannot have more than one DHCP server on the wire. You MUST kill one or
the other.

The windows server can be configured to offer anything the phone system
needs. Find out what it needs and put that in your windows DHCP server.

You will not ever get it working with the two of them running at the same
time.

-Bill Kearney

[John John - MVP]

People very often use multiple DHCP servers for fault tolerance, as long
as the scopes are properly configured there is usually no problem with
multiple DHCP servers.

John

[Phil Angus]

Find out what it needs, take the mac address and simply reserve it with that
IP.

"Tang" <Ta...@discussions.microsoft.com> wrote in message
news:51AC41F5-1EF9-4E31...@microsoft.com...

[Frankster]

"Bill Kearney" <wkear...@hotmail.com> wrote in message
news:n5KdnaPY4tTVaIvW...@speakeasy.net...

I always assign two of my DCs DHCP duty. Each are configured to NOT pass
out the same addresses. This way, if one DC goes down, the other still
allows operation. Routine.

-Frank

[Bill Kearney]

> People very often use multiple DHCP servers for fault tolerance, as long
> as the scopes are properly configured there is usually no problem with
> multiple DHCP servers.

The simple answer is don't run two of them. Especially in a domain
environment. When expecting to use a domain-integrated DHCP server it an
exceptionally bad idea to use non-Windows DHCP services. DHCP feeds into
DNS and AD, but that's only with a Windows DHCP server, and one authorized
in the AD. When using AD integration it's indeed possible to use more than
one *windows* DHCP server. It's often a good plan to do so.

But using a mix of a Windows and a non-Windows DHCP server is a bad plan.
Mainly because the non-windows server won't (can't) populate the AD and DNS
entries. Doing so would lose all the AD-integation features.

-Bill