Hi all,
We have quite a large WFWG network here, and I'm running a Linux box
which acts as our DNS, mailserver & general Internet connection box. The
WFWG network administrator has just come off a course where he's gotten
all e*d about the NT DHCP setup. Not wanting to have data duplicated
all over the place I set up bootpd (2.4 - the latest on sunsite) to try
and test whether it'll do the job.
Here's the relevant part of the bootptab -
external: hn:ht=ethernet:ha=0020AF9AC803:dn=spl.co.za:ds=196.14.5.2:\
:sm=255.255.255.0:gw=196.14.5.1:
and here's the syslog entry of what happens when I try to start the
Windows box -
in.bootpd[260]: recvd pkt from IP addr 0.0.0.0
in.bootpd[260]: bootptab mtime: Wed Jun 14 11:08:04 1995
in.bootpd[260]: request from Ethernet address 00:20:AF:9A:C8:03
in.bootpd[260]: found 196.14.5.22 (external)
in.bootpd[260]: bootfile=""
in.bootpd[260]: vendor magic field is 99.130.83.99
in.bootpd[260]: request message length=548
in.bootpd[260]: extended reply, length=548, options=312
in.bootpd[260]: sending reply (with RFC1048 options)
in.bootpd[260]: setarp 196.14.5.22 - 00:20:AF:9A:C8:03
This all looks good to me.
Unfortunately, (you knew that was coming didn't you :-), the WFWG box
just sits there for a while and then comes up with a message about not
being able to find the DHCP server. This same box with no change in
config is able to use the NT DHCP server with no problems. I have also
tried this with a box using Windows 95 Final Beta - same problem.
So, does anyone know what the problem is? Can bootpd 2.4 not handle
DHCP, or has Uncle Bill done a dirty on us again and used a strange
proprietry version of the protocol?
Alternatively, does anyone have another piece of software for Linux which
can do the job?
Thanks
--
Neil
=========== It don't mean a thing if it ain't got that swing ==============