Re: Leasing Time Issue

Ok, you have a remote pc receiving dhcp addresses from a dhcp server.
The
link goes down. While the link is down a pc has been rebooted. Well, it
will
not keep it's dhcp address because it will not have a DHCP server to
tell it
that the address is still leased to it. So it will try to ask for one
and
will not receive one and will give itself the APIPA address. The lease
is
only important if the machine isn't rebooted. So, earlier, when the
other
posters kept saying it couldn't see the dhcp server and that was the
point.
The other pc's kept their addresses because they hadn't rebooted.
Run ipconfig /renew on the pc and all should be well as long as you
don't
have any issues with the card or other network devices between the pc
and
the dhcp server.

--
LRM


"fmsmcse" <> wrote in message
news:1171F898-B417-4E18-BAEA-...
> That's exactly the issue, the client is in a remote site and the lease
has
> not expired.
> For sure if the link is down, it should keep it's address until it
> expires,
> one MUST consider the leasing time.
>
> "JaR" wrote:
>
>> In microsoft.public.cert.exam.mcse, =?Utf-8?B?Zm1zbWNzZQ==?= spewed
>> across the ether:
>>
>>
>> > Yes, it can't find the net, but it should keep the IP until the
lease
>> > expires if it couldn't contact the DHCP at 50% and 87,5% of the
total
>> > time for the end of the lease.
>>
>> Forget about the lease. If the client is giving itself an APIPA, it
can't
>> see the DHCP server for some reason.
>>
>> --
>> JaR
>> MCNGP 10110
>> Remove hat to reply
>> You can see a lot by just looking. ~Yogi Berra
>>

Pedro Simoes