*** From dhcp-server -- To unsubscribe, see the end of this message. ***
> (Here's the real question:) Why doesn't the bundled HP dhcp
> server have this same problem in getting offers accepted by
> the clients?
My understanding is that the HP server is setting socket options that
aren't documented. I've been told that I will someday be let in on
the secret of these socket options, but so far that hasn't happened.
:'(
> IOW, the only piece that changed is the dhcp server software,
> and now the local win clients are unable (or are refusing) to
> accept offers.
This is the broadcast address problem. If you set up the broadcast
as specified in the README, this problem should go away.
> 2) The README says that it's the "picky windows" clients that
> are causing the problem, but if they are performing to the
> spec (the RFCs), isn't the problem really somewhere else?
The problem is that the spec demands more of most IP stacks than
they have to offer. Microsoft isn't being unreasonable in their
interpretation of the spec, but it would have been nice if they could
have interpreted it a tiny bit more loosely.
_MelloN_
------------------------------------------------------------------------------
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.
------------------------------------------------------------------------------
