Re: DHCP Leasing

In article <07500AAC-1D8C-4DD8-A306-0DE62086D322@xxxxxxxxxxxxx>,
fmsmcse@xxxxxxxxxxxxxxxxxxxxxxxxx says...
> Wonder the following situation, you've centralized your IP distribution in a
> main site and several sites, let's say 15 sites, all depend on the main one
> to get an IP.
>
> All clients in the 15 sites have gotten an IP early in the morning and then
> at midday the link goes down for all 15 sites to the main site and, as you
> are lucky enough, there's a power down in those 15 sites.
> By what you explained, all the clients would get an APIPA then...??

Exactly. And this is one of the exact scenarios APIPA was designed for,
because in this scenario all of the hosts would be able communicate with
each other in the APIPA address space.

>
> "Ben Smith" wrote:
>
> > In article <1FC4E5F9-6F61-48AD-BC80-1A736CDC4899@xxxxxxxxxxxxx>,
> > fmsmcse@xxxxxxxxxxxxxxxxxxxxxxxxx says...
> > > Client01 one leases an IP and so does Client02.
> > > One hour after their leasing, the DHCP server goes down.
> > > 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?
> > > Remember Client01 has the same config and does not release the IP.
> >
> > This is not quite how DHCP leases work. DHCP leases are controlled by
> > the DHCP server, not the client.
> >
> > When a DHCP client reboots, after the IP stack is started, it issues a
> > DCHP Discovery packet, if the DHCP servers that receive the broadcast
> > respond with a Acknowledge packet. If the DHCP server that acknowledges
> > the client was the one that issued the address the client has cached,
> > the client will request it in the Request packet, if the lease is still
> > active, the DHCP server will respond with a Offer package for the
> > address and the lease time is reset.
> >
> > If the DHCP server is not online when the client reboots, the client
> > will use an APIPA address and continue to rebroadcast a Discovery packet
> > every 5 minutes (2000 and later).
> >
> > As for why the two XP clients are behaving differntly, my guess is that
> > the network IP properties on each client are configured differently.
> > Most likely, APIPA is turned off on Client01. Client02 is working as
> > expected.
> >
> > If you would like to learn more about this I suggest reading the RFC on
> > DHCP (while boring as heck, if there is no better source for learning
> > DHCP, which is a pretty simple protocol) and/or installing a network
> > monitor and watching DHCP traffic.
> >
>
.

Relevant Pages

  • Re: Understanding the DHCP Server Client conversation (very intresting subject)
    ... why not the DHCP server just sends its offer to the client that is requesting the service according to its MAC address?? ... you said the (DHCP server send the DHCP OFFER as a unicast, to the whole network) but a specified MAC address. ...
    (microsoft.public.cert.exam.mcse)
  • Re: mac address issue
    ... mac address that was different in some way that just resulted in the DHCP ... Sounds like the client is sent our a DHCP request, ... your DHCP server is replying with an offer, but the client is sending back ... Modeled after the famous Black Hat event ...
    (Security-Basics)
  • Re: DHCP client and XPE FP2007
    ... If you put your device through FBA with its NIC connected to a network that ... start with a REQUEST for the remembered IP address. ... "remembered address" can not be leased by the DHCP server then your device ... But if I reboot the client ...
    (microsoft.public.windowsxp.embedded)
  • Re: Understanding the DHCP Server Client conversation (very intresting subject)
    ... I understand that the Client is sending a broadcast message because ... it doesn't know any concrete DHCP server in order to request an IP ... specified DHCP server, I shout to everyone on the network that I ...
    (microsoft.public.cert.exam.mcse)
  • DHCP scope shows multiple IPs leased out by same host...
    ... I have been looking at my DHCP leases and I have noticed that a certain ... client machine is grabbing multiple IP addresses from my scope from both DHCP ... Server2 scope. ...
    (microsoft.public.windows.server.networking)
Quantcast