force DHCP client to start with Discover?

Tech-Archive recommends: Speed Up your PC by fixing your registry

From: The Other Roger (blooline_at_online.nospam)
Date: 02/25/05 

Date: Fri, 25 Feb 2005 17:28:29 -0500

I've noticed that the typical protocol sequence for DHCP assignment in Windows
consists of a client Request message with option 50 set to a desired address
followed by a server Ack. I assume Windows clients "remember" their last DHCP
assignment in the registry and they use it to populate option 50. However I
have a need to force clients through the full protocol of starting with
Discover, getting an Offer, responding with Request, and getting an Ack. Is
there a registry setting or other means by which I can force my client not to
remember its last address and always start the DHCP protocol with a Discover?

BTW, I need to do this to demonstrate a serious bug I've found in Windows XP
Embedded (XPe). XPe is essentially the XP Pro code base broken into lots of
components that can be selected to build smaller systems. I've found that for
my XPe configuration, which always starts DHCP with Discover, about 50% of the
time the client abandons the protocol after receiving an Offer. I'd like to see
if the same thing happens with XP Pro because in that case I have the
possibility of seeking support through my MSDN subscription.

Roger

Relevant Pages

  • DHCP, dual NIC, DHCP failure
    ... abandon the DHCP protocol about 50% of the time. ... and a Win2003 server that was both boot server and DHCP server. ... It appears to me that the DHCP client runs independent threads to execute this ...
    (microsoft.public.windowsxp.embedded)
  • Re: newbie - client not replying to DHCPOFFER
    ... > I did write earlier about my dhcp woes. ... > the windows client and the firewall is disabled when i try with dhcpd. ... well on both Linux and Windows. ...
    (comp.os.linux.networking)
  • Re: Windows 7 doesnt update PTR
    ... I just noticed, I have a windows 7 client that never updates its PTR, evenn after a ipconfig /registerdns. ... By default, the client registers the A record, and DHCP registers the PTR. ... Clients that are running Windows Server 2003, Windows 2000, or Windows XP DHCP interact with DNS dynamic update protocol in the following manner: ...
    (microsoft.public.windows.server.dns)
  • Re: Windows 7 doesnt update PTR
    ... I just noticed, I have a windows 7 client that never updates its PTR, ... the client registers the A record, and DHCP registers the PTR. ... Clients that are running Windows Server 2003, Windows 2000, or Windows XP ...
    (microsoft.public.windows.server.dns)
  • Re: How to obtain an IP-address immediately
    ... works, but not on Linux" ... On Windows the OS detects whenever i attach a wired connection an will ... Windows violates the DHCP protocol requirements by ... client will find out that the address is no longer available. ...
    (comp.os.linux.networking)