I'm attempting to use a SuSE 9.2 machine as a terminal server.
However, I'm running into problems with TFTP. When the clients boot
they receive an IP address, but when they connect to the TFTP
server, the following error is returned:
PXE-T01: File not found
PXE-E38- TFTP Error - file not found
PXE-M0F- Exiting Intel Boot Agent
I checked to make sure that my settings were in accordance with the
advice given here, and everything checks out. My TFTP server is using
/tftpboot as root, everything is installed, and everything is enabled.
However, my clients aren't finding the kernel image they need when
trying to connect to the server.
Anyone have any ideas?
Here is my dhcpd.conf file.
________________________________________________________________________
default-lease-time 21600;
max-lease-time 21600;
ddns-update-style none;
allow booting;
allow bootp;
option subnet-mask 255.255.255.0;
option broadcast-address 192.168.0.255;
option routers 192.168.0.254;
option domain-name-servers 192.168.0.254;
option domain-name "ltsp";
option root-path "192.168.0.254:/opt/ltsp/i386";
option option-128 code 128 = string;
option option-129 code 129 = text;
option option-221 code 221 = text;
shared-network WORKSTATIONS {
subnet 192.168.0.0 netmask 255.255.255.0 {
range dynamic-bootp 192.168.0.100 192.168.0.253;
use-host-decl-names on;
option log-servers 192.168.0.254;
# trick from Peter Rundle <[EMAIL PROTECTED]>
# newer Macs
if substring (option vendor-class-identifier, 0, 9) = "AAPLBSDPC"
{
filename "yaboot";
option vendor-class-identifier "AAPLBSDPC";
}
# really old iMacs
elsif substring (option option-221, 0, 5) = "Apple"
{
filename "yaboot";
option vendor-class-identifier "AAPLBSDPC";
}
# Intel PXE
elsif substring (option vendor-class-identifier, 0, 9) = "PXEClient"
{
# NOTE: kernels are specified in /tftpboot/lts/pxe/pxelinux.cfg/
filename "/lts/pxe/pxelinux.0";
}
# default to an i386 BOOTP image
else
{
filename "/lts/vmlinuz.ltsp";
}
if substring (option vendor-class-identifier, 20, 3) = "ppc" {
option root-path "192.168.0.254:/opt/ltsp/ppc";
} else {
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/vmlinuz.ltsp";
option option-128 e4:45:74:68:00:00;
option option-129 "NIC=3c509";
}
host ws002 {
hardware ethernet 00:D0:09:30:6A:1C;
fixed-address 192.168.0.2;
filename "/lts/vmlinuz.ltsp";
option option-128 e4:45:74:68:00:00;
option option-129 "NIC=ne";
}
host ws003 {
hardware ethernet 00:D0:09:30:28:B2;
fixed-address 192.168.0.3;
# kernels are specified in /tftpboot/lts/boot/pxe/pxelinux.cfg/
filename "/lts/boot/pxe/pxelinux.0";
}
Thank you,
Ben Murphy
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_idt77&alloc_id492&op=click
_____________________________________________________________________
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
