Articles on: ggRock
This article is also available in:

PXE Boot Troubleshooting

This article details steps to troubleshoot connectivity during the PXE boot phase of ggRock



Problem


Computers fail to PXE boot with "No More Network Devices" or any other PXE-related error (Typically Exx, where xx is some number)


Solution


Please refer to the iPXE troubleshooting guide here for more information:
https://ipxe.org/cmdline


  1. Reboot, or turn on any machine in the center


  1. After PXE boot begins, press CTRL+B on the keyboard to access the iPXE command line.



  1. Type config at the prompt, which should show all settings.


  1. Select the net0 interface, and you should see things filled in for IP address, Netmask, filename, etc.


  1. If it fails at the dhcp command or one of the above fields in empty, then there is a problem with the DHCP response packet.


Network settings to verify


For intermittent PXE failures, have the network team verify the following:


  • Use IPv4 for PXE boot; do not allow the client to select IPv6 for this process.
  • Confirm that the server and client machines are on the same network segment, or that routing and PXE forwarding between their segments is configured correctly.
  • Check that there are no other PXE responders on the VLAN or broadcast domain.
  • Confirm that DHCP options 66 (next-server) and 67 (boot filename) are not configured on the DHCP scope for this network segment.
  • Check DHCP server logs at the time of a failed boot for address-allocation failures, dropped requests, or a depleted scope.
  • On access switch ports connected to PXE clients, verify that STP edge/PortFast is enabled. Also check switch logs for broadcast storm-control events.
  • If failures continue, capture a failed boot and check for multiple DHCP Offers, delayed DHCP responses, or TFTP/HTTP file-transfer errors. A capture can be made on the ggRock server with:


sudo tcpdump -i any -s 0 -w pxe_boot_troubleshoot.pcap 'port 67 or port 68 or port 69 or port 4011 or port 80'


  1. Check that the LAN cable is properly connected between the PC and the network switch. Swap the cable with one from a working PC to rule out a faulty cable or port.


  1. If the PC still cannot find the server, try booting an older snapshot of both the regular Windows image and the game image. If an older snapshot boots successfully, the problem may be related to the current snapshot.


  1. If all of the above fails and you have verified DHCP functionality on your network, please contact a member of the support staff via the purple chat bubble at the lower-right.

Updated on: 10/11/2026

Was this article helpful?

Share your feedback

Cancel

Thank you!