When using System Center Configuration Manager 2007 to PXE Boot bare metal clients across subnets, the process may fail with the following errors:
PXE-T04: Access Violation
PXE-E36: Error Received from TFTP Server
PXE-M-F Exiting PXE Rom
This can occur when trying to PXE Boot from a Virtual Machine or Physical Machine. You may also notice a lack of entries in the SMSPXE.log on the PXE Service Point Server from the clients you are PXE booting, indicating that the client never contacts the PXE Service Point.
Symptoms
This can occur due to a configuration issue with DHCP in Linux.
For example, looking at a network capture you might notice that the PXE Boot File path being passed to the client from the DHCP Offer packet is something like \smsboot\x86\name.com which indicates that the PXE Boot File Path is not getting passed correctly from the DHCP Scope Options on the DHCP server.
This can occur with some Linux DHCP server appliances unless the path is specified as such:
Some DHCP servers require double backslashes for the Boot File Name Scope Option so if you configure it using standard UNC naming conventions (e.g. \\smsboot\x86\name.com) it can fail in this manner.
HOWEVER, DHCP Options are NOT a supported option by Microsoft for use with ConfigMgr 2007. Instead, IP helpers should be set up in the routers.
Cause
Remove the DHCP Options for PXE on the DHCP server (usually Options 60, 66, and 67) and configure IP helpers in the router instead. For more information please see the following article:
ConfigMgr 2007: Troubleshooting the PXE Service Point and WDS
http://bemis/15/Pages/2472266_en-US.aspx
Troubleshooting the PXE Service Point and WDS in Configuration Manager 2007
