NBP filesize is 0 Bytes; PXE-E18: Server response timeout

  • @foggymind Did some more testing and legacy PXE boot doesn’t work either, with error E-23. So I think it might be something related to the TFTP service. Not sure how to verify the status but I’ll do some digging to see what I can find.

  • Moderator

    @foggymind ok with the fog server and cleints on the same subnet we can get the fog server to listen in on the dhcp process. https://forums.fogproject.org/topic/9673/when-dhcp-pxe-booting-process-goes-bad-and-you-have-no-clue

    This will capture the pxe booting process. Once captured you can load into wireshark or upload so one of us can look at it. What you want to look for is multiple OFFER packets. You should have one from each DHCP that hears the clients DISCOVER packet. Look to see if you have more offer packets than known dhcp servers.

    Also look into the Discover packet, there should be the bootp settings in the ethernet header. You should see a {next-server} this should point to your fog server’s IP as well as a {boot-file} that should be the name of the boot loader (undionly.kpxe for bios and ipxe.efi for uefi systems). Then down in the dhcp options make sure 66 is the ip address of the fog server and 67 is the proper boot loader. Do this for every offer packet making sure they ALL point to the same settings.

  • @foggymind Some background, both UEFI and legacy PXE were working fine before this.

  • @george1421 Thanks for the quick reply! I’m waiting to hear back to see if our DHCP servers are in sync, but the fog server and client are both on the same subnet. I did check the configuration for 66/67 and they are correct on all three DHCP servers so I think everything is configured correctly it just seems like that TFTP service isn’t running for some reason or something is blocking it. This error happens when attempting UEFI boot, but I just tried a legacy PXE boot and the got the message PXE-E32 TFTP open timeout.

  • Moderator

    @foggymind Are all three DHCP server, fog server and target computer on the same subnet? If not can you install wireshark on a witness computer (second computer on the same subnet as the pxe booting computer)? If so please run with a capture filter of port 67 or port 68 and then upload the contents to a file share site and post the link here. Ideally if you can capture the error being generated that would tell us what is broke.

  • Senior Developer

    @foggymind Quite often the DHCP sync is “out of sync”. Have you double checked?