@SharonLampe well this one is pretty interesting cause I’m seeing double vision on this one.

A quick diagram would be this.

Packets 31 to 35 are the same client saying hello I’m here world I need configuring. This is remarkable since this should only happen in one packet. Its the client sending out 4 dhcp discover requests rapid fire. I can see from this discover packet that this is a Dell computer that is running in bios mode. (so undionly.kpxe needs to be sent for dhcp option 67 {boot-file} and this is just a wild guess that is is one of the older dells (pre o7010). Packets 35 to 50 are replies from your dhcp server. This again is remarkable since there should only be one reply from your dhcp server. Looking at the time codes I can see these are in 3 groups of 4 responses each (which seems to align with the 4 packets send in step 1. looking at the dhcp server reply I can see that dhcp server 10.0.0.8 is replying to your client. And the address its replying with your IP address is 10.0.20.92 with a next server of 10.0.0.8 (your dhcp server!! which should be your FOG server if you want pxe booting to work). The subnet mask is 255.255.0.0 so both the dhcp server and the target computer are in the same subnet (this is good). Your upstream router is 10.0.0.1 (not really relevant). In that same conversation ID you have a second dhcp server 10.0.0.9 responding to the target computer with your IP address is 10.0.21.9 (not typically a good thing). Its telling the target computer that its next server (dhcp option 66) is itself 10.0.0.9 (still not good for pxe booting, this next server must be the FOG server).

OK from here I’ve seen enough to know why its not working.

Lets identify what servers are 10.0.0.8 and 10.0.0.9 are. Once that is figured out, we need to ensure they have dhcp options 66 {next-server} (should be your FOG server’s IP address) and dhcp options 67 {boot-file} (should be undionly.kpxe for bios based computers) values set. Right now they are not sending the client the proper information to boot via pxe.

And while this is only a suspicion I question why the target computer is ending out multiple dhcp discover requests. This is either because of a network misconfiguration, or something is not right with that target computer. There should be just one disover, with a reply from the dhcp server, then the target computer providing a full list of parameters its needs, and then finally the target computer responding with (OK got it). That should be 4 packets total to 30 ish packets.