PXE-E32: TFTP open timeout

[mark29]

Good evening, I am a newbie on FOG and on this forum, I hope you could help me with this issue. I installed FOG ver 1.5.10 on several VMs (VMware Workstation Pro) running Kubuntu 22.04 LTS, without problems capturing or deploying images. But lately in a laptop always on a VM Kubuntu 22.04 LTS created with VMware Workstation Pro, Fog version 1.5.10, I’m having a problem when I try to capture the image from my source PC … it screens PXE-E32: TFTP open timeout. The settings are the same of other VMs I set before where I have no problems…
Have you some ideas about?
Thank you in advance for your help.

[george1421]

@mark29 said in PXE-E32: TFTP open timeout:

it screens PXE-E32: TFTP open timeout.

This can be (most commonly) caused by either

1. DHCP options for that subnet have dhcp options 66 set incorrectly.
2. You have two or more dhcp servers on that subnet and both don’t have all of the setting needed to pxe boot.
3. The tftp service is not running on your fog server.

I would setup a witness computer on the same subnet as the pxe booting computer that witness computer will run wireshark, with a capture filter of port 67 or port 68 or use a display filter of BOOTP. Start wireshark and then pxe boot the target computer until you get the error, then stop the wireshark capture.

Now review in wireshark the OFFER packet. This comes from the dhcp server to the client.

1. Look to see if you only have one OFFER packet. You should because the pxe error is “Open timeout”.
2. Look at the OFFER packet in the ethernet header verify that both the {next-server} field has the IP address of the FOG server, and the {boot-file} has the proper FOG boot loader.
3. Now look at the DHCP options under option 66 and 67 they should match whats in the ethernet header.

FWIW: I’ve seen soho routers that eventhough you properly configure them, they set themselves (the routers) as the pxe boot server and not what you put in dhcp option 66.