I should say that all my other models pxe boot just fine and recieve the "F8" menu.
These other 2 units will not get the LD pxe menu.
They are a Panasonic Toughbook CF-H1 and a Lenovo S20
Did you drop some items from the PXE menu?
BIOSes are using more memory these days and so the amount of text in the F8 menu sometimes is less on certain BIOSes.
Yes i tried that as well with still same results.
Thanks for responding
Ok the toughbook CF-H1 produces the error with no pxe number of "No filename or root path specified" but the Lenovo S20 actually produces the PXE-E53: No boot filename received.
Could the error message be shown differently due to the different hardware platforms?
On the other hand, my other units hit the PXE menu fine. Lenovo M58's, Dell Optiplex 755's
Check to see if these machines have any BIOS updates available?
1 of 1 people found this helpful
The PXE-E53 error indicates that your client got a DHCP address (such as from your standard DHCP server), but did not get the boot options that our PXE Representative should be sending.
You mentioned other devices boot just fine. Are they booting from the same subnet or VLAN? This might be the kind of thing that requires a wireshark capture on the PXE rep to see if we can find the DHCP request and see if we're sending a response.
Yes same subnet/Vlan I actually moved the not working unit to a connection that was working and it still did the same.
If you are using a IPHelper with option 66 DHCP
you can try to uncheck the options "for all Method" and "Broadcast discovery" ... in "Proxy DHCP Server"
Unchek option "send a large trame MTFTP" on configure boot server in section MTFTP options.
Restart service PXE and MTFTP.
Your network card on client computer use GPXE protocol ?
Thanks for the response CSI. I was really hoping that would work.
I do not have access to the DHCP server but i tried to change the MTFTP option of 'Transmit MTFTP large packets"
The one device that im trying to boot is just a handheld tablet type with Win7 going on them.
but they only have a wireless card and the NIC is only in the dock so not nic/pxe options in the BIOS.
I also couldnt find any BIOS updates for the Panasonic CF-H1
The other unit is a special model S20 that does have BIOS options for Net boot with PXE and they are enabled.
I have our TAM on it as well with no luck.
You can try to uncheck the options "for all Method" and "Broadcast discovery" ... in "Proxy DHCP Server LANDesK"
for more information look this article
tftp: No filename or root path specified
IBM Tivoli PXE Server 18.104.22.168 is reported to send trailing garbage
bytes at the end of the OACK packet, which causes gPXE to reject the
packet and abort the TFTP transfer.
Work around the problem by processing as much as possible of the OACK,
and treating name/value parsing errors as non-fatal.
gPXE wants to find the boot filename in the dedicated slot in the reply packet.
dnsmasq does something clever/stupid (I’m not sure which) and puts it
someplace else. You have to use the –dhcp-no-override option to
dnsmasq to make gPXE see the filename.