On 5/24/06, Cristi Mitrana <[EMAIL PROTECTED]> wrote:
from the tcpdump lines it seems the network is down on the ltsp client. Can you check and see if it's still connected after loading the etherboot image (power leds, ping from server). I remember some time ago that I had trouble getting etherboot to recognize the NIC you described.
I tried pinging the client throughout the whole process and even when it was downloading the kernel, I still didn't get a response. The ping was done from the LTSP server. How strange.
One thing you could try is a PXE boot (instead of the etherboot cdrom) and load the initial kernel via PXE instead of etherboot.
Ok, I changed the following setting on the DHCP server: 067 Bootfile Name /lts/2.6.16.1-ltsp-2/pxelinux.0 Now after fixing a spelling error in the Root Path in DHCP it works nicely. Thanks for your help. -- Later David Kirk ------------------------------------------------------- All the advantages of Linux Managed Hosting--Without the Cost and Risk! Fully trained technicians. The highest number of Red Hat certifications in the hosting industry. Fanatical Support. Click to learn more http://sel.as-us.falkag.net/sel?cmd=lnk&kid7521&bid$8729&dat1642 _____________________________________________________________________ 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
