Re: force DHCP client to start with Discover?
From: The Other Roger (blooline_at_online.nospam)
Date: 02/28/05
- Next message: The Other Roger: "DHCP offer ignored - Ethereal trace"
- Previous message: AliR: "Re: TTL Question. Don't understand the boundaries."
- In reply to: Rhett Gong [MSFT]: "RE: force DHCP client to start with Discover?"
- Next in thread: Rhett Gong [MSFT]: "Re: force DHCP client to start with Discover?"
- Reply: Rhett Gong [MSFT]: "Re: force DHCP client to start with Discover?"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 28 Feb 2005 11:34:26 -0500
It is not true that the client will start with a Discover as a little sniffing
with a protocol analyzer will clearly show. If the client had a previously
assigned DHCP address, it will start with a Request after the next boot using
the previous address in option field 50 as the desired address unless "ipconfig
/release" was issued before shutting down the client.
"Rhett Gong [MSFT]" wrote:
>
> >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?
> Generally, if DHCP is enabled, client will start discover when it is
> starting or reconnecting to a network. All these actions are handled by
> system. So I don't know there is a registry setting always start the DHCP
> protocol with a Discover.
- Next message: The Other Roger: "DHCP offer ignored - Ethereal trace"
- Previous message: AliR: "Re: TTL Question. Don't understand the boundaries."
- In reply to: Rhett Gong [MSFT]: "RE: force DHCP client to start with Discover?"
- Next in thread: Rhett Gong [MSFT]: "Re: force DHCP client to start with Discover?"
- Reply: Rhett Gong [MSFT]: "Re: force DHCP client to start with Discover?"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
|