@eldiablo909 I think we are back to requiring a pcap file so we can see what is going on… on the wire. Make sure tcpdump is installed on your FOG server then run the following command

tcpdump -w output.pcap port 67 or port 68 or port 69

Next pxe boot the client computer. You will get the question for the fog server IP enter it and take it to the final error where you can’t go any more. Then post the pcap file here. We’ve instructed tcpdump to only capture broadcast bootp and tftp requests.

@eldiablo909 We see that the first round of DHCP seems to work out because the Intel® PXE boot ROM is able to grab an ip, get next-server/filename info and load the iPXE binary. One thing I notice here is the DHCP server IP address being totally different to the client IP and gateway address. This does not have to be an issue. It’s just a bit unusual and I wanted to point this out in case…

Version 6213 might not be the very latest but from what I see in the repo we haven’t changed the embedded iPXE script since then. So upgrading to the very latest won’t help I reckon!

From the message you see it seems like your DHCP server does not send next-server (option 66) on the second DHCP round (when iPXE is asking). Possibly your DHCP server decided to not like the DHCP options send by iPXE/gPXE/Etherboot anymore (e.g. option 175).

Just for sanity sake, please type in the fog servers IP address here. What I’m interested in is does it boot properly post this error message.

For this error message resolution we will probably need a pcap file of the communications here. Because within the ipxe kernel its getting the IP address but its not getting the dhcp options for {boot-server} or possibly {bootfile}. Or you have a dhcpPROXY that is giving extra information.

The other noteworthy thing is that you might want to upgrade to latest on the trunk build. Your release is a bit behind the times.