pxe not using the right file.

[t_dashs]

I am trying to capture an image but pxe will will not load the right image that was in the docs It loads undionly.kkpxe instead of ipxe.pxe. How would I go about fixing this?

[george1421]

@t_dashs Well to answer your question exactly, update dhcp option 67 on your dhcp server. If fog is your dhcp server for this network then its the dhcp config file that needs to be adjusted.

BUT undionly.kpxe is the right boot loader for a bios computer. Your issue is something completely different.

Your issue is (probably) you have 2 dhcp servers on your network.

See how this works is that when your computer is turned on and PXE booted. The PXE rom in your nic queries for a dhcp address and boot server and boot file name. That info is being given to the PXE rom because it download undionly.kpxe. When iPXE starts up it takes over the NIC from the PXE rom and then again queries for dhcp address, boot server and boot file name. What it should get back is the same as what the PXE rom recieved. In your case iPXE did not receive a boot server name so its asking for it. It should be given automatically via the dhcp offer from your dhcp server.

We see this often when you have 2 dhcp server (one primary and one secondary) and the secondary dhcp server doesn’t have the pxe boot settings configured.

[t_dashs]

Just checked I have 2 dhcp server. I was able to get it to boot into the PXE interface by typing in the ip of my server.

[george1421]

@t_dashs Right you can do that by typing in the IP address of your fog server. But the root of the problem is that you have at least 1 dhcp server not handing out the complete information. Understand this is an network infrastructure problem not specifically a FOG issue.

If you have a computer loaded with wireshark on the same subnet as the pxe booting computer we might be able to find out which one is wrong. You will want to use a wireshark capture filter of port 67 or port 68 Start the wireshark capture then pxe boot the target computer til you get this error. Stop wireshark from scanning. In the data area you will see a discover package sent from the target computer and one or more OFFER packets. The problem lies in one of these offer packets. Either the next-server or dhcp option 66 is not set on the offending dhcp server.