TFTP Open Timed out when PXE boot

Both workstations and DHCP  ( DHCP Is configured on Cisco Switch) are on  same Subnet >> VLAN1

and  SCCM DP/PXE is  on another subnet>>>  VLAN 2

DHCP Option 

66 and 67 configured.

Client is able to pick up IP address from DHCP, there after it's getting failed

PXE-E32:              TFTP open timeout

PXE-M0F:            Exiting Intel Boot Agent

Please  assist me to right direction, Do I need IP helper configuration  in this scenario?

August 24th, 2015 11:57am

How are 66/67 configured?
You don't need DHCP options at all if you set up IPhelpers (which would be the recommended method).
Free Windows Admin Tool Kit Click here and download it now
August 24th, 2015 12:01pm

Well iphelper and option 66 and 67 kind of serve the same purpose just different way of doing it.

In the switch if you configure IPhelper to manage DHCP only request the switch will shoot the info to the DHCP server that will give the info back to the client. The client now is looking to reach the server configure in the option 66.

Option 66: should be the IP or FQDN for the PXE point

Option 67: should be the file name:\smsboot\x64\wdsnbp.com

If the iphelper is configure to handle everything the switch you send the DHCP request to the DHCP serve and the PXE request to the PXE point.

Iphelper are a lot easier to work with in general and less issue then using DHCP to manage those option.

Now for your issue i would look at the SMSPXE.log file on the dp/pxe point to see if the request ever got to the server.


August 24th, 2015 12:05pm

Thanks for response!!

Option 66: should be the IP or FQDN for the PXE point

Option 67: should be the file name:\smsboot\x64\wdsnbp.com

Already DHCP Option was configured. Still am getting  the below error

PXE-E32:              TFTP open timeout

PXE-M0F:            Exiting Intel Boot Agent

Please tell me, How do i configure IP Helper for above my Infrastrucute Scenario


*************************************SMSPXE.log*************

Begin validation of Certificate [Thumbprint AD77860D25FD2937606590E89A530A23ED374FF4] issued to 'de5316d7-817d-4ca5-969b-62e62ac70ee6' SMSPXE 8/23/2015 3:57:34 AM 6296 (0x1898)
Completed validation of Certificate [Thumbprint AD77860D25FD2937606590E89A530A23ED374FF4] issued to 'de5316d7-817d-4ca5-969b-62e62ac70ee6' SMSPXE 8/23/2015 3:57:34 AM 6296 (0x1898)
Cannot read the registry value of MACIgnoreListFile (800703e5) SMSPXE 8/23/2015 4:06:41 AM 10348 (0x286C)
MAC Ignore List Filename in registry is empty SMSPXE 8/23/2015 4:06:41 AM 10348 (0x286C)
Cannot read the registry value of MACIgnoreListFile (800703e5) SMSPXE 8/23/2015 4:54:19 AM 10068 (0x2754)
MAC Ignore List Filename in registry is empty SMSPXE 8/23/2015 4:54:19 AM 10068 (0x2754)
Begin validation of Certificate [Thumbprint AD77860D25FD2937606590E89A530A23ED374FF4] issued to 'de5316d7-817d-4ca5-969b-62e62ac70ee6' SMSPXE 8/23/2015 4:57:34 AM 3668 (0x0E54)
Completed validation of Certificate [Thumbprint AD77860D25FD2937606590E89A530A23ED374FF4] issued to 'de5316d7-817d-4ca5-969b-62e62ac70ee6' SMSPXE 8/23/2015 4:57:34 AM 3668 (0x0E54)
Cannot read the registry value of MACIgnoreListFile (800703e5) SMSPXE 8/23/2015 5:41:58 AM 7552 (0x1D80)
MAC Ignore List Filename in registry is empty SMSPXE 8/23/2015 5:41:58 AM 7552 (0x1D80)
Begin validation of Certificate [Thumbprint AD77860D25FD2937606590E89A530A23ED374FF4] issued to 'de5316d7-817d-4ca5-969b-62e62ac70ee6' SMSPXE 8/23/2015 5:57:34 AM 5640 (0x1608)
Completed validation of Certificate [Thumbprint AD77860D25FD2937606590E89A530A23ED374FF4] issued to 'de5316d7-817d-4ca5-969b-62e62ac70ee6' SMSPXE 8/23/2015 5:57:34 AM 5640 (0x1608)
Cannot read the registry value of MACIgnoreListFile (800703e5) SMSPXE 8/23/2015 6:28:41 AM 4828 (0x12DC)
MAC Ignore List Filename in registry is empty SMSPXE 8/23/2015 6:28:41 AM 4828 (0x12DC)
Begin validation of Certificate [Thumbprint AD77860D25FD2937606590E89A530A23ED374FF4] issued to 'de5316d7-817d-4ca5-969b-62e62ac70ee6' SMSPXE 8/23/2015 6:57:35 AM 1656 (0x0678)
Completed validation of Certificate [Thumbprint AD77860D25FD2937606590E89A530A23ED374FF4] issued to 'de5316d7-817d-4ca5-969b-62e62ac70ee6' SMSPXE 8/23/2015 6:57:35 AM 1656 (0x0678)
Begin validation of Certificate [Thumbprint AD77860D25FD2937606590E89A530A23ED374FF4] issued to 'de5316d7-817d-4ca5-969b-62e62ac70ee6' SMSPXE 8/23/2015 7:57:35 AM 9236 (0x2414)
Completed validation of Certificate [Thumbprint AD77860D25FD2937606590E89A530A23ED374FF4] issued to 'de5316d7-817d-4ca5-969b-62e62ac70ee6' SMSPXE 8/23/2015 7:57:35 AM 9236 (0x2414)

