At 4:24 PM -0500 10/25/99, Michael Bartosh wrote:

[SNIP]
>
>Actually I was mistaken. It was a 200 that started to boot correctly.
>
>I have moved things to the internal network in ymy room rather than 
>keeping them at work. This is a much simplified networks so things 
>will be easier. Am hoping to install on the 200 and then put the 
>disk on the 240.  Intend to use it as a departmental ftp server 
>eventually. Have an old 200 running ultrix right now but we didn't 
>want to futz with y2k compliance. So now my linux box is seeing the 
>bootp request.  It's a first step...
>
>I am still interested in the errs I was getting on the 240.

So here's where I am:

The 200 is sending out bootp requests- at least about 15 sec after I do
>>boot 6/tftp

the linux box logs
>Oct 25 19:01:45 heretic in.bootpd[8188]: version 2.4.0

However nothing happens then. The 200 is not timing out, so it must 
be getting something.

TFTP is working correctly.

Any ideas? When I netboot our iMac it logs as a dhcpd BOOTREQUEST and 
logs the MAC address and then fails at
dhcpd: DHCPREQUEST  from 00:50:e4:90:ed:62 vi eth0
dhcpd: No applicable record for BOOTP host 00:50:e4:90:ed:62

So should I be doing something with DHCP?

I have the 200 on a coax line but I suppose that if it were not 
working the bootp request would time out and wouldn't log on heretic 
(the linux box)

Thanks-

-mab

>
>-mab
>
>>Tohru Nishimura
>>Nara Institute of Science and Technology

OK here's where I'm at right now.