This pxe-e55 “error indicates that the PXE client has sent a request to the proxy DHCP server on port 4011, but has not received a reply. It seems that this problem only occurs when the DHCP class identifier option # 60 is set on the DHCP server, but there is no proxy DHCP service running on port 4011 on the same computer
If you operate the DHCP and proxy DHCP services on different computers, do not set the DHCP class identifier option in the DHCP configuration, and let the two services run on port 67/UDP
If you operate the DHCP and proxy DHCP services on the same computer, please set the DHCP class identifier option in the DHCP configuration. Let the DHCP service run on port 67/UDP and the proxy DHCP service run on port 40111 UDP
Here is an link to this question
https://kb.acronis.com/content/8358
At the same time, you can restart the WDS service
Please make sure you have checked this:
When creating an operating system deployment for x64 BIOS computers only, the x64 boot image and x64 boot image must be available on all DPS
my experimental environment :
VMware, both client and server use VMware 8 (NAT) network, and use local DHCP service when shutting down
server win-2008: DHCP (192.168.1.1-100), DNS（ www.feiquan.net ）, WDS server, feiquan.com (192.168.1.132) domain
start from PXE after client configuration: prompt error: proxydhcp service did not reply to request on port 4011
solution:
If Windows Deployment Services and DHCP are running on the same computer, configuring Windows Deployment Services to not respond to any client computers will not work. This is because although Windows Deployment Services will not respond, DHCP will. You can try to work around this issue by disabling DHCP option 60 on the DHCP tab
the main reason is that the configuration of DHCP is wrong. To add 60,67 as boot/x64/wdsnbp.com, because my DHCP and WDS server are the same computer, and then restart the WDS server
server:
DHCP server configuration :
DNS server:
WDS server:
If you want to restart WDS server and DHCP server after modifying 60 and 67 of DHCP. The client then requests recognition again. If you do not restart, you will still be prompted with the above error even after you modify the configuration. I just restart the computer
client:
