Client IP: 000.000.000.000 while attempting PXE Boot

SAMUEL VALAPARLA 131 Reputation points
2021-03-16T10:44:33+00:00

Hi All,

At a new site where we've set up a DP, Sync'd OSD content we're seeing issues when attempting to PXE Boot computers. CB 2006

One odd thing I can see in the SMSPXE.log of the DP is that whenever an unsuccessful PXE client request comes in, we're not seeing the IP Address of the incoming client. It's just marked as Client IP: 000.000.000.000. However we're able to see the MAC Address of the device and also the lookup happening against SCCM to determine the advertisement. However there is no "============> REQUEST Reply to client " that is being sent back to the client which usually follows by default.

Below is a snippet from the SMSPXE.log

============> Received from client: SMSPXE 3/16/2021 9:21:38 AM 3376 (0x0D30)
Operation: BootRequest (1) Addr type: 1 Addr Len: 6 Hop Count: 0 ID: D5B53E93
Sec Since Boot: 4 Client IP: 000.000.000.000 Your IP: 000.000.000.000 Server IP: 000.000.000.000 Relay Agent IP: 000.000.000.000
Addr: 89:73:5a:bd:bd:07:
Magic Cookie: 63538263
Options:
Type=53 Msg Type: 1=Discover
Type=57 Max Msg Size: 05c0
Type=55 Param Request List: 0102030405060c0d0f111216171c28292a2b3233363a3b3c4243618081828384858687
Type=97 UUID: 0044454c4c500010358044b2c04f583933
Type=94 UNDI: 010310
Type=93 Client Arch: EFI BC
Type=60 ClassId: PXEClient:Arch:00007:UNDI:003016 SMSPXE 3/16/2021 9:21:38 AM 3376 (0x0D30)
Not in SSL. SMSPXE 3/16/2021 9:21:38 AM 6568 (0x19A8)
Client lookup reply: <ClientIDReply><Identification Unknown="0" DuplicateSMBIOS="0" DuplicateMACAddress="0" ItemKey="16952027" ServerName=""><Machine><ClientID/><NetbiosName/></Machine></Identification></ClientIDReply>
SMSPXE 3/16/2021 9:21:38 AM 7720 (0x1E28)
89:73:5A:BD:BD:07, 4C4C4544-0050-3510-8044-B2C04F583933: Device is in the database. SMSPXE 3/16/2021 9:21:38 AM 7720 (0x1E28)
Not in SSL. SMSPXE 3/16/2021 9:21:38 AM 7720 (0x1E28)
Request using architecture 9. SMSPXE 3/16/2021 9:21:38 AM 7720 (0x1E28)
Not in SSL. SMSPXE 3/16/2021 9:21:38 AM 7720 (0x1E28)
Not in SSL. SMSPXE 3/16/2021 9:21:39 AM 6568 (0x19A8)
Client boot action reply: <ClientIDReply><Identification Unknown="0" DuplicateSMBIOS="0" DuplicateMACAddress="0" ItemKey="16952027" ServerName=""><Machine><ClientID>GUID:5C6C0006-42BC-44B5-921B-7C97E843A918</ClientID><NetbiosName/></Machine></Identification><PXEBootAction LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="ABC201E9" OfferIDTime="2/27/2021 4:32:00 AM" PkgID="ABC01257" PackageVersion="" PackagePath="http://DPServerName.domain.group.com/SMS_DP_SMSPKG$/ABC01098" BootImageID="ABC01098" Mandatory="1"/></ClientIDReply>
SMSPXE 3/16/2021 9:21:41 AM 7720 (0x1E28)
89:73:5A:BD:BD:07, 4C4C4544-0050-3510-8044-B2C04F583933: using advertisement ABC201E9 SMSPXE 3/16/2021 9:21:41 AM 7720 (0x1E28)
Operation: BootReply (2) Addr type: 1 Addr Len: 6 Hop Count: 0 ID: D5B53E93
Sec Since Boot: 0 Client IP: 000.000.000.000 Your IP: 000.000.000.000 Server IP: 010.xx.xx.148 Relay Agent IP: 000.000.000.000
Addr: 34:73:5a:bd:ce:04:
Magic Cookie: 63538263
Options:
Type=53 Msg Type: 2=Offer
Type=54 Svr id: 010.xx.xx.148
Type=97 UUID: 0044454c4c500010358044b2c04f583933
Type=60 ClassId: PXEClient SMSPXE 3/16/2021 9:21:41 AM 7720 (0x1E28)
Client lookup reply: <ClientIDReply><Identification Unknown="0" DuplicateSMBIOS="0" DuplicateMACAddress="0" ItemKey="16952027" ServerName=""><Machine><ClientID/><NetbiosName/></Machine></Identification></ClientIDReply>
SMSPXE 3/16/2021 9:21:43 AM 6568 (0x19A8)
89:73:5A:BD:BD:07, 4C4C4544-0050-3510-8044-B2C04F583933: Device is in the database. SMSPXE 3/16/2021 9:21:43 AM 6568 (0x19A8)
Not in SSL. SMSPXE 3/16/2021 9:21:43 AM 6568 (0x19A8)
Request using architecture 9. SMSPXE 3/16/2021 9:21:43 AM 6568 (0x19A8)
Not in SSL. SMSPXE 3/16/2021 9:21:43 AM 6568 (0x19A8)

