On Mon, 17 Nov 1997, Tim Rightnour wrote:

> OK.. here is more information..  here are the messages from "netboot"
> (copied down by hand)

[..]

> Ive attempted manually setting that last arp statement, and checking it with
> arp -a  which seems to work ok....  bootp: no reply is the errant message I'm
> looking at right now..  It seems to cause the later messages and the eventual
> retry to the next kernel..

You could try posting tcpdump output from during the boot. Seeing at which
stage a packet from either side is not responded to by the other side is
often a quick way of finding the problem.


-- 
Soren