Link to home
Start Free TrialLog in
Avatar of Asif Naeem
Asif NaeemFlag for United Kingdom of Great Britain and Northern Ireland

asked on

Error53: No Boot File name received ( PXE)

Dear Experts,

I have recently Build new WDS server 2008 R2 and install WDS role on it along with config part. WDS server is on  my remote site and it is VM machine. I have build the reference computer with windows 7 64 bit along with all required software.
WDS server and Refrence computer are no same domain.
After the sysprep when I run the F12 PXE boot is returning me following error ( error 53: NO Boot filename Received ) . I  have done research on it but still cannot find solution for this.

Please advice how to fix this issue to capture the image and deploy on target machine.

Avatar of Kimputer

Always test ON SITE first. Only if it works, can you continue testing with a remote site.

For now, I suspect you didn't configure your router properly. If you have A VERY SIMPLE router, it's no use to start testing further.

Router requirements:
You need IP-Helpers in your routers. For multicast your router need to support IGMP Multicast rouring.

If you didn't get it to work locally, it's no use continuing with this until that's resolved.
Avatar of Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)
Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)
Flag of United Kingdom of Great Britain and Northern Ireland image

Link to home
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of Asif Naeem



Router is not simple bcz  job in my case.  the problem is Server is hosted and have IP for example. but on my site  reference computer has IP range I an ping both side with name and IP trust relation is between both site valid. same domain.

is it there any way round  to over come this.


Will come back with result after cofig DHCP 66  & 67  

If you have a proper PXE service, you must NOT set dhcp opt 66 and 67.
WDS embeds a real PXE server so if this one is working, no DHCP option 66 and 67 should be set.
If you set these options, you can't, for instance, have a 32bit NBP (Network Boot Program) for certain nodes and a 64bits NBP for some other nodes, since the boot file name is fixed and can't be changed.

Check my article (and its comments), to have more details about DHCP options (60, 66 and 67) and their interactions with PXE nodes and services:

Don't forget that if your DHCP/PXE Servers are on another subnet than the nodes to serve, there must be DHCP relays (aka DHCP forwarders or ip-helpers) for DHCP and potentially for DHCP-Proxy (on UDP port 4011) in the case the DHCP and PXE Servers run on the same host.
Fixed after configuring the option 66 and 67 in dhc server
Check my article, it explains how DHCP options 66 and 67 are used in relation with PXE clients.
One MAY want to set these options, but this has side effects :
A PXE Server is then not required. But not having a PXE Server makes it impossible to serve different boot programs to different nodes/different architectures. If the OP has only one kind of architecture or wants only one boot program, using dhcp options 66 and 67 is OK. Now it is better to know what it does than to accept a "magic" solution...

No doubt Andrew Hancock advice me  to check or config option 66 and 67 in server  which was not worked for remote server but when i config both on local DHCP it works prefect.
I chose two expert solution because vivigatt post and article  was very comprehensive and in detail to explain the problem.
that is the reason I chose both of them for solution hope this will help to close the call
Thanks  for Help