WDS PXE-E53 No Boot Filename Received

Question

WDS PXE-E53 No Boot Filename Received

Connor Owens 6

Hello,

Having some issues with WDS. I can not get any clients to boot to WDS, as they receive a "PXE-E53 No Boot Filename Received" error. For background, DHCP and WDS are on the same machine, option 60 is PXEClient, option 66 points to the IP of the WDS server, and option 67 is set to "\boot\x64\wdsnbp.com" I can not get this figured out for some reason. Any help is appreciated.

Connor

1 answer

Your answer

Answer 1

Teemo Tang 11,471

Hi Connor,
The "PXE-E53" error indicates that the PXE client received a reply to its DHCPDISCOVER message, but the "boot filename" information was missing in this reply. Make sure that the "boot filename" option is present on your DHCP server, and that its value is set to the filename of the boot loader.
When using DHCP Options for PXE Boot, Option 66 must be the IP-address of your WDS server, Option 67 must be pointing to "SMSBoot\x86\wdsnbp.com". When using IP-helpers you need to enter the IP-address of your WDS server only.
Option 67 for the name is like this
For legacy bios x86 SMSBoot\x86\wdsnbp.com
For legacy bios x64 SMSBoot\x64\wdsnbp.com
For UEFI x86 SMSBoot\x86\wdsmgfw.efi
For UEFI x64 SMSBoot\x64\wdsmgfw.efi
The option 60 is by default the value should be: PXEClient
Option 66 is the FQDN of the pxe server.
If you plan on booting UEFI you will only be able to boot UEFI with this option. And with the legacy bios you can use For legacy bios x86 SMSBoot\x86\wdsnbp.com to boot both X64 and X86
But please look into using Ip-helper and not forcing those option they are wonky at best and Microsoft strongly suggest using Ip-helper as well.
A similar case
https://www.dell.com/community/Laptops-General-Read-Only/PXE-E53-No-boot-filename-received-after-Dell-update/m-p/5048450#M899836
Please note: Information posted in the given link is hosted by a third party. Microsoft does not guarantee the accuracy and effectiveness of information.

-------------------------------------------------------------------------------------

If the Answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Connor Owens 6 Reputation points

2020-11-23T15:52:12.32+00:00

Hello,

This is for MDT through WDS, will that make a difference in the bootfile name. I am currently using Boot\x64\wdsnbp.com as the bootfile name for option 67. In DHCP, everything is how it should be, with the options set as described in your answer. I don't believe I have any IP Helpers. I am not using UEFI, as this will only be for desktop computers using LAN PXE to boot. Option 60 is set to PXEClient. I tried all your options just to see if that would work, but had no luck. Any other suggestions?

Connor
Teemo Tang 11,471 Reputation points

2020-11-24T03:06:08.773+00:00

Check this case for more ideas
https://serverfault.com/questions/541029/wds-clients-receive-error-pxe-e53-no-boot-filename-received/963476
Connor Owens 6 Reputation points

2020-11-24T03:29:39.167+00:00

No idea what is going on! I have tried everything in this article. I have uninstalled the WDS role, un-initialized the service and completely setup again, deleted and reinstalled all my Boot WIMs, with no luck. I'm starting to think this is maybe more of a DHCP issue, but I have checked everything in DHCP. Not sure where to go next. I appreciate your paitence

Connor
Teemo Tang 11,471 Reputation points

2020-11-25T08:00:29.71+00:00

Well, I believe you have done all the things...
What i can come up with is separating your DHCP server and WDS server, WDS and DHCP server on the same subnet but different servers, the clients will find the WDS by broadcast.
echo_LOGNAME 1 Reputation point

2022-09-22T19:32:51.603+00:00

Hi! I'm a student and I started a similar project this week on Windows Server 2019, and I'm a little confused, how do I know what the boot filename is? I extracted the boot.wim and install.wim from an ISO when setting up my WDS server which is the same machine as my DHCP server, would it be somewhere in the ISO or the name of the ISO itself? Thanks! :)
Mohd Abdul rahman Talha 1 Reputation point

2022-12-23T23:03:41.11+00:00

Had Exactly the same issue and i resolved by going to wds, going to properties than in DHCP tab enabling both checkboxes (if wds and dhcp both are on same machine).

Share via

WDS PXE-E53 No Boot Filename Received

1 answer

Your answer