---
title: "iPXE boot environment troubleshooting guide"
canonical: "https://support.blancco.com/space/KB/11632933/iPXE%20boot%20environment%20troubleshooting%20guide"
format: markdown
---
<span style="color: #000000">This article is created to resolve problems encountered during iPXE boot installation/update in Windows Server 2012 Server environment. The instructions for building the Windows Server 2012 based iPXE environment can be found from </span>[<span style="color: #000000">this KB article</span>](https://support.blancco.com/pages/viewpage.action?pageId=66005)<span style="color: #000000">.</span>

<span style="color: #000000">It is important to be able to pin-point the iPXE process step where an issue occurs. Use the following list of iPXE boot loading steps to locate the exact step:</span>

1. <span style="color: #000000">PXE boot agent loads on client side</span>
2. <span style="color: #000000">PXE client checks network link</span>
3. <span style="color: #000000">PXE client reaches out to DHCP</span>
4. <span style="color: #000000">Server DHCP responds | Possible error: PXE-E51</span>
5. <span style="color: #000000">DHCP scope option 60 (PXEClient) is loaded | Possible error: PXE-53</span>
6. <span style="color: #000000">Client machine gets IP address</span>
7. <span style="color: #000000">Client machine reaches out to next-server / TFTP server address</span>
8. <span style="color: #000000">TFTP boot program is loaded (wdsnbp.com in WDS)</span>
9. <span style="color: #000000">TFTP boot program (wdsnbp.com) responds to client machine</span>
10. <span style="color: #000000">TFTP boot program detects client architecture (e.g. x64)</span>
11. <span style="color: #000000">TFTP boot program (wdsnbp.com) hands out undionly.kpxe (or the configured PXE client program in the WDS settings)</span>
12. <span style="color: #000000">Undionly.kpxe loads on the client machine</span>
13. <span style="color: #000000">Undionly.kpxe / client checks DHCP scope option 66 (Boot server host name) and tries to load '\Boot\x86\boot.ipxe'</span>
14. <span style="color: #000000">Undionly.kpxe / client checks DHCP scope option 67 (Bootfile name)</span>
15. <span style="color: #000000">Undionly.kpxe / client loads '\Boot\x86\boot.ipxe' (as configured in opt 67)</span>
16. <span style="color: #000000">Boot.ipxe loads menu.ipxe file from the HTTP server (IIS) Virtual directory (at http://${server}/Images/menu.ipxe)</span>
17. <span style="color: #000000">HTTP server / IIS looks for the .ipxe MIME type and delivers the menu.ipxe to the client</span>
18. <span style="color: #000000">Blancco PXE boot menu is displayed on the client screen</span>
19. <span style="color: #000000">Boot menu option is selected from the boot menu</span>
20. <span style="color: #000000">Boot menu / Client tries to load the selected ISO image from the HTTP server at e.g: '</span><span style="color: #000000">http://10.10.1.1/Images/Blancco_5.iso</span><span style="color: #000000">'</span>
21. <span style="color: #000000">HTTP server/ IIS recognizes the .iso MIME type and delivers the Image</span>
22. <span style="color: #000000">Boot menu / Client tries to chain load the memdisk.bin file from the Images-directory at e.g: 'memdisk.bin'</span>
23. <span style="color: #000000">HTTP server/IIS delivers the memdisk file and the ISO image downloading starts</span>
24. <span style="color: #000000">Blancco.ISO image loads on the client and Blancco starts booting</span>

<span style="color: #000000">When you have a clear vision at which point the error message appears, use the following list of the most common error messages, causes and fixes, to resolve what's the most obvious fix for the problem. You may also contact our Technical Support team regarding the issue by submitting a Support ticket at:</span>[<span style="color: #ff0000">https://support.blancco.com</span>](https://support.blancco.com/)<span style="color: #000000"> </span>

<span style="color: #000000">Note! Remember to add picture of the error message from the client computer!</span>

  
<span style="color: #000000">**ERROR: **</span>  
<span style="color: #000000">PXE-E51: No DHCP or proxyDHCP offers were received</span>  
<span style="color: #000000">CAUSE/FIX: Client computer can't find a DHCP server</span>  
<span style="color: #000000">a) Check that the network cable is connected and that network connection exists between the client computer and the DHCP server.</span>  
<span style="color: #000000">b) Check that the DHCP service is running on the server.</span>  
<span style="color: #000000">c) Check that DHCP server is authorized in Active directory (if AD is used).</span>  
<span style="color: #000000">d) Check that the DHCP scope is active and running in the same network (same IP range) as the server (check the IP address).</span>  
<span style="color: #000000">e) Check that the server network card, that hosts the DHCP service, is active and connected to the client network.</span>  
<span style="color: #000000">f) Check that the DHCP scope is configured properly, including the IP range, DNS, Router and boot server host name.</span>  
<span style="color: #000000">g) Check that there are no other conflicts or issues between the scope and the server network card.</span>  
<span style="color: #000000">h) Check the server/Windows firewall settings and make sure UDP port for TFTP/PXE boot (i.e. ports 67 or 69) is allowed for PXE booting. Try disabling the firewall for troubleshooting purposes.</span>  
<span style="color: #000000">i) Check the server network card settings, including IP, subnet mask, gateway and DNS settings.</span>  
<span style="color: #000000">j) Reset server network card/IP settings and recreate the DHCP scope if nothing else works.</span>  
  
