From: "Saurav  Gohain" <[EMAIL PROTECTED]>
Subject: [Ltsp-discuss] TFTP Problem


Saurav;

Here's my thoghts on troubleshooting this:


1. Network configuration

        In a prior message, you wrote:
        
                1.While loading the workstation, it shows the server add as : 
                169.254.177.197 where as my server add in lts.conf is set as 
                192.168.0.254 and on issuing 'dhcpd' only i found that it's 
                listening on eth0 .
                
                2.Second , it shows TFTP Error 1 ( File Not found)
                I guess this is because, it tries to load 
                169.254.177.197:/lts/vmlinu...
        
        If you are still getting this, *something* is
        responding to its dhcp request incorrectly.  It
        may not be the server you think it is.  Are any
        other servers on your network that may respond 
        to the dhcp request?  Where is this address
        coming from?
        
        Perhaps you can fire up ethereal and trace where 
        it is coming from.  Another approach is to isolate
        the LAN between your server and client (use a 
        crossover cable or a hub and two wires).

2. Are you booting it with PXE or Etherboot?  Do you have
   any *working* clients on your network to compare it with?

3. dhcpd server

        Once your dhcpd server is working correctly, the 
        client will display dhcp request information like
        this:
        
                CLIENT MAC Addr: . . .
                CLIENT IP: 192.168.0.1
                GATEWAY IP: 192.168.0.254
                
                Auto-select:
                     Network boot
                
                BOOT SERVER IP: 192.168.0.254
                TFTP...

        If it doesn't display any of this on the client
        screen, you aren't getting the right info from
        dhcpd.  I would verify basic connectivity first
        and verify that you are connecting to the right
        dhcpd server.
        
        Note that just because you change some values
        in the /etc/dhcpd.conf file, you have to restart
        the dhcpd daemon to make it effective:
        
                # /sbin/service dhcpd restart

4. tftp server

        I noticed an error in your configuration:  your
        dhcpd.conf file specifies the boot image:
        
                /tftpboot/lts/vmlinuz-2.4.19-ltsp-1
        
        It should be:
        
                /lts/vmlinuz-2.4.19-ltsp-1
        
        since your tftp config file sets its root directory
        as "/tftpboot".
        
        After the initial dhcp exchange, the boot image
        is retrieved with tftp.  It will say something
        like:

                BOOT SERVER IP: 192.168.0.254
        
        This IP address must match your server and the
        image be available where advertised.  I verify
        that it is available using the "tftp" client:
        
                $ tftp 192.168.1.100
                tftp> get /lts/vmlinuz-2.4.19-ltsp-1
                Received 1428636 bytes in 2.6 seconds
                tftp> 
        
        If this doesn't work, your basic tftp service
        is not working.

I think this should be enough to get you going.

Tom

-- 
----------------------------------------------------------------------
   Thomas L. Griffing       Red Hat Certified Engineer
   Pondus Solutions, Inc.   mailto:[EMAIL PROTECTED]




-------------------------------------------------------
This SF.net email is sponsored by: VM Ware
With VMware you can run multiple operating systems on a single machine.
WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines at the
same time. Free trial click here: http://www.vmware.com/wl/offer/345/0
_____________________________________________________________________
Ltsp-discuss mailing list.   To un-subscribe, or change prefs, goto:
      https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help,   try #ltsp channel on irc.freenode.net

Reply via email to