PXE Boot not working - Windows 2019 DHCP

[multipass]

Hey,

I’m having trouble getting my machines to boot to FOG.
On a BIOS machine it just times out at the TFTP stage
On a Lenovo UEFI machine I just get “boot failed”
I have disabled secure boot.

I am running FOG on a Debian 11 VM on an ESXI host
our DHCP server is a windows 2019 server

I’ve set option 66 to the IP of the fog machine
option 67 is udionly.kpxe

I did follow the windows 2012 settings in this guide but it didn’t help
https://wiki.fogproject.org/wiki/index.php/BIOS_and_UEFI_Co-Existence#Using_Windows_Server_2012_.28R1_and_later.29_DHCP_Policy

I’ve probably done something wrong (I blame the UK heatwave) so I’m hoping someone can hold my hand and help me out.

Cheers

[JJ Fullmer]

@multipass Is this a completely new setup or was it working and it broke?
The BIOS and UEFI co-existence page might need some updating, but I believe it’s still accurate from the last time I utilized it. I don’t use the co-existence anymore because we were able to get all uefi machines.

I’d try to get it work without the vendor policies first and then add those after.

If you have a way to mount the TFTP share of fog elsewhere, that would be a good test to make sure that’s running correctly
I also find setting the options for DHCP per scope is helpful

[multipass]

@jj-fullmer This is a completely new setup.

Are there any guides you’ve seen for moving the TFTP share?

[george1421]

@multipass said in PXE Boot not working - Windows 2019 DHCP:

option 67 is udionly.kpxe

Hopefully this is just a type-o in this thread, but the file name is undionly.kpxe you are missing the n in the name. Secondly undionly.kpxe is a bios boot loader. For uefi you need to send ipxe.efi or snp.efi in dhcp option 67.

Is the FOG server on the same subnet as the target computer? If yes then we might want to grab a packet capture [pcap] of the pxe booting process.

[multipass]

@george1421 that was a typo in the thread, ive changed option 67 to ipxe.efi and I’ve now noticed that on a UEFI machine I very briefly get the below

NBP filename is ipxe.efi
NBP filesize is 0 bytes
PXE-E99: Unexpected Network Error.

[george1421]

@multipass Is the fog server on the same ip subnet as the target computer?

Is the fog server at the same site as the pxe booting computer?

[multipass]

@george1421 yeah its on the same network

[george1421]

@multipass ok would you follow this tutorial to capture a pcap of the pxe booting process. https://forums.fogproject.org/topic/9673/when-dhcp-pxe-booting-process-goes-bad-and-you-have-no-clue

Upload that pcap to a file share site and DM me the link using FOG chat. I’ll take a look at it for the next steps. The capture filter will only collect the dhcp process and no other traffic on your network.