Quantcast
Channel: Ivanti User Community : All Content - OS Deployment and Provisioning
Viewing all articles
Browse latest Browse all 1803

Error: PXE-E53: No boot filename received

$
0
0

Issue

When attempting to PXE boot, the following error appears:

PXE-E53.jpg

  • PXE Boot fails.
  • No F8 option is recieved by clients.
  • Unable to PXE Boot machines.
  • Unable to network boot machines.

Cause

  • No PXE representatives are deployed.
  • Deployed PXE Representative is turned off.
  • PXE representative is not in the same broadcast domain as target machine.
  • Firewall on PXE representative is blocking requests from target machine.
  • PXE services are not running.
  • Windows Deployment Services (WDS) are installed on the PXE representative.
  • Another service on the server is using port 67

Resolution

  • Update BIOS on device
  • Ensure that a PXE representative is on and is deployed in the same broadcast domain as the target machine.
  • Ensure that no firewall is blocking requested packets from PXE booted machines.
  • Ensure PXE services are running.  The two services are "LANDESK® PXE Service" and "LANDESK® PXE MTFTP Service".
    If they are running, restart the services.
  • Redeploy the PXE Representative.
  • If PXE services repeatedly stop on PXE representatives, download and install the latest service pack on the core, then remove and redeploy PXE representatives.
  • Disable the Windows Deployment Services (WDS) on the PXE representative.
  • Run the "netstat -abn" command to find the service which is using port 67 and disable/reconfigure this service.

 

Note: The PXE Representative may need to be rebooted if the services are running, the firewall is off, but it still does not respond.

 

More information on PXE boot errors: PXE Boot errors and descriptions.


How to troubleshoot PXE boot:
Troubleshooting PXE boot (OSD)


Viewing all articles
Browse latest Browse all 1803

Trending Articles