The client computer requested a PXE boot menu and did not receive sufficient instructions on how to get one.
The basic PXE process starts with a DHCP request which is expecting responses that include 1) an IP address for the booting system, 2) the address of the PXE server and 3) the name of the .0 or .efi file (the PXE boot menu). If only #1 is returned and not 2,3, an E53 error is displayed.
Following are some possible reasons this might happen.
- (GSS 3.x & 6.x) In the PXE Configuration utility, under the DS/GSS tab, the option for "Enable response to request from computers not in the DS/GSS Database" box is not enabled which stops new computers from being able to receive the PXE boot menu. Also there is an option under the same DS/GSS tab for "Enable response to computers with active DS job assigments only". If this option is checked computers with no DS job scheduled will get the PXE-E53 error when attempting to PXE boot.
- The PXE server service is not running. Either this service failed to start up when the computer first booted, or it started up, and then stopped afterward for some reason.
- The network infrastructure is not configured properly for the PXE server to see DHCP requests from the client computers and respond back with the PXE boot menu. This could be caused by the network devices (such as routers and switches) not properly forwarding DHCP broadcast traffic to the PXE server.
- Option 60 is set on the DHCP server when there are no PXE services on the same.
- If the PXE services are on the DHCP server, scope option 060 is not set correctly on the DHCP server.
- Some other program or service on the PXE server is using ports 67, 68, or 4011 and is preventing the PXE Server from listening on those ports (including possibly another PXE service)
- The PXE server is responding either too quickly, or too slowly for the client computer to receive and understand the response.
- The client computer is a pre-PXE 2.0 compliant system and is receiving a incompatible BSTRAP.0 file.
- The PXE service is not responding for some reason (e.g. corrupted installation, MAC Filtering enabled, etc)
- A Firewall on the PXE server or routers is blocking PXE communications, as well as other Network utilities that may block or drop PXE traffic.
- Possible corruption of the pxe.ini (DS 6.9 GSS 3.x) file or the InitialPXEConfigPath.txt file (7.x).
- If the server uses multiple network card, an incorrect binding order of the network cards can prevent PXE Server to bind to the production one.
- Newer versions of VMWare default to using NAT with an E1000e network adapter. This has shown to not work with our PXE services.