PENDING PXE-E55: ProxyDHCP service did not reply to request on port 4011

[MedHajjem]

hello
following the preparation of the system deployment with scp 2309, I installed and configured the wds role for pxe, add a wim image with the latest ISO of windows 10 2202 H2, distribute the contents,in the dcp part, I added the options (60,66 and 67 ) .now when I test the boot in a machine by F12 it does not pass
attached are screenshots of the configuration
Cordially

 

[Prajwal Desai]

What do you see when you PXE boot? DO you see the message "press F12 for network boot"?

 

[MedHajjem]

hi,
please find attached the screenshots displayed when I click on F12
Cordially;

 

[Prajwal Desai]

From the screenshot that you attached, I see you are experiencing the following error: PXE-E55: ProxyDHCP service did not reply to request on port 4011

Solution: In order for a PXE server to reply to a PXE request, the request needs to be able to communicate with PXE servers on other subnets by traversing routers. PXE transfers data using the DHCP option fields.

In order for the PXE server to react appropriately, it is helpful to ensure that DHCP packets are routed to it by including the PXE server in the router's IP assistance table.

The PXE-E55 error message suggests that the PXE client attempted to connect to the proxyDHCP server on port 4011 but was unable to establish a connection. When the DHCP server has the DHCP Class Identifier Option 60 configured, but the proxyDHCP service is not operating on port 4011 on the same system, an issue may arise.

To fix this, In the DHCP setup, do not set the DHCP Class Identifier Option 60 if you are running DHCP and proxyDHCP services on separate machines. Permit services to operate on UDP port 67 (bootps). In the DHCP settings, specify the DHCP Class Identifier Option 60 if you are running both DHCP and proxyDHCP services on the same computer. Allow the proxyDHCP service to operate on port 4011 (UDP) and the DHCP service to operate on port 67 (UDP).

 

[MedHajjem]

Hi Prajwal,
for the dhcp proxy, do I need to add a new option in the DHCP settings or just a service to allow in the dhcp server and SCCM?

Cordially

 

[Prajwal Desai]

DHCP options shouldn't be configured for PXE boot at all. You must use IP helpers instead.

 

[MedHajjem]

hello,
please find attached the error detected when I disabled DHCP option 60
Cordially;

 

[MedHajjem]

Hello,

When I activate the 060 PXE CLient in the extension , I receive the message from port 4011
Cordially

 

[Prajwal Desai]

You must contact your network team for this. Basically the DHCP is not forwarding the request to PXE server. If that is not the case, repair the PXE once.

 

[MedHajjem]

hi,
I've noticed that the WDS service is not running on the SCCM server. Is this normal?

 

[Prajwal Desai]

WDS should be running for PXE to work.

 

[MedHajjem]

Hi Prajwal,
I notice that sccmpxe also uses the same ports 67,69 and 4011 as WDS, so since these ports are reserved by SCCMPXE, WDS can't stay running.

 

[MedHajjem]

hi,
I have installed a new windows 2019 server and I have mounted the WDS role, after changing the IP in dhcp of the new WDS, I have succeeded in booting to the WDS server from a workstation.
Cordially;

 

[MedHajjem]

hello,
please find attached the captures of the detected errors

Cordially

 

[Prajwal Desai]

You must repair the PXE as I see some of the files are missing. Why are you not using PXE Responder instead - https://www.prajwaldesai.com/enable-pxe-responder-without-wds-on-sccm-dp/

 

[MedHajjem]

hello
Comment puis-je réparer le PXE dans sccm, j'ai activé l'option de répondeur PXE, ma version actuelle de SCCM est 2309




Cordially

 

[Prajwal Desai]

hello
Comment puis-je réparer le PXE dans sccm, j'ai activé l'option de répondeur PXE, ma version actuelle de SCCM est 2309




Cordially

Please post your responses in English so that everyone can understand.

 

[MedHajjem]

Hello,
I'm really sorry,
how can I fix the PXE in sccm ?
i have enabled the PXE responder otion
my current version SCCM is 2309

Thanks

 

[MedHajjem]

hello Prajwal,
To isolate the source of my blocage , i installed separately in a new windows server 2019 the wds server , i changed in the DHCP extents the IP of the startup server by the IP of WDS and I succeeded in booting by F12 to this server
So here , i'm reassured that my blocage is at the SCCM level.
I repaired and redistributed the PXE but the problem still persists , I can't boot to the image
please find attached SMSPXE and distmgr logs

Cordially

 

[MedHajjem]

Hello Prajwal,

I haven't heard back from you

Cordially;