When attempting to network-boot a device via iPXE, the process halts at the message: “No configuration methods succeeded”. The device then falls back to the next boot option or loops indefinitely.
iPXE prints this message when it cannot finish its automatic network-configuration step (usually DHCP) before the built-in timeout expires. In the captured logs, the NIC momentarily resets while iPXE takes control; during that brief reset, the switch port drops the link and re-enables spanning-tree processing. Because the port is not running a “fast-start” mode (PortFast, Edge, or fast-STP), it spends several seconds in a blocking state, so iPXE’s DHCP request times out and the 040ee1 error appears.
In summary, the network itself is healthy, but the NIC card or USB dongle is too slow to forward traffic after the tiny link-flap that occurs during chain-boot.
Current Scenario (Field Observation)
The issue occurs even with previously known-good USB–NIC dongles and docking stations. Reverting BIOS firmware has no impact, confirming the root cause is external to the workstation hardware.
10secdelay/undionly.kpxe (BIOS/legacy)10secdelay/ipxe.efi (UEFI)
or