<span style="color: #000000">**ERROR:**</span>  
<span style="color: #000000">PXE-E53: No boot filename received</span>  
<span style="color: #000000">CAUSE/FIX: Server/scope option 60 (PXEClient) is missing in the DHCP settings or WDS -> DHCP -> "Configure DHCP options to indicate that this is also a PXE server" check box is not checked.</span>  
  
<span style="color: #000000">**ERROR:**</span>  
<span style="color: #000000">CLIENT IP: 10.10.1.2 MASK: 255.255.255.0 DHCP IP: 10.10.1.2</span>  
<span style="color: #000000">TFTP.</span>  
<span style="color: #000000">PXE-M0F: Exiting Boot Agent.</span>  
<span style="color: #000000">CAUSE/FIX: The Client/TFTP server can't find the default TFTP boot program (wdsnbp.com in WDS). Check that wdsnbp.com exists in \RemoteInstall\Boot\x86\ folder and that WDS is properly configured.</span>  
  
<span style="color: #000000">**ERROR:**</span>  
<span style="color: #000000">Downloaded WDSNBP from 10.10.1.1 WIN-123.test.local</span>  
<span style="color: #000000">TFTP download failed.</span>  
<span style="color: #000000">PXE-M0F: Exiting Intel Boot Agent.</span>  
<span style="color: #000000">CAUSE/FIX: Check the WDS Server -> Boot -> PXE boot policy properties. Make sure "Always continue PXE boot" is selected.</span>  
  
<span style="color: #000000">**ERROR:**</span>  
<span style="color: #000000">Filename: \Boot\x86\boot.ipxe</span>  
<span style="color: #000000">/\Boot\x86\boot.ipxe... Error 0x3d126001 (</span><span style="color: #000000">http://ipxe.org/3d126001</span><span style="color: #000000">)</span>  
<span style="color: #000000">No more network devices</span>  
<span style="color: #000000">CAUSE/FIX: Scope option 66 missing or is not correctly defined in the DHCP scope(s)</span>  
  
<span style="color: #000000">**ERROR:**</span>  
<span style="color: #000000">WDSNBP started using DHCP Referral.</span>  
<span style="color: #000000">Contacting Server: 10.10.1.1 (Gateway: 0.0.0.0).</span>  
<span style="color: #000000">Architecture: x64</span>  
<span style="color: #000000">Contacting Server: 10.10.1.1.</span>  
<span style="color: #000000">TFTP Download: Boot\x86\undionly.kpxe</span>  
<span style="color: #000000">CAUSE/FIX: </span>  
<span style="color: #000000">a) Scope option 67 (\Boot\x86\boot.ipxe) is missing in the iPXE Policy/Vendor class DHCP options.</span>  
<span style="color: #000000">a) undionly.kpxe file can't be found in the \Boot\x86\ -folder</span>  
<span style="color: #000000">c) Wdsutil bootprogram/N12bootprogram for x64 architecture is not set correctly.</span>  
  
