PXE boot error KACE

Hi all,

I'm facing problem PXE booting on multiple Lenovo Notebook even though all the settings in the BIOS are correct (Secure boot disabled and the boot order is set correctly and the BIOS is up-to-date) I tired both on UEFI  its says "NBP filesize is 0 bytes" and then "PXE-E23 client received TFTP error from server" and when i try legacy it says "NBPf ile is too big to fit in free base memory". It works fine on any other machine except for Lenovo machines.

Any Idea what might be causing it?
Any suggestion/solution is much appreciated.

2 Comments   [ + ] Show comments
  • I suggest creating an additional KBE, ensuring to select the UEFI option in media manager. - flip1001 3 years ago
  • Good morning, Gwin. Let's break this down to its component parts. First, what are you using for your DHCP configuration for PXE? Can you list the configuration here? For example, is it Windows Server DHCP, Cisco IOS, or something else? - WhatsATOF 3 years ago

Answers (2)

Posted by: Nico_K 3 years ago
Red Belt

at first: try to update to the latest BIOS versions.

Which model(s) are affected? Vendor, Make, Build, BIOS version.

Sometimes the bootcode is problematic and needs to be fixed from the vendor. You can check with the vendor if they have issues with PXE boot.

As a workaround is using a USB KBE.

  • Hi Nico

    Thanks for your reply as mentioned I've already updated the BIOS to the latest version.
    Vendor Lenovo
    Models: ThinkPad X1 carbon (4th Gen), ThinkPad T460s, ThinkPad T550.
    BIOS version: 1.47.

    I tried using USB KBE but when I try to flash the KBE using the install.exe (after the operation is done) the USB drive become unusable (like if it's broken or something, you can not even open it) I tried multiple USB drives. The flashing of the System Image via install.bat is fine though. - Gwin 3 years ago
Posted by: CarstenBuscher 3 years ago
Purple Belt

Check the firewall. We had the same error when we changed from legacy to uefi boot and the problem was that the restrictions on the firewall was to high. We opened the ports (1024 to 65535) for in- and outgoing traffic and everything was fine.

The inital communication starts on the lower portrange (https://support.quest.com/de-de/kb/129799/network-ports-needed-for-the-kace-systems-deployment-appliance-sda-) and then an dynamic port is used.

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login


This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