Common errors that are seen at the PXE boot screen when the PXE Service Point is either not configured properly or experiencing problems are the following: PXE-E53: No boot filename received PXE-T01: File not found PXE-E3B: TFTP Error – File not Found PXE-E55 Proxy DHCP Service did not reply to request on port 4011 PXE-T04: Access Violation PXE-E36: Error Received from TFTP Server PXE-M-F Exiting PXE Rom However the error messages can vary depending on the PXE implementation on the client PC. Otherwise, if either the DHCP server, the client PC or the Config Mgr 2007 server is running WDS and the PXE Service Point are on separate subnets or vlans, which is usually the case in most environments, the first step to take before trying to install and configure the PXE Service Point and WDS is to set up IP Helpers on the routers.
In the properties of the boot image, under Data Source, make sure the check box labeled If machines can’t boot via PXE, open up the SMSPXE.
LOG file in the tool on the SCCM PXE, and look for problems.
There is an updated version of this guide over at the Configuration Manager OSD Support Team Blog.
For the latest version, please visit the below article: Troubleshooting the PXE Service Point and WDS in Configuration Manager 2007 ===== This is a general guide on properly setting up and troubleshooting the System Center Configuration Manager 2007 (Config Mgr 2007) PXE Service Point.
This is because modern net card boot agent takes charge during the boot process if it is set to do so on the net card PROM.