PXE-E32 TFTP open timeout

Article
2017-06-16

Question

_{Friday, June 16, 2017 7:52 PM}

Last resort coming here for some help. I set up a new SCCM 2012 server and was imaging machines last weed without issues.

All of a sudden all PXE boots started failing with the above error. Here is some additional information...

- client is grabbing an IP and is on the same subnet as the SCCM server

- Option 66&67 configured in DHCP scope as IP of SCCM server & smsboot\x86\wdsnbp.com

- running netstat -an I can see that the SCCM server is NOT listening on UDP port 69. Any attempt to telnet to that port is rejected by the system.

- I've tried uninstalling the distribution point role and reinstall with no luck

It appears I'm timing out with UDP 69 not open but I'm at a loss as to what happened or how to get this server to listen on this port? Windows firewall is NOT on.

Thank you in advance for any help you can offer. Again this was working repeatedly last week.

All replies (6)

_{Friday, June 16, 2017 9:45 PM}

Hi,

You don't have to configure any option in DHCP.

You have just to be sure IP relay is configured from client network to dhcp server and client server to pxe server (if they are not on the same network) If 3 are on the same network, you don't have to do nothing. Client will do broadcast request when they boot and find dhcp server and pxe server.

If you reboot your pxe server same issue ? Are you up to date because I know there is a bug in pxe service in sccm 2012. Do you have any event log ? wds service is started ?

Merci de marquer comme réponse les sujets qui vous ont permis d'avancer afin que cela puisse être bénéfique aux personnes qui rencontrent le même problème.

_{Monday, June 19, 2017 9:52 AM}

Hi,

Have you also examined the smspxe.log on your site server? Also, have you enabled the options "Allow this distribution point to respond to incoming PXE requests" and "Enable unknown computer support" on DP properties?

Regards,

Jimmy

Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].

_{Monday, June 26, 2017 3:44 PM}

Hi,

You don't have to configure any option in DHCP.

You have just to be sure IP relay is configured from client network to dhcp server and client server to pxe server (if they are not on the same network) If 3 are on the same network, you don't have to do nothing. Client will do broadcast request when they boot and find dhcp server and pxe server.

If you reboot your pxe server same issue ? Are you up to date because I know there is a bug in pxe service in sccm 2012. Do you have any event log ? wds service is started ?

Merci de marquer comme réponse les sujets qui vous ont permis d'avancer afin que cela puisse être bénéfique aux personnes qui rencontrent le même problème.

I'm sorry it took me so long to respond, I've been traveling extensively. Getting back to this...the DHCP, SCCM and client are all on the same subnet, the SCCM server is up to date with all patches etc. and this was working but then stopped. Server has been rebooted, same issue.

_{Monday, June 26, 2017 3:49 PM}

Hi,

Have you also examined the smspxe.log on your site server? Also, have you enabled the options "Allow this distribution point to respond to incoming PXE requests" and "Enable unknown computer support" on DP properties?

Regards,

Jimmy

Where are the smspxe.log located?

As for my DP settings...

- Enable PXE support for clients = checked

- Allow this distribution point to respond to incoming PXE requests = checked

- Enable unknown computer support = checked

- Respond to PXE requests on all network interfaces = radio button selected

_{Monday, June 26, 2017 6:42 PM}

I got this to work after continuing to fiddle with it...it turned out to be two things.

1 - my WDS service was not only not running but wasn't even installed. I may have at some point removed the role and not added it back in. Thank you for a pointer to look there.

2 - my drive was running out of space and when I tried to deploy the OS.wim file I believe it was failing.

Thank you again...but I'm not out of the woods yet.

Imaging now it goes well I can see it installing drivers etc. and then throws up error code 0x8004005 and aborts.

I'm looking for my smspxe.log file and have searched both C: and D: drive (where SCCM is installed) and I do not have this log. I'm not sure why it's not writing to it.

_{Tuesday, June 27, 2017 4:30 AM}

Hi,

SMSPXE.log is only used for troubleshooting PXE boot issues, it is located at the PXE enabled DP server. If the PXE boot is fine and you got errors during the OSD task sequence, you should examine the smsts.log instead. The smsts.log should be found at c:\SMSTaskSequence\Logs\Smstslog\smsts.log or c:\windows\ccm\logs\Smstslog\smsts.log if the error appears after the installing drivers step.