Re: DHCP Leasing

Answers in line
"fmsmcse" <> Persisted in message
news:1FC4E5F9-6F61-48AD-BC80-...
> Client01 one leases an IP and so does Client02.
> One hour after their leasing, the DHCP server goes down.

Your DHCP server going down would trouble me most.

> Client01 and Client02 have to reboot for any reason.
>
> After rebooting, Client01 maintains its IP address, as per the leasing
> expiration. Client02 releases the IP (remember they both have the same
> leasing period) for some reason.
>
> Both clients are Windows XP, and their behavior is expected to be the
> same,
> since they have the same TCP/IP configuration. They are in the same
subnet
> and both can find the default gateway. No alternate IP is assigned.
>
> Any clue about why Client02 would release its IP before the leasing
time
> expires?

Nocturnal gave you a clue last week when he asked if your DHCP client
service was disabled.
Check that this service is working properly (remember to check the
services
it depends on as well). If it fails to start in a timely manner your ip
address will become 0.0.0.0 and if the service comes on line a few
moments
later your macine will begin to look for the DHCP server asking for an
IP
address. When no response is received Client02 will give itself an
APIPA.

> Remember Client01 has the same config and does not release the IP.

TCP/IP configs may be the same, but services and other hardware may not
be
equal.

As for the question of the dhcp info remaining after reboot on Client01,
the
registry holds the answer to this please see:
http://support.microsoft.com/default...b;en-us;314053

If you continue to have trouble please post in:
microsoft.public.windows.server.networking group.


LRM
....and answer came there none -- and that was scarcely odd because
they'd
eaten everyone.
~Lewis Carroll: Through the Looking Glass

Pedro Simoes