DHCPD will not work with windows clients. It seem that the client does not see the replies.
glenn.satchell at uniq.com.au
Sat Feb 2 10:41:19 UTC 2013
Wow, that's really old, approx September 2000...
How about testing a client from that era such as Windows 98? That would
verify that the dhcp server and network is functioning correctly. The
packet captures might also be useful for comparison with new clients.
The underlying protocol may not have changed, but the defaults for various
operating systems have, and, for example, items such as 'always broadcast'
is not available as a switch.
Can you post your config, or at least the main parts?
On Sat, February 2, 2013 10:23 am, Steven Carr wrote:
> On 1 February 2013 22:40, Zentner, Jeff <jeff.zentner at hp.com> wrote:
>> Hi All
>> I am using a old version V3.0pl2_DHCP4 of dhcpd and it does not seem to
>> with windows. It seem that the client does not see the replays. I have
>> XP and 7 so far. I have a current dhcpd on another computer and it seems
>> work fine is there a way I can do something to make my older code work.
>> is not easy for me to upgrade. Thanks for the help in advance.
> Have you taken any packet captures from both the server running DHCPD
> and the Windows client to find out why the Windows computer is not
> picking up DHCP? Does the Windows client receive the reply? and does
> the reply contain the correct data?
> AFAIK the underlying DHCP protocol itself hasn't changed (in a long
> time) so there shouldn't be anything preventing a newer version of
> Windows from getting a DHCP lease. Another thing to look into is
> whether any network equipment is filtering out/dropping/blocking the
> DHCP messages, but you are going to need to do packet captures first
> to see if the messages are getting through.
> dhcp-users mailing list
> dhcp-users at lists.isc.org
More information about the dhcp-users