Date: Thu, 28 Mar 2024 18:39:20 +0000 (UTC) Message-ID: <390368863.8336.1711651160871@support.blancco.com> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_8335_1376667448.1711651160871" ------=_Part_8335_1376667448.1711651160871 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
This article is created to re= solve problems encountered during iPXE boot installation/update in Windows = Server 2012 Server environment. The instructions for building the Windows S= erver 2012 based iPXE environment can be found from this= KB article.
It is important to be able to pi= n-point the iPXE process step where an issue occurs. Use the following= list of iPXE boot loading steps to locate the exact step:=
When you have a clear vision at = which point the error message appears, use the following list of the m= ost common error messages, causes and fixes, to resolve what's the most obv= ious fix for the problem. You may also contact our Technical Support t= eam regarding the issue by submitting a Support ticket at:https://support.blancco.com
Note! Remember to add picture of the =
error message from the client computer!
If you find any difficulties in "navi=
gating" to the correct place in Windows Server environment please download =
the ZIP package below which contains example pictures:
https://download.blancco.com/general/manuals/=
pxe/ipxe_troubleshooting_pictures.zip
ERROR:
=
strong>PXE-E51: No DHCP or proxyDHCP off=
ers were received
CAUSE/FIX: C=
lient computer can't find a DHCP server
a) Check that the network cable is connected and that networ=
k connection exists between the client computer and the DHCP server.=
b) Check that the DHCP service is ru=
nning on the server.
c) Check =
that DHCP server is authorized in Active directory (if AD is used).<=
br>d) Check that the DHCP scope is activ=
e and running in the same network (same IP range) as the server (check the =
IP address).
e) Check that the=
server network card, that hosts the DHCP service, is active and connected =
to the client network.
f) Chec=
k that the DHCP scope is configured properly, including the IP range, DNS, =
Router and boot server host name.
g) Check that there are no other conflicts or issues between the scope =
and the server network card.
h=
) Check the server/Windows firewall settings and make sure UDP port for TFT=
P/PXE boot (i.e. ports 67 or 69) is allowed for PXE booting. Try disabling =
the firewall for troubleshooting purposes.
i) Check the server network card settings, including IP, subne=
t mask, gateway and DNS settings.
j) Reset server network card/IP settings and recreate the DHCP scope if=
nothing else works.
ERROR:
PXE-E53: No=
boot filename received
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.
ERROR:
CLIENT IP: 10.10.1.2 MASK: 255.255.255.0 DHCP IP: 10.10.1.2
TFTP.
PXE-M0F: Exiting Boot Agent.
CAUSE/FIX: The Client/TFTP server can't find the default TFT=
P boot program (wdsnbp.com in WDS). Check that wdsnbp.com exists in \Remote=
Install\Boot\x86\ folder and that WDS is properly configured.
ERROR:
Downloaded WDSNBP from 10.10.1.1 WIN-123.test=
.local
TFTP download failed.=
span>
PXE-M0F: Exiting Intel Boot Age=
nt.
CAUSE/FIX: Check the WDS S=
erver -> Boot -> PXE boot policy properties. Make sure "Always contin=
ue PXE boot" is selected.
ERROR:
Filena=
me: \Boot\x86\boot.ipxe
/\Boot=
\x86\boot.ipxe... Error 0x3d126001 (http://ipxe.org/3d126001=
)
No more network devices
CAUSE/FIX: Scope option 66 missing=
or is not correctly defined in the DHCP scope(s)
WDSNBP started using DHCP Referral.
Contacting Server: 10.10.1.1 (Gateway: 0.0.0.0).
Architecture: x64
CAUSE/FIX:
a) Scope option 67 (\Boot\x86\boot.ipxe) is&=
nbsp;missing in the iPXE Policy/Vendor class DHCP options.
a) undionly.kpxe file can't be found in the \B=
oot\x86\ -folder
c) Wdsutil bo=
otprogram/N12bootprogram for x64 architecture is not set correctly.<=
br>
ERROR:
http://10.10.1.1/Images/menu.ipxe
CAUSE/FIX: Path for the=
menu.ipxe file in boot.ipxe file is not set correctly.
a) Check that the menu.ipxe path is correct, e.g.=
: (http://${server}/Images/menu.ipxe).
b) /Images directory is not properly defined in the HTTP server as=
virtual directory (IIS: under the default website). Make sure that the /Im=
ages folder is added to the HTTP server (IIS: under default website).
c) MIME type for .ipxe missing in I=
IS under the /images virtual directory. Add .ipxe in IIS MIME types under t=
he /Images virtual directory.
ERROR:http://1=
0.10.1.1/Images/menu.ipxe... input/output error (http://ipxe=
.org/1d0c6139)
CAUSE: HTTP Server (IIS) has a problem accessing the .ipxe file or fi=
les in general in the /Images folder.
FIX: Check the IIS virtual directory and the MIME type settings.
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.<=
br>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 br=
owsing must be enabled first in the IIS settings. If you get a MIME type re=
lated error, try removing the conflicting MIME types from the higher levels=
.
ERROR:
<=
span class=3D"nolink">http://10.10.1.2/Images/menu.i=
pxe...... Connection timed out (http://ipxe.org/4d0c6135)
CAUSE/FIX: =
Server address in the boot.ipxe file is not set correctly
a) Check and fix the server address in the boot=
.ipxe file
ERROR:<=
/span>
(after loading image =
from the boot menu):
http://10.10.1.=
1/Images/Blancco_5.iso... ok
Could not boot image: No such file or directory (http://ipxe.=
org/2d0c613b)
No more network devices
P=
ress Ctrl-B for the iPXE command line...
(Reboots)
CAUSE/FIX=
: .iso MIME type missing in IIS
ERROR:
=
(after loading image from the boot menu):
http://10.10.1.1/Images/Blancco_5.iso... ok
/memdisk.. No such file or directo=
ry (ht=
tp://ipxe.org/2d0c613b)
Booting failed, dropping to shell
Type 'exit' to get back to the menu
iPXE>
CAUSE/FIX: Boot menu can't find/load the memdisk file. Check the memdis=
k path/filename/extension in the menu.ipxe and in the /Images folder and re=
name if necessary. For examp=
le if memdisk.bin file exists in /Images -folder, try changing the line for=
the memdisk in the menu.ipxe file as:
chain memdisk.bin iso raw || goto failed