TFTP Times out on PXE boot

[amarc611]

I started to get a TFTP time out error imaging PCs here is the log from the server below. Could someone give me some pointers on what to look for?

 

I have removed the PXE from Dist point and rebooted and reinstalled PXE on the dist point.

I have checked and recreated a new boot image and check the box to distrubute the boot image.

and nothing.

 

I checked my DHCP for option settings are all correct.

 

066 Boot Server Host Name Standard

067 Bootfile Name Standard SMSBoot\x86\wdsnbp.com

SMSPXE.log

 

Start:

 

Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="16778090" ServerName="" ServerRemoteName=""><Machine><ClientID>GUID:869c7a8b-de66-48e9-8c92-a1fb7b6349be</ClientID><NetbiosName/></Machine></Identification><PXEBootAction LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="XLA20033" OfferIDTime="11/20/2013 3:38:00 PM" PkgID="XLA00036" PackageVersion="" PackagePath="http://HX-SCCM01.XXXX.com/SMS_DP_SMSPKG$/FLA0007D" BootImageID="XLA0007D" Mandatory="0"/></ClientIDReply>
SMSPXE 12/11/2013 8:52:21 AM 3060 (0x0BF4)

B8:AC:6F:71:86:5B, 4C4C4544-0035-5910-8046-C2C04F524E31: found optional advertisement XLA20033 SMSPXE 12/11/2013 8:52:21 AM 3060 (0x0BF4)

 

End of log.

 

 

Then the system gets a TFTP PXE-E32 timeout

[Kazi]

If you are using Cisco routers, try adding an IP Helper, otherwise make sure your Boot Server Host Name is an IP address and not a server name.

[amarc611]

I do have the server IP address instead of the host name.

[Kazi]

Try including your Router, DNS Domain Name, Boot Server Host Name (but list the IP and not the name), Bootfile Name, and DNS Servers in your options.

[amarc611]

Well I figured it out it was a breakdown of the my management Point because of a KB update. I had everything configured correctly but PXE just wouldn't work.

I found this article which solved it. http://configmgrblog.com/2012/12/18/how-to-repair-mdt-2012-integration-with-configmgr-2012-and-mp-after-kb2506143/

 

Below are some of the steps I took to fix

1. Removed update KB2506143 from the Software Update deployment
2. Uninstalled update KB2506143 on the Configuration Manager 2012 server
3. Changed the CcmEval=TRUE registry key workaround described in KB2796086
4. Rebooted the Configuration Manager 2012 server
5. Removed the MDT 2012 integration with Configuration Manager 2012
6. Removed the Management Point from the Configuration Manager 2012 server
7. Rebooted the Configuration Manager 2012 server
8. Installed the Management Point on the Configuration Manager 2012 server
9. Rebooted the server
10. Configured the MDT 2012 integration with Configuration Manager 2012 again

ALL is working now.

Thank you all for your suggestions and help.

[Kazi]

Great find! Glad you have it working.

[amarc611]

Well, after 5 days of it working it broke again yesterday. No updates installed nothing I have not touched the system. I'm puling my hair out how can I find out whats causing the break down.

[amarc611]

Here is the latest from SMSPXE.log

 

Using CMtrace below is RED.

 

Initializing PXEPerfObject. SMSPXE 12/19/2013 10:59:37 AM 2364 (0x093C)
Could not load logging configuration for component ccmperf. Using default values. SMSPXE 12/19/2013 10:59:37 AM 2364 (0x093C)
Client is set to use HTTPS when available. The current state is 224. SMSPXE 12/19/2013 10:59:37 AM 2364 (0x093C)
RequestMPKeyInformation: Send() failed. SMSPXE 12/19/2013 10:59:37 AM 2364 (0x093C)
Failed to get information for MP: http://HQ-SCCM01.XXX.com. 80004005. SMSPXE 12/19/2013 10:59:37 AM 2364 (0x093C)
PXE::MP_InitializeTransport failed; 0x80004005 SMSPXE 12/19/2013 10:59:37 AM 2364 (0x093C)
PXE::MP_LookupDevice failed; 0x80004005 SMSPXE 12/19/2013 10:59:37 AM 2364 (0x093C)
PXE Provider failed to initialize MP connection.
Unspecified error (Error: 80004005; Source: Windows) SMSPXE 12/19/2013 10:59:37 AM 2364 (0x093C)
RequestMPKeyInformation: Send() failed. SMSPXE 12/19/2013 10:59:37 AM 2364 (0x093C)
Failed to get information for MP: http://HQ-SCCM01.XXX.com. 80004005. SMSPXE 12/19/2013 10:59:37 AM 2364 (0x093C)
PXE::MP_InitializeTransport failed; 0x80004005 SMSPXE 12/19/2013 10:59:37 AM 2364 (0x093C)
PXE::MP_ReportStatus failed; 0x80004005 SMSPXE 12/19/2013 10:59:37 AM 2364 (0x093C)
PXE::CPolicyProvider::InitializeMPConnection failed; 0x80004005 SMSPXE 12/19/2013 10:59:37 AM 2364 (0x093C)
PXE::CBootImageInfo::CBootImageInfo: key= SMSPXE 12/19/2013 10:59:37 AM 2364 (0x093C)
PXE::CBootImageInfo::CBootImageInfo: key= SMSPXE 12/19/2013 10:59:37 AM 2364 (0x093C)
Begin validation of Certificate [Thumbprint 7D39125C5AFB752CA2C9EC47563A4EE5D4CCB604] issued to '2d04c5b8-1f6c-43d6-aeee-227b139e8592' SMSPXE 12/19/2013 10:59:39 AM 2364 (0x093C)
Completed validation of Certificate [Thumbprint 7D39125C5AFB752CA2C9EC47563A4EE5D4CCB604] issued to '2d04c5b8-1f6c-43d6-aeee-227b139e8592' SMSPXE 12/19/2013 10:59:39 AM 2364 (0x093C)
PXE Provider finished loading. SMSPXE 12/19/2013 10:59:39 AM 2364 (0x093C)

[amarc611]

I found out the Site System Installation Account defined was a network account that didn't not have permissions to the Distribution point.

 

I found in the Distmgr.log this error

 

Failed to set share security on share \\HQ-SCCM01.XXX.com\SMSSIG$. Error = 5 SMS_DISTRIBUTION_MANAGER 12/19/2013 12:20:03 PM 5508 (0x1584)

 

If you change the option of "Use another account for installing this site system" to "Use the site server's computer account to install this site system", then the error should be corrected.