none
SCCM PXE Boot Errors RRS feed

  • Question

  • Having an issue getting the PXE boot to work using the PXE Responder (although we haven't gotten it to work any other way either). On the client side I'm receiving a PXE-E52: proxyDHCP offers were received. No DHCP offers were received error.

    From the SCCM server, here are the logs were receiving when attempting to PXE boot.

    PXE: Received packet from 10.100.191.1 (DHCP, 00:50:56:8E:62:CD, 10.100.13.76). SCCMPXE 7/3/2019 10:25:25 AM 13644 (0x354C)
    Operation: 1, Address type: 1, Address length: 6, Hop Count: 1, Transaction ID: 89159f07, Seconds since boot: 0, Address: 10:65:30:f1:04:90:00:00:00:00:00:00:00:00:00:00, Host name: , Boot file name: , Client IP: 0.0.0.0, Host IP: 0.0.0.0, Server IP: 0.0.0.0, Relay IP: 10.100.191.1
    Options: <bunch of numbers, removed>
    PXE: 10:65:30:F1:04:90: Operation=1, MessageType=1, Architecture=7, Continuation=0 SCCMPXE 7/3/2019 10:25:25 AM 5712 (0x1650)
    PXE: 10:65:30:F1:04:90: Parsed a discover/solicit packet. SCCMPXE 7/3/2019 10:25:25 AM 5712 (0x1650)
    PXE: 10:65:30:F1:04:90: 4C4C4544-0059-3010-8054-B1C04F4E4E32: Client is 64-bit, UEFI, Firmware. SCCMPXE 7/3/2019 10:25:25 AM 5712 (0x1650)
    PXE: 10:65:30:F1:04:90: Prioritizing local MP https://DSJSCCM01.ad.matsugov.us. SCCMPXE 7/3/2019 10:25:25 AM 5712 (0x1650)
    SSL - using authenticator in request. SCCMPXE 7/3/2019 10:25:25 AM 5712 (0x1650)
    In SSL, but with no client cert SCCMPXE 7/3/2019 10:25:25 AM 5712 (0x1650)
    SSL - using authenticator in request. SCCMPXE 7/3/2019 10:25:25 AM 5712 (0x1650)
    In SSL, but with no client cert SCCMPXE 7/3/2019 10:25:25 AM 5712 (0x1650)
    Client Boot Get ID Info reply: <ClientIDReply><Identification Unknown="0" DuplicateSMBIOS="0" DuplicateMACAddress="0" ItemKey="0" ServerName=""><Machine><ClientID/><NetbiosName/></Machine></Identification><ClientIDInfo ItemKey="16777400" ClientID="GUID:E1B85BBB-0932-4B97-B542-FDE732B60D19" DuplicateSMBIOS="0" DuplicateMACAddress="0" MatchType="1"/></ClientIDReply>
    SCCMPXE 7/3/2019 10:25:25 AM 5712 (0x1650)
    PXE: 10:65:30:F1:04:90: System records: SCCMPXE 7/3/2019 10:25:25 AM 5712 (0x1650)
    PXE: 10:65:30:F1:04:90:   16777400, GUID:E1B85BBB-0932-4B97-B542-FDE732B60D19, SMBIOS ID is a match, MAC Address is NOT a match. SCCMPXE 7/3/2019 10:25:25 AM 5712 (0x1650)
    PXE: 10:65:30:F1:04:90: Using system record 16777400, GUID:E1B85BBB-0932-4B97-B542-FDE732B60D19. SCCMPXE 7/3/2019 10:25:25 AM 5712 (0x1650)
    Operation: 2, Address type: 1, Address length: 6, Hop Count: 1, Transaction ID: 89159f07, Seconds since boot: 0, Address: 10:65:30:f1:04:90:00:00:00:00:00:00:00:00:00:00, Host name: , Boot file name: , Client IP: 0.0.0.0, Host IP: 0.0.0.0, Server IP: 10.100.13.76, Relay IP: 10.100.191.1
    Options:<bunch of numbers, removed>
    PXE: Sending reply to 10.100.191.1, DHCP. SCCMPXE 7/3/2019 10:25:25 AM 5712 (0x1650)

    Some information about our environment. We do use HTTPS and we have the cert loaded into the DP. Any help would be much appreciated.


    • Edited by erlandday Wednesday, July 3, 2019 6:33 PM
    Wednesday, July 3, 2019 6:32 PM

Answers

  • We have an IP helper in place with both DHCP server and SCCM server

    it looks like this client does not have (is not getting) IP address from DHCP ?

    Don [doesn't work for MSFT, and they're probably glad about that ;]

    • Marked as answer by erlandday Wednesday, July 3, 2019 10:37 PM
    Wednesday, July 3, 2019 9:30 PM

All replies

  • Are you using any DHCP Options?
    Wednesday, July 3, 2019 7:28 PM
  • We have an IP helper in place with both DHCP server and SCCM server

    Wednesday, July 3, 2019 8:50 PM
  • We have an IP helper in place with both DHCP server and SCCM server

    it looks like this client does not have (is not getting) IP address from DHCP ?

    Don [doesn't work for MSFT, and they're probably glad about that ;]

    • Marked as answer by erlandday Wednesday, July 3, 2019 10:37 PM
    Wednesday, July 3, 2019 9:30 PM
  • That's what I think as well. Since we have the IP Helper's in place, do we also need to have some DHCP scope in place for it to work?

    Wednesday, July 3, 2019 10:10 PM
  • Thank you thank you. It was a combination of the IP Helper set incorrectly and not having a boundary setup for that VLAN. Thank you.
    Wednesday, July 3, 2019 10:38 PM
  • Hi,
     
    Thanks for your sharing. This may help the users who have similar issue. Thank you!
     
    Best regards,
    Simon Ren

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Thursday, July 4, 2019 2:41 AM