******************************

Free Windows Admin Tool Kit Click here and download it now
August 24th, 2015 2:21pm

Just set up an IPhelper that points to the PXE-enabled DP. No need to do that for DHCP as it is on the same subnet as the clients.
August 24th, 2015 2:50pm

Well iphelper and option 66 and 67 kind of serve the same purpose just different way of doing it.

In the switch if you configure IPhelper to manage DHCP only request the switch will shoot the info to the DHCP server that will give the info back to the client. The client now is looking to reach the server configure in the option 66.

Option 66: should be the IP or FQDN for the PXE point

Option 67: should be the file name:\smsboot\x64\wdsnbp.com

If the iphelper is configure to handle everything the switch you send the DHCP request to the DHCP serve and the PXE request to the PXE point.

Iphelper are a lot easier to work with in general and less issue then using DHCP to manage those option.

Now for your issue i would look at the SMSPXE.log file on the dp/pxe point to see if the request ever got to the server.


Free Windows Admin Tool Kit Click here and download it now
August 24th, 2015 4:04pm

Removed DHCP both Option 66  and 67

and configured IP Helper.

we are getting  " no Boot file name received" 

If we configured both Option and IPhelper, it does work.

Please tell me  If IPhelper should be configured, what are steps for IPhelpers?

August 27th, 2015 7:02am

Are you sure the 2 boot image are distributed on the DP/PXE
Free Windows Admin Tool Kit Click here and download it now
August 27th, 2015 7:13am

Examine smspxe.log on the pxe enabled DP.
August 27th, 2015 7:35am

we  are able to achieve  PXE boot   by configuring Both DHCP Option 66/67 and  IP helpers

verified that Boot Images(x86/x64) got distributed successfully. and examined the same at SMSPXE.log. all is Good.

Here my question is  " Why I couldn't achieve  If IP Helper configuration method alone.

my setup is 

Both workstations and DHCP  ( DHCP Is configured on Cisco Switch) are on  same Subnet >> VLAN1

and  SCCM DP/PXE is  on another subnet>>>  VLAN 2

Where I am wrong?, Please correct me.

Free Windows Admin Tool Kit Click here and download it now
August 27th, 2015 9:05am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics