Someone else already pointed to making sure your path is correct, but also (RedHat based) check /etc/xinet.d/tftp and check where TFTPd is making root.  By default on redhat, the ‘root’ directory is /tftpboot .  So if your dhcpd.conf file tells the client to look into /tftpboot/etc/blah/vmlinuz.nic, it will get lost, and instead the dhcpd.conf file should tell it only /etc/blah/vmlinuz.nic .

 

It all sounds kind of cryptic, but its not that difficult, let us know your findings…

 

Joey

 

 

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Bill Watters
Sent: Tuesday, August 20, 2002 7:26 AM
To: [EMAIL PROTECTED]
Subject: [Ltsp-discuss] TFTP question?

 

I have been following the list for a while, and reading the archives, but no clear answer yet that I can find, so, I'll post my question.

I have successfully passed the DHCP Configuration.  I edited it alittle to allow for fitting into my existing network.  The issue I believe is with TFTPD.  On the client, it passes the dhcp handshake, gets it's IP, then it says something to the effect of 192.168.1.3:/lts/boot/vmlinuz-(the nic) not found error 1.

(192.168.1.3 is the server, assigned)

 

Not really sure where to go from here.  I was thinking maybe there is something with the rom-o-matic boot disk. or perhaps the TFTPD configuration, or the DHCPD configuration...

 

Any thoughts would be greatly appreciated

 

-bill watters

Reply via email to