Very rarely we see the client IP show up in the PXE Client request and such are handled successfully. But most of the others are ending up unsuccessful without any obvious error in the logs. Also on the device side we're seeing a "PXE-E16 : No valid offer received" error. While we're also reviewing this with our network team (DHCP) who haven't found anything credible so far, just looking for some thoughts and tips on this behaviour, please.

Thank You.

Microsoft Configuration Manager Deployment
Microsoft Configuration Manager Deployment
Microsoft Configuration Manager: An integrated solution for for managing large groups of personal computers and servers.Deployment: The process of delivering, assembling, and maintaining a particular version of a software system at a site.
939 questions
Microsoft Configuration Manager
{count} votes

2 answers

Sort by: Most helpful
  1. Fiona Yan-MSFT 2,311 Reputation points
    2021-03-17T08:12:57.043+00:00

    @SAMUEL VALAPARLA

    Thank you for posting in Microsoft Q&A forum.

    Sec Since Boot: 0 Client IP: 000.000.000.000 Your IP: 000.000.000.000 Server IP: 010.xx.xx.148 Relay Agent IP: 000.000.000.000

    It is expected that the client will not have not IP address during the "discover" phase. From the description we provide above, It seems trying to discover the DHCP and PXE servers. The DHCP server has not assigned an IP. That happens during the "offer" phase.

    89:73:5A:BD:BD:07, 4C4C4544-0050-3510-8044-B2C04F583933: Device is in the database. SMSPXE 3/16/2021 9:21:38

    Could we know which collection we have deployed? This machine seems to be known client, it could boot successful if the known collection was deployed.

    While we're also reviewing this with our network team (DHCP) who haven't found anything credible so far.

    Have we tried to use one client with operating system to see if it could connect to the DHCP server?

    Have a good day!


    If the response is helpful, please click "Accept Answer" and upvote it.
    Note: Please follow the steps in [our documentation][1] to enable e-mail notifications if you want to receive the related email notification for this thread.

    0 comments No comments

  2. SAMUEL VALAPARLA 131 Reputation points
    2022-06-23T15:50:28.15+00:00

    So we found that for the specific Network on which this PXE build was being performed, the DHCP Pool was exhausted and there were no IPs being issued out for assignment. Due to this any new builds weren't receiving any IP Addresses. Once the pool was refreshed, we could see valid IPs being received and the build progressed further.

    0 comments No comments