Abandoned messages.

[Keith]

Ive got three clients that are doing this:

Jan  8 11:03:35 netreg1 dhcpd: DHCPDISCOVER from 00:11:43:41:84:2c via
69.176.166.1

Jan  8 11:03:35 netreg1 dhcpd: DHCPOFFER on 69.176.166.126 to
00:11:43:41:84:2c (Bekah) via 69.176.166.1

Jan  8 11:03:35 netreg1 dhcpd: DHCPREQUEST for 69.176.166.126
(209.145.111.37) from 00:11:43:41:84:2c (Bekah) via 69.176.166.1

Jan  8 11:03:35 netreg1 dhcpd: DHCPACK on 69.176.166.126 to
00:11:43:41:84:2c (Bekah) via 69.176.166.1

Jan  8 11:03:35 netreg1 dhcpd: Abandoning IP address 69.176.166.126:
declined.

Why would a client go through the whole discover/offer/request/ack then
the server at the end of it say declined, when the client ACK'd the
request?

lease 69.176.166.126 {
  starts 2 2008/01/08 18:09:45;
  ends 2 2008/01/08 18:09:46;
  binding state free;
  hardware ethernet 00:e0:18:57:f7:d4;
  uid "\001\000\340\030W\367\324";
--
lease 69.176.166.126 {
  starts 2 2008/01/08 18:09:46;
  ends 2 2008/01/15 18:09:46;
  binding state active;
  next binding state free;
  hardware ethernet 00:e0:18:57:f7:d4;
--
lease 69.176.166.126 {
  starts 2 2008/01/08 18:09:46;
  ends 2 2008/01/08 18:09:46;
  tstp 2 2008/01/08 18:09:46;
  binding state abandoned;
  next binding state free;
--

And in dhcpd.leases I have that IP address in three different
states...active, free and abandoned.

Then in a blink as I'm grepping over the dhcpd.leases file, 69.176.166.126
is not in there as dhcpd seems to have rewritten the lease file.

Its only 3 clients that are doing this on this one subnet and seems kind
of a tricky situation.

Any pointers on what happening here?

Thanks,
Keith