PXE boot problem when using DHCP policy

[scgsg]

This may have come up before, I wanted get legacy to work with uefi so on my windows 2016 dhcp server i configured a policy for legacy (vendor PXEClient:Arch:00000) and set 66 + 67. The client loads and gets to bit where it gets an ip address but after a while fails with ‘PXE-E53: No Boot Filename Received’ so it looks like the policy works in part. Ok now here’s the weird bit, instead of using a policy, if I set the options directly as DHCP options with the same settings it works perfectly fine.

Any ideas whats going on here?

[george1421]

Follow the guidance here: https://wiki.fogproject.org/wiki/index.php/BIOS_and_UEFI_Co-Existence#Using_Windows_Server_2012_.28R1_and_later.29_DHCP_Policy

Setup up arch types 7 and 9. You can setup the others while you are there just in case you have a 32 bit uefi system (not really common) as long as you are in the neighborhood.

[george1421]

I may have read your post too quickly, so if after you confirm the settings according to the wiki page, you still have issues we can debug using a packet capture. If the fog server and the pxe booting computer is on the same subnet, please use this tutorial to capture the best quality pcap. https://forums.fogproject.org/topic/9673/when-dhcp-pxe-booting-process-goes-bad-and-you-have-no-clue

The pcap will show us what the target computer is being told to do.

If your pxe booting compute is on a different subnet then install wireshark on a witness computer (second computer not part of the pxe booting process). Use the wireshark capture filter of port 67 or port 68 to only capture the pxe boot.

Post the pcap to a file share site (like google drive) and either post the link in the thread or IM me the link and I will take a look at what the client is being told.