Good morning,
I just spent hours with this error while attempting a PXE deployment
NBP file name is ipxe.efi
NBP filesize is 0 bytes
download succeed
and the PC refused to boot
We have an ISC DHCP server running Linux, and we need to specify the size of the IPXE file that will be downloaded. To complicate matters, this file must be divided by 512
This requirement applies to UEFI BIOS versions higher than 2.3
If it helps...
[SOLVED] PB PXE NBP file size 0 Bytes
Forum Rules
Community Forum Rules
* English support on www.reddit.com/r/wapt
* French community support is available on this forum
* Please prefix the topic title with [RESOLVED] if it is resolved.
* Please do not edit a topic that is tagged [RESOLVED]. Open a new topic referencing the old one.
* Specify the installed WAPT version, full version, and build number (2.2.1.11957 / 2.2.2.12337 / etc.) as well as the Enterprise/Discovery edition.
* Versions 1.8.2 and earlier are no longer supported. The only questions accepted regarding version 1.8.2 are related to upgrading to a supported version (2.1, 2.2, etc.).
* Specify the server OS (Linux/Windows) and version (Debian Buster/Bullseye - CentOS 7 - Windows Server 2012/2016/2019).
* Specify the OS of the administration/package creation machine and the machine with the problematic agent, if applicable (Windows 7/10/11/Debian 11/etc.).
* Avoid asking multiple questions when opening a topic, otherwise it may be ignored. If there are multiple topics, open separate topics, preferably one after the other and not all at the same time (i.e., do not spam the forum).
* Include code snippets, screenshots, and other images directly in the post. Links to Pastebin, Bitly, and other third-party sites will be systematically removed.
* As with any community forum, support is provided voluntarily by members. If you require commercial support, you can contact Tranquil IT's sales department at 02.40.97.57.55
Community Forum Rules
* English support on www.reddit.com/r/wapt
* French community support is available on this forum
* Please prefix the topic title with [RESOLVED] if it is resolved.
* Please do not edit a topic that is tagged [RESOLVED]. Open a new topic referencing the old one.
* Specify the installed WAPT version, full version, and build number (2.2.1.11957 / 2.2.2.12337 / etc.) as well as the Enterprise/Discovery edition.
* Versions 1.8.2 and earlier are no longer supported. The only questions accepted regarding version 1.8.2 are related to upgrading to a supported version (2.1, 2.2, etc.).
* Specify the server OS (Linux/Windows) and version (Debian Buster/Bullseye - CentOS 7 - Windows Server 2012/2016/2019).
* Specify the OS of the administration/package creation machine and the machine with the problematic agent, if applicable (Windows 7/10/11/Debian 11/etc.).
* Avoid asking multiple questions when opening a topic, otherwise it may be ignored. If there are multiple topics, open separate topics, preferably one after the other and not all at the same time (i.e., do not spam the forum).
* Include code snippets, screenshots, and other images directly in the post. Links to Pastebin, Bitly, and other third-party sites will be systematically removed.
* As with any community forum, support is provided voluntarily by members. If you require commercial support, you can contact Tranquil IT's sales department at 02.40.97.57.55
- dcardon
- WAPT Expert
- Messages: 1929
- Registration: June 18, 2014 - 09:58
- Location: Saint Sébastien sur Loire
- Contact :
Hello Bruno67,
have you disabled Secure Boot on your machine? I've already encountered the exact same issue on Lenovo laptops with Secure Boot enabled, even though the IPXE file isn't signed.
The IPXE binary provided by the IPXE project isn't signed for Secure Boot. If you want to keep Secure Boot enabled during the initial installation, you need to:
* purchase an IPXE Anywhere license from 2pints Software
* perform a boot without IPXE (boot directly from the Microsoft BCD).
Regards,
Denis
have you disabled Secure Boot on your machine? I've already encountered the exact same issue on Lenovo laptops with Secure Boot enabled, even though the IPXE file isn't signed.
The IPXE binary provided by the IPXE project isn't signed for Secure Boot. If you want to keep Secure Boot enabled during the initial installation, you need to:
* purchase an IPXE Anywhere license from 2pints Software
* perform a boot without IPXE (boot directly from the Microsoft BCD).
Regards,
Denis
Denis Cardon - Tranquil IT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
- dcardon
- WAPT Expert
- Messages: 1929
- Registration: June 18, 2014 - 09:58
- Location: Saint Sébastien sur Loire
- Contact :
Hello Bruno67,
we have laptops with secure boot for internal testing/development on WADS, and secure boot was introduced with the UEFI 2.3.1 specification, so it's not always necessary to specify it.
It might depend on the implementation. What is the model of laptop you have (manufacturer and exact model number)?
Regards,
Denis
we have laptops with secure boot for internal testing/development on WADS, and secure boot was introduced with the UEFI 2.3.1 specification, so it's not always necessary to specify it.
It might depend on the implementation. What is the model of laptop you have (manufacturer and exact model number)?
Regards,
Denis
Denis Cardon - Tranquil IT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
- dcardon
- WAPT Expert
- Messages: 1929
- Registration: June 18, 2014 - 09:58
- Location: Saint Sébastien sur Loire
- Contact :
Hello Bruno67,
after investigation we found an issue in the TFTP server response where the `tsize` variable in the TFTP response has an extra null character (`\0`), which can cause problems for some TFTP clients. We are currently fixing and validating the fix. We found an internal laptop exhibiting the same behavior as yours, so we can reproduce the issue and validate the fix.
Sincerely,
Denis
after investigation we found an issue in the TFTP server response where the `tsize` variable in the TFTP response has an extra null character (`\0`), which can cause problems for some TFTP clients. We are currently fixing and validating the fix. We found an internal laptop exhibiting the same behavior as yours, so we can reproduce the issue and validate the fix.
Sincerely,
Denis
Denis Cardon - Tranquil IT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
Good morning,
I just tried a deployment on a new PC and the PXE boot in UEFI mode is stuck at:
Secure boot has been disabled.
I'm stuck...
I just tried a deployment on a new PC and the PXE boot in UEFI mode is stuck at:
Code: Select all
Downloading NBP file...I'm stuck...
- sfonteneau
- WAPT Expert
- Messages: 2318
- Registered: July 10, 2014 - 11:52 PM
- Contact :
Hello,
could you try the latest release I just pushed?
https://wapt.tranquil.it/wapt/releases/ ... -1b2dfbee/
Simon Fonteneau
could you try the latest release I just pushed?
https://wapt.tranquil.it/wapt/releases/ ... -1b2dfbee/
Simon Fonteneau
- sfonteneau
- WAPT Expert
- Messages: 2318
- Registered: July 10, 2014 - 11:52 PM
- Contact :
Can you tell me the server's operating system (Windows/Debian/Red Hat)?
Are you using WaptFTP Server?
I'd like to try switching you to another TFTP server to see if it's better, but I need the system information to guide you properly.
Are you using WaptFTP Server?
I'd like to try switching you to another TFTP server to see if it's better, but I need the system information to guide you properly.
