Forums on Intune, SCCM, and Windows 11

Welcome to the forums. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your topics and posts, as well as connect with other members through your own private inbox!

SOLVED SCCM PXE just stopped working?

  • Thread starter Thread starter Cliff
  • Start date Start date
  • Replies Replies 2
  • Views Views 1K
Status
Not open for further replies.

Cliff

Member
Messages
14
Solutions
1
Reaction score
2
Points
3
Hi we are on the latest sccm build an have the latest SDK installed, for some reason over the weekend, PXE has stopped
it responds with IP and then a 20 second pause and then a quick flash on the screen and the machine continues to boot from the hard disk..
normally see this behavior if the mac address exists in sccm, but thats not the case for this,, the smspxe.log, below, shows nothing of any real help...
the only bit I dont understand is the host ip saying 0.0.0.0, not sure if thats how it used to be or not, nothing changed on the network
some suggestions would be great,,
thanks
1722890667547.png
 
Solution
There are no errors in the log file. But I see the following in the log file: "MAC address is in the list of common hardware identifiers. Discarding from the list. Use hierarchy settings to manage duplicate hardware identifiers."
Thanks for the reply, I found the issue, one of our networking guys thought it would be good to drop all tftp traffic on the main firewall.. problem now solved :)
There are no errors in the log file. But I see the following in the log file: "MAC address is in the list of common hardware identifiers. Discarding from the list. Use hierarchy settings to manage duplicate hardware identifiers."
 
There are no errors in the log file. But I see the following in the log file: "MAC address is in the list of common hardware identifiers. Discarding from the list. Use hierarchy settings to manage duplicate hardware identifiers."
Thanks for the reply, I found the issue, one of our networking guys thought it would be good to drop all tftp traffic on the main firewall.. problem now solved :)
 
Solution
Status
Not open for further replies.
Back
Top