I've been having some really terrible problems with DHCP on our network
here. I'm running joind under DU 4.0D with mixed Win95 and WinNT
clients. We've had some serious outages of DHCP service where DHCP will
work fine one day and ignore incoming events the next. Two questions:
1) I've looked at the incoming packets with 'joind -d4' and 'tcpdump
-xels 1500 udp port bootps or port bootpc'. While I can get the packets
to line up, it seems that there's some "extra" stuff between the UDP
header (which claims it has five 32-bit words, per RFC 791) and the RFC
2131 definition of the BOOTP header. There appear to be two 32-bit words
between the nominal end of the UDP header and the start of the DHCP
data. What am I missing here?
2) We had (before I reconfigured it) a WinNT box with RAS installed that
sent out DHCP requests to pick up IP addresses for remote access users.
One problem: the hlen parameter on the request was set to 16 (0x10).
There being no earthly Ethernet device with a MAC address that long,
joind always rejected it. Does anyone know why Microsoft would put that
value there? Could it be that there was some kind of
synchronization/framing problem?
--
Robert L. McMillin | Not the voice of Syseca, Inc. | rlm_at_syseca-us.com
Personal: rlm_at_helen.surfcty.com | rlm_at_netcom.com
Received on Tue Nov 10 1998 - 22:11:13 NZDT