Page 2 of 2
Re: Problem accessing the Wapt server on the client side
Published: March 4, 2026 - 7:20 PM
by sfonteneau
I just noticed a significant error in:
/usr/lib/systemd/system/wapttftpserver.service.
You should have:
--root_dir=/var/www/wads/pxe
, but it should be:
--root_dir=/var/www/html/wads/pxe.
Try replacing `reload / restart`.
Re: Problem accessing the Wapt server on the client side
Published: March 6, 2026 - 12:44 PM
by Regis
Hello,
I modified the file /usr/lib/systemd/system/wapttftpserver.service and restarted the service.
However, when I run this command, it still fails, so on the Wapt client side, it still fails:
tftp srvwapt3.domain.fr
tftp> binary
tftp> get efi/boot/bootmgfw.efi
Transfer timed out.
tftp>
There seems to be a problem with the wapttftpserver service.
Thank you in advance for your reply.
Re: Problem accessing the Wapt server on the client side
Published: March 6, 2026 - 1:52 PM
by sfonteneau
I just retested on an AlmaLinux 10 system.
After modifying wapttftpserver.service on my system, I can confirm that it works.
Verify that the correct folder is present here:
`ps aux | grep wapttftpserver.bin`
Re: Problem accessing the Wapt server on the client side
Published: March 6, 2026 - 1:59 PM
by Regis
It works on my server itself, but not on a client machine. On
the WAPT client side, when I try to boot, I now get the following message:
........................................................................................................................................................................................................................................
PXE-E79: NBP is too big to fit in free base memory
PXE-M0F: Existing Intel PXE ROM
.........................................................................................................................................................................................................................................
I wonder what this means
Re: Problem accessing the Wapt server on the client side
Published: March 6, 2026 - 3:46 PM
by Regis
It seems to be switching to UEFI mode, not Legacy mode. It's currently stuck due to a domain name issue when it launches the DOS console:
...................................................................................................................................................................................................................................
VerifyCert: X:\SSL\server\server.crt
Using wads repo URL
https://srvwapt3.domaine.fr/wads for our IP 172.16.1.133
wads exe URL: https://srvwapt3.domaine.fr/wads/wads64.exe
DNS resolution has failed for: srvwapt3.domaine.fr .
DNS resolution has failed for: srvwapt3.domaine.fr
DNS resolution has failed for: srvwapt3.domaine.fr .
............................................................................................................................................................................................................................
Re: Problem accessing the Wapt server on the client side
Published: March 6, 2026 - 5:44 PM
by sfonteneau
Regis wrote: ↑March 6, 2026 - 3:46 PM
It seems to be running in UEFI mode, not Legacy mode.
Indeed, efi/boot/bootmgfw.efi is for UEFI only
https://www.wapt.fr/fr/doc/wapt-wads.ht ... figuration
In hybrid mode, we use IPXE for legacy systems and efi/boot/bootmgfw.efi for UEFI systems