<span style="color: #000000">**ERROR:**</span>  
<span style="color: #000000">http://10.10.1.1/Images/menu.ipxe</span><span style="color: #000000">... No such file or directory (</span><span style="color: #000000">http://ipxe.org/2d0c613b</span><span style="color: #000000">)</span>  
<span style="color: #000000">CAUSE/FIX: Path for the menu.ipxe file in boot.ipxe file is not set correctly.</span>  
<span style="color: #000000">a) Check that the menu.ipxe path is correct, e.g.: (http://${server}/Images/menu.ipxe).</span>  
<span style="color: #000000">b) /Images directory is not properly defined in the HTTP server as virtual directory (IIS: under the default website). Make sure that the /Images folder is added to the HTTP server (IIS: under default website).</span>  
<span style="color: #000000">c) MIME type for .ipxe missing in IIS under the /images virtual directory. Add .ipxe in IIS MIME types under the /Images virtual directory.</span>  
  
<span style="color: #000000">**ERROR:**</span>  
<span style="color: #000000">http://10.10.1.1/Images/menu.ipxe</span><span style="color: #000000">... input/output error (</span><span style="color: #000000">http://ipxe.org/1d0c6139</span><span style="color: #000000">)</span>  
<span style="color: #000000">CAUSE: HTTP Server (IIS) has a problem accessing the .ipxe file or files in general in the /Images folder.</span>  
<span style="color: #000000">FIX: Check the IIS virtual directory and the MIME type settings.</span>  
<span style="color: #000000">a) In IIS, click the MIME types under Default Website/images directory. If you get an error about the MIME types, try deleting the conflicting (.ipxe and .ipxe) MIME types under the server/default website MIME types. Double-click the MIME types again under the /images virtual directory to check that you don't get an error.</span>  
<span style="color: #000000">b) Another way to test if the problem is related to the virtual directory or the MIME types, is to try browsing the virtual directory from IIS by right-clicking the virtual directory -> Manage Virtual Directory -> Browse. Note that the virtual directory browsing must be enabled first in the IIS settings. If you get a MIME type related error, try removing the conflicting MIME types from the higher levels. </span>  
  
<span style="color: #000000">**ERROR:**</span>  
<span style="color: #000000">http://10.10.1.2/Images/menu.ipxe</span><span style="color: #000000">...... Connection timed out (</span><span style="color: #000000">http://ipxe.org/4d0c6135</span><span style="color: #000000">)</span>  
<span style="color: #000000">CAUSE/FIX: Server address in the boot.ipxe file is not set correctly</span>  
<span style="color: #000000">a) Check and fix the server address in the boot.ipxe file</span>  
  
<span style="color: #000000">**ERROR:**</span>  
<span style="color: #000000">(after loading image from the boot menu):</span>  
<span style="color: #000000">http://10.10.1.1/Images/Blancco_5.iso</span><span style="color: #000000">... ok</span>  
<span style="color: #000000">Could not boot image: No such file or directory (</span><span style="color: #000000">http://ipxe.org/2d0c613b</span><span style="color: #000000">)</span>  
<span style="color: #000000">No more network devices</span>  
<span style="color: #000000">Press Ctrl-B for the iPXE command line...</span>  
<span style="color: #000000">(Reboots)</span>  
<span style="color: #000000">CAUSE/FIX: .iso MIME type missing in IIS</span>  
  
<span style="color: #000000">**ERROR:**</span>  
<span style="color: #000000">(after loading image from the boot menu):</span>  
<span style="color: #000000">http://10.10.1.1/Images/Blancco_5.iso</span><span style="color: #000000">... ok</span>  
<span style="color: #000000">/memdisk.. No such file or directory (</span><span style="color: #000000">http://ipxe.org/2d0c613b</span><span style="color: #000000">)</span>  
<span style="color: #000000">Booting failed, dropping to shell</span>  
<span style="color: #000000">Type 'exit' to get back to the menu</span>  
<span style="color: #000000">iPXE></span>  
<span style="color: #000000">CAUSE/FIX: Boot menu can't find/load the memdisk file. Check the memdisk path/filename/extension in the menu.ipxe and in the /Images folder and rename if necessary. </span><span style="color: #000000">For example if memdisk.bin file exists in /Images -folder, try changing the line for the memdisk in the menu.ipxe file as: </span>  
<span style="color: #000000">chain memdisk.bin iso raw || goto failed</span>