Article ID: 2024414 - Last Review: November 22, 2010 - Revision: 4.0

PXE booting with System Center Configuration Manager 2007 fails with "PXE-T04: Access Violation" and "PXE-E36: Error Received from TFTP Server"

View products that this article applies to.

System TipThis article applies to a different operating system than the one you are using. Article content that may not be relevant to you is disabled.

Expand all | Collapse all

Symptoms

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.

Back to the top

Cause

This can occur do to an issue with DHCP.

Back to the top

Resolution

You may need to configure IP Helper (BOOTP) settings on the router or configure the DHCP Scope Options as appropriate. This can also occur if the settings are configured improperly.

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:

\\smsboot\\x86\\name.com

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.

Back to the top

Note This is a "FAST PUBLISH" article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use (http://go.microsoft.com/fwlink/?LinkId=151500) for other considerations.

Back to the top