DHCP not working

I can confirm that with a fresh install of Leopard Server this necessary part was missing from /etc/bootpd.plist.

Adding it fixes the problem.

Okay, I had the same problem.

I looked in /etc/bootpd.plist and found some bugs (or obscure features).

First of all Bootp_enabled was set to false so I changed it to True.
Then under the pool config, two lines were simply missing. So I pasted:
<key>net_address</key>
<string>192.168.42.0</string>

And last I changed reply thresholdseconds from 10 to 1 seconds

After that the DHCP server works 🙂

I don't know if it's important to this case, but the DHCP server dont recieves the DHCP-requests directly from the clients but from a DHCP relay.

thank you very much, your 3 steps solved it all!

I'm having the same issue: 2 of the devices on my network (Maxtor shared storage device and a Sony network camera) are issuing DHCP DISCOVERs, but getting no response. I have adjusted the threshold 1 to, made sure the network is defined and enabled bootp - all as suggested here. But no luck. My log shows on restart:

Jan 6 13:49:40 refuge-server bootpd[61761]: can't open /etc/bootptab
Jan 6 13:49:40 refuge-server bootpd[61761]: server name refuge-server.refuge......
Jan 6 13:49:40 refuge-server bootpd[61761]: interface en0: ip 192.168.1.56 mask 255.255.255.0
Jan 6 13:49:40 refuge-server bootpd[61761]: subnets: Failed to convert 'nb over_tcpip_nameserver': Invalid IP address
Jan 6 13:50:48 refuge-server bootpd[61761]: DHCP DISCOVER [en0]: 1,0:10:75:ff:b4:ec <mss-FFB4EC>
Jan 6 13:51:37 refuge-server bootpd[61761]: DHCP DISCOVER [en0]: 0,8:0:46:7b:34:b3:0:0
Jan 6 13:51:56 refuge-server bootpd[61761]: DHCP DISCOVER [en0]: 1,0:10:75:ff:b4:ec <mss-FFB4EC>
Jan 6 13:51:57 refuge-server bootpd[61761]: DHCP DISCOVER [en0]: 0,8:0:46:7b:34:b3:0:0
Jan 6 13:51:58 refuge-server bootpd[61761]: DHCP DISCOVER [en0]: 1,0:10:75:ff:b4:ec <mss-FFB4EC>

The "failed to convert" bugs me too. In the bootpd.plist there is an entry:
<key>dhcp nb_over_tcpip_nameserver</key>
<array>
<string>192.168.1.56</string>
<string></string>
</array>
and I assume the empty <string> is the cause, but if I delete it, ServerAdmin puts it back. Any ideas>

All help or ideas most appreciated.

Regards,

--Kip

Apologies - when I set the threshhold down to 0 (instead of 1) both of these devices were able to get addresses.

Regards,

--Kip

OK, last issue I hope. All my devices are now being served addresses, but there's something weird with the IP Camera (a Sony PTZ model). I have a static map set for it, but its always being server a dynamic address. I've cycled the DHCP server, manually edited the dhcpd_lease file, rebooted the camera - but still the case. Then I noticed the following:

Jan 6 15:40:06 refuge-server bootpd[64529]: DHCP DISCOVER [en0]: 0,8:0:46:7b:34:b3:0:0
Jan 6 15:40:07 refuge-server bootpd[64529]: OFFER sent <no hostname> 192.168.1.107 pktsize 300
Jan 6 15:40:07 refuge-server bootpd[64529]: DHCP REQUEST [en0]: 0,8:0:46:7b:34:b3:0:0
Jan 6 15:40:07 refuge-server bootpd[64529]: ACK sent <no hostname> 192.168.1.107 pktsize 308

Notes the MAC address format of the camera: In the static map I have it as 08:00:46:7b:34:b3, but here it is sending the DHCP server 08:00:46:7b:34:b3:0:0. Is that enough to mean it won't match the static address I've defined? And what do these extra 0:0 address elements mean?

Thanks for any help or suggestions,

--Kip