@Sebastian-Roth Found a firmware update for the model and took a peek at it’s change log. Didn’t see anything relating to PXE in recent changes. Ran it anyway to bring it current. No changes in PXE boot behavior.

@george1421 Ran a capture job before I left Friday using the FOSLinux usb boot method. Checking the deploy sometime today.

As always, thanks for you help you two!

@george1421 thank you, this was actually going to be my next step. Appreciate you heading me off with some solid info to work with.

@george1421 Set up an isolated network with just the FOG instance running DHCP, the workstation, and tried 3 different switches; the Cisco and Dlink I mentioned previously, as well as, a TPLink 6 port switch I found that appeared to be the ‘dumbest’ in the office. Received the same screen.

@Sebastian-Roth I tried realtek.efi, received same screen.

@george1421 Noted. We do have the same NIC in our laptops and they are getting to the FOG ok. Haven’t tried a registration or deploy yet but I do get to the menu. Finger crossed we don’t hit the wall because they are 8168s.

@EduardoTSeoane We’re in an UEFI ~only environment. There is still some legacy but we’re moving away from it. Thanks for the input thought!

@Sebastian-Roth Confirmed spanning tree on our main switch stack. Will segregate our imaging network and set up FOGs dhcp. I’ll check back in soon.

Backed up original ipxe efi and downloaded one recommended. No change.

@Sebastian-Roth Understood, I’ll verify our use of spanning tree in our network (new guy here, trying to bring the joy of imaging :D)

Only one DHCP server in the building, pretty small office.

@Sebastian-Roth I’ll give that a try at my next opportunity.

I failed to mention that FOG is not running DHCP, this is run by a Windows server. Vendor classes for efi/legacy booting have been configured on that server.

Would a switch with spanning tree between DHCP and fog/workstation throw this error as well?

@george1421 @Sebastian-Roth The switch I have both the FOG instance and the workstation plugged into is unmanaged (cisco sg100d-08). I’ve also tried on DLink umanaged switch (dLink dgs-1016d).

Hardware ID is PCI\VEN_10EC&DEV_8168&SUBSYS_314117AA&REV_0E

@Sebastian-Roth We’re on FOG version 1.5.6

Trying to network boot some new workstations but receive the message no configuration methods succeeded followed by the URL to the ipxe article on DHCP timeout.

Able to boot legacy on the devices with undionly. Able to boot legacy and uefi ipxe.efi on laptops with the same model NIC. What am I missing?
Happy to provide additional information.