@punch07 I agree from the picture everything looks good.
What we don’t know is the number of actors involved with this pxe booting process. We really need to know what the client is being told and by who.
Follow the instructions in this tutorial. Collect the pcap and look at it with wireshark.
https://forums.fogproject.org/topic/9673/when-dhcp-pxe-booting-process-goes-bad-and-you-have-no-clue
What will be specifically interesting will be the OFFER packets. If you only have 1 dhcp server on your network you should have only one OFFER packet. If you have more than 1 then you need to identify each dhcp server that is responding.
If you have only one OFFER packet, then look into that packet. In the ethernet header you should have two fields. {next-server} and {boot-file} those settings should match what you have set in dhcp options 66 and 67. Both the bootp section and the dhcp options section need to be set.
If you can’t figure out the pcap, unload the pcap to a public file share site and paste the link here. We can take a look at the pcap and give you additional guidance on where to look, but in the pcap file you should see at least 4 packets, DISCOVER, OFFER, REQUEST, ACK/NACK. The OFFER packet comes from your dhcp server(s).
One additional note if you have a primary and backup dhcp servers make sure both have the boot settings configured.
EDIT: I just thought of another issue it might be. If you did not complete the installation properly the /tftpboot directory on the fog server might be empty. Double check to see if you have ipxe.efi in that directory. If its not there, make sure you complete all 3 phases of the install. fog server console->web ui to install database-> fog server console to complete the install.
