[svlug] Linux Terminal Server (LTSP) problem : workstation could not find TFTP files

[Rob Walker]

On Sun, 2002-08-25 at 08:59, Stephen Liu wrote:
> I tried several days to set up a LTSP server (Linux Terminal Server) but 
> met with frustration.  Hereinbelow are my test results and problem.  Hoping 
> that some folks on the list can give me a hand.
> 
> Thanks in advance.
> 
> Stephen Liu
> 
> 
> LTSP server (v3.0) setup without problem
> Diskless workstation is borrowed from K12osn project.  It works fine there 
> with boot ROM on LAN card
> OS: RH7.3
> LTSP server : ethernet cards activated
> 
> 
> Problem :  TFTP file not found
> ===========================
> Workstation starts to boot ending :-
> ............
> ....... TFTP error 1 (File not found).  Unable to load file
> <sleep>
> <abort>

Are you sure that the file which the client is trying to load exists?  

What are the permissions on the file?

Is the file in the correct place in the filesystem (some tftp servers
will look in /tftpboot or some other configurable place by default)?

more comments below.


> ------   TEST RESULTS  -------
> 
> option root-path              "192.168.0.254:/opt/ltsp/i386";
> group   {
>      use-host-decl-names       on;
>      option log-servers        192.168.0.254;
> 
>      host ws001 {
>          hardware ethernet     00:E0:06:E8:00:84;
>          fixed-address         192.168.0.1;
>          filename              "/lts/boot/bootp/vmlinuz.eepro100.bootp";
>      }
> }
> 
> 
> /etc/dhcpd  (Sample No. 2)
> ====================
> (REMARK :  2 tests
> 
> 1)  change made to   filename "/lts/vmlinuz-2.4.18-3"  (previous  filename 
> "/lts/boot/bootp/vmlinuz.eepro100.bootp")
> 
> 2)  change also made to kernel to read    filename 
> "/lts/vmlinuz-2.4.18-ltsp-1" )

I don't know, but is it possible that the file that the client is
looking for is /opt/ltsp/i386/lts/vmlinuz-2.4.18-ltsp-1 ??

I suggest getting a packet trace from the server, and look at it with
ethereal.

> # ls -IR /tftpboot
> lts

what happens when you do the following command?

cat /etc/inetd.conf /etc/services | grep -i tftp

Once again, get a packet trace with tcpdump, save it to a file, and then
open it in ethereal.  That should tell you exactly what file the tftp
client is asking for, and why the client is reporting that the file
doesn't exist.

have fun,
rob