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

Muneer Jahangeer 46 Reputation points
2021-12-01T12:59:45.517+00:00

Apologies if my question was answered already in some other way. Request your assistance to fix the PXE boot issue please,
Server :
Primary server has below roles,
DHCP [ Address pool start IP address is, xx.xx.100.71 and End IP address is, xx.xx.101.240]
AD
IP : xx.xx.100.2
Secondary server has below roles:

DHCP [ Same as primary]

SCCM Server has below roles:
IP: xx.xx.100.23
WDS : Just installed but not configured (Note: instead , enabled Enable a PXE responder without windows deployment service option in Distribution point]
SCCM version 2103

PXE Network boot testing:

Scenario 1: Physical Machine: [ Network Legacy PXE Boot]
it is communicating properly to the primary server and assigning IP from DHCP server "xx.xx.101.xx" however at the end of the screen - receiving an error: PXE-E55: ProxyDHCP service did not reply to request on port 4011.

Scenario 2: Created hyper-V on SCCM server. enabled Legacy network boot. same error.

Could you please check and let me know how to troubleshoot and fix the issue please

Windows Server
Windows Server
A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.
12,113 questions
0 comments No comments
{count} vote

Accepted answer
  1. Limitless Technology 39,351 Reputation points
    2021-12-01T16:16:18.3+00:00

    Hello MuneerJahangeer-4994

    The cause is that, for a PXE server to respond to a PXE request, the request must be able to transverse routers to communicate with PXE servers on other subnets. PXE uses the DHCP option fields to pass information. Therefore having the PXE server in the routers IP helper table helps make sure that the DHCP packets are forwarded to the PXE server so the PXE server can respond correctly. The PXE-E55 error indicates that the PXE client has sent a request to the proxyDHCP server on port 4011, but did not receive a reply. This problem can occur when the DHCP Class Identifier Option 60 is set on the DHCP server, but there is no proxyDHCP service running on port 4011 on the same machine.

    To resolve this, If you are operating DHCP and proxyDHCP services on different machines, do not set the DHCP Class Identifier Option 60 in the DHCP configuration. Allow services run on port 67 UDP (bootps).

    If you are operating DHCP and proxyDHCP services on the same machine, set the DHCP Class Identifier Option 60 in the DHCP configuration. Let the DHCP service run on port 67 (UDP) and the proxyDHCP service on port 4011 (UDP).


    --If the reply is helpful, please Upvote and Accept as answer--

    1 person found this answer helpful.
    0 comments No comments

1 additional answer

Sort by: Most helpful
  1. Muneer Jahangeer 46 Reputation points
    2021-12-08T11:46:59.727+00:00

    Thanks for your valuable suggestions.

    Looks like Antivirus software blocks a few ports in the firewall. For testing purposes, disabled the firewall and reran the PXE, working as expected.

    0 comments No comments