Problem accessing the Wapt server on the client side
Published: March 4, 2026 - 12:21
Hello,
I'm testing a Windows deployment via WAPT on a VirtualBox 7.2.4 environment.
As a reminder, I installed WAPT version 2.6 on Rocky 10.
I configured the DHCP server; here is the dhcpd.conf file:
..............................................................................................................................................................................
subnet 172.16.1.0 netmask 255.255.255.0 {
range 172.16.1.120 172.16.1.180;
option routers 0.0.0.0;
option subnet-mask 255.255.255.0;
option broadcast-address 172.16.1.255;
next-server 172.16.1.100; # TFTP server
# If not iPXE
if not exists user-class {
# If legacy BIOS
if (option vendor-class-identifier = "PXEClient:Arch:00000") {
filename "boot/pxeboot.n12";
} else {
filename "efi/boot/bootmgfw.efi";
}
}
# If iPXE
else if option user-class = "iPXE" {
# If legacy BIOS
if (option vendor-class-identifier = "PXEClient:Arch:00000") {
filename "http://172.16.1.100/api/v3/baseipxe?uef ... &keymap=fr";
} else {
filename "http://172.16.1.100/api/v3/baseipxe?keymap=fr";
}
}
..............................................................................................................................................................................
Testing this command on the client side works fine:
...............................................................................................................................................................................
cd ~
tftp 172.16.1.100;
binary
get snponly.efi
quit
ls -l snponly.efi
..............................................................................................................................................................................
When I then test the Windows deployment after adding the Windows ISO and an answer file, I find that the rest doesn't work. The client correctly obtains an IP address, but it stops at the TFTP connection
with error messages:
.......................... .................................................................................................................................
client mac addr: 08 00 27 5c b2 0c ..................
client ip: 172.16.1.140 mask: 255.255.255.0 dhcp ip: 172.16.1.110
TFTP
pxe-t01: file not found
pxe-e3b: tftp error - file not found
pxe-m0f:Exiting Intel pxe rom
..................................................................................................................................................................
I can get an IP address, but the TFTP connection is stuck; I don't understand why.
I'm wondering what I'm missing, whether I enable UEFI or not in the client-side BIOS.
Thanks in advance for your help.
I'm testing a Windows deployment via WAPT on a VirtualBox 7.2.4 environment.
As a reminder, I installed WAPT version 2.6 on Rocky 10.
I configured the DHCP server; here is the dhcpd.conf file:
..............................................................................................................................................................................
subnet 172.16.1.0 netmask 255.255.255.0 {
range 172.16.1.120 172.16.1.180;
option routers 0.0.0.0;
option subnet-mask 255.255.255.0;
option broadcast-address 172.16.1.255;
next-server 172.16.1.100; # TFTP server
# If not iPXE
if not exists user-class {
# If legacy BIOS
if (option vendor-class-identifier = "PXEClient:Arch:00000") {
filename "boot/pxeboot.n12";
} else {
filename "efi/boot/bootmgfw.efi";
}
}
# If iPXE
else if option user-class = "iPXE" {
# If legacy BIOS
if (option vendor-class-identifier = "PXEClient:Arch:00000") {
filename "http://172.16.1.100/api/v3/baseipxe?uef ... &keymap=fr";
} else {
filename "http://172.16.1.100/api/v3/baseipxe?keymap=fr";
}
}
..............................................................................................................................................................................
Testing this command on the client side works fine:
...............................................................................................................................................................................
cd ~
tftp 172.16.1.100;
binary
get snponly.efi
quit
ls -l snponly.efi
..............................................................................................................................................................................
When I then test the Windows deployment after adding the Windows ISO and an answer file, I find that the rest doesn't work. The client correctly obtains an IP address, but it stops at the TFTP connection
with error messages:
.......................... .................................................................................................................................
client mac addr: 08 00 27 5c b2 0c ..................
client ip: 172.16.1.140 mask: 255.255.255.0 dhcp ip: 172.16.1.110
TFTP
pxe-t01: file not found
pxe-e3b: tftp error - file not found
pxe-m0f:Exiting Intel pxe rom
..................................................................................................................................................................
I can get an IP address, but the TFTP connection is stuck; I don't understand why.
I'm wondering what I'm missing, whether I enable UEFI or not in the client-side BIOS.
Thanks in advance for your help.