DHCP client and XPE FP2007

Hi Dick, I have investigate deeply my image and I find the solution myself
but I explain it here for everyone who have a similar problem. If I use the
XPE component 'Realtek 8169 family' for the 8139c+ nic and boot the image,
the first time the DHCP client request a IP sends a DISCOVER message on the
network for a DHCP server(I can notice it using MS NetworkMonitor3.1) and
after, when it found it, sends a REQUEST message to that server for a IP and,
after an ACK message, use that IP for itself. But if I reboot the client
(shutdown and powerup again) it doesn't send a DISCOVER message but only a
REQUEST for the old IP (I don't know why it can remember that IP, but it
remember that information!) and if another DHCP server propose to it a
different IP it doesn't consider that value and use the older. So I try to
componentize the exact driver for 8139c+ downloaded from Realtek and use it
on the same image; on the first boot the client perform a DISCOVER REQUEST
and ACK; when I reboot, the client perform again a REQUEST but if the server
propose to it a different ip, the client performs a new DISCOVER, REQUEST and
ACK messages and use the new ip from the DHCP server. I absolutely don't know
why the image show this behaviour; I use the FBWF so I think that when I
shutdown the client, no informations on the DHCP will remain....
Another time please note that on the SP1 version of XPE, I never seen this
strange behaviour.
Thanks,
Andrea Valori.

"Dick Dawson" wrote:

> I've dealt with some DHCP client issues so I might be able to help but I
> don't understand what "if I change the requested IP for the image from the
> DHCPserver" means. Does this mean that you have made a reservation of a
> specific IP address for your client's MAC address? If so, why would you
> expect the client IP address to change before its lease expires? It would
> be hard for me to believe that the behavior in this case varies for
> different versions of the client since the client has no way of knowing what
> configuration options are being changed on the server.
>
> DD
>
> "Andrea Valori" <AndreaValori@discussions.microsoft.com> wrote in message
> news:C06335EF-2288-4E76-88EE-0668D7D55E02@microsoft.com...

> > Hi to everyone,
> > I have a big trouble with DHCP client in FP2007 (but, like I see on this
> > newsgroup, similar problems arises starting from the SP2 release). I have
> > a
> > minlogon image with FBWF on, booting from a CF. Like suggested in other
> > posts
> > (thanks, KM!) in my image I added the core networking (without firewall)
> > and
> > basic tcp/ip networking macro, the client for MSnetwork component and
> > disabled the APIPA feature. If I boot the image, at first time the DHCP
> > client receive the espected address from a WIN2k3 DHCP server, but if I
> > change the requested IP for the image from the DHCPserver and reboot the
> > client, it mantains the old address (!) until I manually call a ipconfig
> > /release and ipconfig /renew command from the cmd. I see this behaviour
> > with
> > the FBWF on or off. The NIC is a Realtek RTL8139C+ and I try to select for
> > it
> > either the rtl8139 family xpe component and the rtl8139c+ component
> > obtained
> > from the driver package downloaded from Realtek. Please note, as usually,
> > that with the XPE SP1 and the same computer/image I never seen this
> > problem!
> > Thanks in advance,
> > Andrea Valori.

>
>
>

Andrea,
If you put your device through FBA with its NIC connected to a network that
has a DHCP server then the IP address it gets during FBA will be
"remembered" in the registry and when you boot the deployed device it will
behave exactly as you described, i.e. it will bypass sending DISCOVER and
start with a REQUEST for the remembered IP address. However if the
"remembered address" can not be leased by the DHCP server then your device
should time out and send a DISCOVER.

I have found that the simplest way to prevent this problem is to make sure
your ethernet cable is disconnected during FBA. If you do that you should
also disable automatic IP address configuration as described in
http://technet2.microsoft.com/window....mspx?mfr=true
otherwise the device will remember a 169... address.

DD

"Andrea Valori" <AndreaValori@discussions.microsoft.com> wrote in message
news:9C177875-5467-4B83-BD44-171BD677BCC2@microsoft.com...

> Hi Dick, I have investigate deeply my image and I find the solution myself
> but I explain it here for everyone who have a similar problem. If I use
> the
> XPE component 'Realtek 8169 family' for the 8139c+ nic and boot the image,
> the first time the DHCP client request a IP sends a DISCOVER message on
> the
> network for a DHCP server(I can notice it using MS NetworkMonitor3.1) and
> after, when it found it, sends a REQUEST message to that server for a IP
> and,
> after an ACK message, use that IP for itself. But if I reboot the client
> (shutdown and powerup again) it doesn't send a DISCOVER message but only a
> REQUEST for the old IP (I don't know why it can remember that IP, but it
> remember that information!) and if another DHCP server propose to it a
> different IP it doesn't consider that value and use the older. So I try to
> componentize the exact driver for 8139c+ downloaded from Realtek and use
> it
> on the same image; on the first boot the client perform a DISCOVER REQUEST
> and ACK; when I reboot, the client perform again a REQUEST but if the
> server
> propose to it a different ip, the client performs a new DISCOVER, REQUEST
> and
> ACK messages and use the new ip from the DHCP server. I absolutely don't
> know
> why the image show this behaviour; I use the FBWF so I think that when I
> shutdown the client, no informations on the DHCP will remain....
> Another time please note that on the SP1 version of XPE, I never seen this
> strange behaviour.
> Thanks,
> Andrea Valori.
>
> "Dick Dawson" wrote:
>

>> I've dealt with some DHCP client issues so I might be able to help but I
>> don't understand what "if I change the requested IP for the image from
>> the
>> DHCPserver" means. Does this mean that you have made a reservation of a
>> specific IP address for your client's MAC address? If so, why would you
>> expect the client IP address to change before its lease expires? It
>> would
>> be hard for me to believe that the behavior in this case varies for
>> different versions of the client since the client has no way of knowing
>> what
>> configuration options are being changed on the server.
>>
>> DD
>>
>> "Andrea Valori" <AndreaValori@discussions.microsoft.com> wrote in message
>> news:C06335EF-2288-4E76-88EE-0668D7D55E02@microsoft.com...

>> > Hi to everyone,
>> > I have a big trouble with DHCP client in FP2007 (but, like I see on
>> > this
>> > newsgroup, similar problems arises starting from the SP2 release). I
>> > have
>> > a
>> > minlogon image with FBWF on, booting from a CF. Like suggested in other
>> > posts
>> > (thanks, KM!) in my image I added the core networking (without
>> > firewall)
>> > and
>> > basic tcp/ip networking macro, the client for MSnetwork component and
>> > disabled the APIPA feature. If I boot the image, at first time the DHCP
>> > client receive the espected address from a WIN2k3 DHCP server, but if I
>> > change the requested IP for the image from the DHCPserver and reboot
>> > the
>> > client, it mantains the old address (!) until I manually call a
>> > ipconfig
>> > /release and ipconfig /renew command from the cmd. I see this behaviour
>> > with
>> > the FBWF on or off. The NIC is a Realtek RTL8139C+ and I try to select
>> > for
>> > it
>> > either the rtl8139 family xpe component and the rtl8139c+ component
>> > obtained
>> > from the driver package downloaded from Realtek. Please note, as
>> > usually,
>> > that with the XPE SP1 and the same computer/image I never seen this
>> > problem!
>> > Thanks in advance,
>> > Andrea Valori.

>>
>>
>>