Hi Gavin, I was just doing that when you responded. Here is dhcp.conf
authoritative;
subnet 192.168.0.0 netmask 255.255.255.0 {
range 192.168.0.20 192.168.0.250;
option domain-name "example.com";
option domain-name-servers 192.168.0.1;
option broadcast-address 192.168.0.255;
option routers 192.168.0.1;
option subnet-mask 255.255.255.0;
if substring( option vendor-class-identifier, 0, 9 ) = "PXEClient" {
filename "/ltsp/i386/pxelinux.0";
}
else{
filename "/ltsp/i386/nbi.img";
}
option root-path "/opt/ltsp/i386";
}
After doing a search, I cannot find " /ltsp/i386/pxelinux.0" or
"/ltsp/i386/nbi.img" niether can I find the path "/opt/ltsp/i386"
There is a "/opt/ltsp/amd64" there is a /var/lib/tftpboot/ltsp/amd64 that
contains pxelinux.0 but no nbi.img I am going to change dhcp.conf to point
to /var/lib/tftpboot/ltsp/amd64/pxelinux.0 and the root path to
/opt/ltsp/amd64. I am not sure about /ltsp/i386/nbi.img as there is no
nbi.img
Regards,
Paul
On 2/5/07, Gavin McCullagh <[EMAIL PROTECTED]> wrote:
On Mon, 05 Feb 2007, Paul J. Thompson wrote:
> The client finds the dhcp server at 192,168.0.1. It gets an address
> 192.168.0249 then comes up with the following error messages:-
>
> TFTP
> PXE-T01 file not found
> PXE-E3B - TFPT error
> PXE-M0F exiting Intel PXE ROM
It looks like the dhcp bit worked and the client tried to run tftp to
download the kernel and initrd.img files. One or both of these was not
available "file not found".
I'd suggest looking at the parameters in /etc/ltsp/dhcpd.conf and check
that the files in /var/lib/tftpboot/ are in place where the dhcp server is
claiming.
In fairness, if you've run ltsp-build-client I'd expect that to be sorted
already but maybe not.
Gavin
--
edubuntu-users mailing list
[email protected]
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/edubuntu-users
--
edubuntu-users mailing list
[email protected]
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/edubuntu-users
