*** From dhcp-server -- To unsubscribe, see the end of this message. ***
> we have a small problem. for the most part, dhcp is working great, but we
> ran into one NT machine where the server offers a lease, the NT machine
> req's it and then the server nak's. any ideas as to what might cause this
> to occur?
>
I had the very same thing happen yesterday. (And have dhcpd report a lease
conflict on an earlier restart).
I had overlapping range statements, ie I wanted machines that initially
bootp, to get the same address no matter what the protocol. (Im cloning NT
boxes using a Linux 'nfs root' boot disk, so they bootp when Linux starts
but dhcp when NT finally starts).
So that the machines would get the same address, no matter the OS, I tried
to have the 'range' and the range dynamic-bootp to be the same. Unfortunatly
this seems to cause dhcpd to issue conflicting leases and get it self in a
knot. My problem went away when I changed the bootp and dhcp ranges not to
overlap. The problems then went away.
------------------------------------------------------------------------------
To unsubscribe from this list, please visit http://www.fugue.com/dhcp/lists
If you are without web access, or if you are having trouble with the web page,
please send mail to [EMAIL PROTECTED] Please try to use the web
page first - it will take a long time for your request to be processed by hand.
------------------------------------------------------------------------------
