I have a strange issue with DHCP on my K12LTSP server. If I boot a client, I now get the following, and the PXE boot fails. Sep 7 12:44:35 ncslts3 dhcpd: DHCPDISCOVER from 00:c0:4f:50:41:bb via eth0 Sep 7 12:44:35 ncslts3 dhcpd: Abandoning IP address <a href="http://192.168.0.253">192.168.0.253</a>: pinged before offer Sep 7 12:44:36 ncslts3 dhcpd: DHCPDISCOVER from 00:c0:4f:50:41:bb via eth0 Sep 7 12:44:36 ncslts3 dhcpd: Abandoning IP address <a href="http://192.168.0.252"> 192.168.0.252</a>: pinged before offer Sep 7 12:44:38 ncslts3 dhcpd: DHCPDISCOVER from 00:c0:4f:50:41:bb via eth0 Sep 7 12:44:38 ncslts3 dhcpd: Abandoning IP address <a href="http://192.168.0.251">192.168.0.251</a> : pinged before offer Sep 7 12:44:42 ncslts3 dhcpd: DHCPDISCOVER from 00:c0:4f:50:41:bb via eth0 Sep 7 12:44:42 ncslts3 dhcpd: Abandoning IP address <a href="http://192.168.0.250">192.168.0.250</a>: pinged before offer Sep 7 12:44:50 ncslts3 dhcpd: DHCPDISCOVER from 00:c0:4f:50:41:bb via eth0 Sep 7 12:44:50 ncslts3 dhcpd: Abandoning IP address <a href="http://192.168.0.249">192.168.0.249</a>: pinged before offer If I specify a reservation for the client though, e.g. host ws123 { # Tech Lab system 1 hardware ethernet 00:c0:4f:50:41:bb; fixed-address <a href="http://192.168.0.123">192.168.0.123</a>; } It boots without issues. All of the IP addresses that are being tried above already are used (and are actually specified as reservations in the conf file). So, why is dhcp trying IP addresses that are already in use? How can I force dhcp to not try these? I know I can reset the range so that it stops at say <a href="http://192.168.0.248">192.168.0.248</a>, but then what happens to the 249-253 systems? Sincerely, Dave Hopkins