PXE-E55 ProxyDHCP did not reply to request on port 4011
PXE-E55 ProxyDHCP did not reply to request on port 4011 When you try to start a Pre-Boot Execution Environment (PXE) client computer, you may see the message PXE-E55 Proxy DHCP Service did not reply to request on port 4011. Depending on the PXE client’s system setup boot device list configuration, the PC then either stops or tries to boot from the next boot device in the system setup boot device list.
PXE-E55 ProxyDHCP did not reply to request on port 4011
CAUSE – 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.
RESOLUTION – 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).
Do you want use WDS ?
close your DHCP 60 port.
and set 66: server hostname or IP
set 67: boot \ x64 \ wdsnbp.com
install tftp server,this is very important!!!!
then next you can download from tftp wdsnbp.com
Clearing my Pending/Approved devices resolved this for me as it was only on a single machine.
Option 60 was set as it is both DHCP and I know it worked as I’d already imaged the machine once but needed to re-run it for a test change
hi I have tried all the above and still not having joy please can someone help
Do you want use WDS ?
close your DHCP 60 port.
and set 66: server hostname or IP
set 67: boot \ x64 \ wdsnbp.com
add tftp server,this ip very important!!!!
then next you can download from tftp wdsnbp.com
The problem in my case here in Norway was that I had reserved an IP address for my computer. Deleting the reservation made the computer PXE-boot from SCCM again and deployment started as it should.
Kjetil B.
Thanks for the update
Hi Prajwal,
I’m having the following problem when I try to PXE boot.
Please advice.
Thanks,
Nick
Option 60 is missing in the DHCP Server
If your DHCP server and WDS server are on the same physical machine, you need to check the “Do not listen on port 67” and Configure DHCP option 60 to PXEClient in WDS server properties. To do this, please open WDS Server console, right click the WDS server you have added and click Properties, navigate to DHCP tap and check the above two options. After that, WDS Server will add DHCP option 60 to the packets sent to PXE client. There is no need to configure DHCP option 60 on DHCP server. If your DHCP server and WDS server are on different physical machine, there is no additional operations needed and WDS server will automatically add DHCP option 60 to PXE client.