When a client computer is trying to boot to PXE, it receives the following error message:
PXE-E53: No boot filename received
As well probably being an issue somewhat related to the computer which requested a PXE boot menu and did not receive sufficient instructions on how to get one, I'm wondering if that
can also be a link problem.
In a nutshell a faulty or wrong connection between the client and the pxe server, can that generate that type of error?
If client and pxe server couldnt' communicate, the result wouldn't be error PXE-E53..right?
Any help will be highly appreciated.
Best Answer
In a PXE environment the PXE client minimally must receive:
This info is sometimes provided by a single DHCP server (which is PXE enabled) or by a regular DHCP server (non PXE enabled) providing only IPs and a complementary proxyDHCP server only providing the rest of the PXE related parameters.
In your case it looks like (despite which method you are using) the Boot filename info is missing from the DHCP/proxyDHCP offer.
You can easily check this by running a Wireshark capture at your DHCP/proxyDHCP server and see if the DHCPOFFER contains the Boot filename info or not.
Your case looks like a typical DHCP/proxyDHCP miss-configuration
From PXE error codes