Dhcp Proxy Error
Contents |
(עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeWindows Server 2012Windows Server 2008 R2Windows Server 2003LibraryForums Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove dhcp proxy option From My Forums Answered by: PXE-E55: ProxyDHCP service did not dhcp proxy server reply to request on port 4011 (on Physical Machines) Windows Server > Windows Server General dhcp web proxy Forum Question 0 Sign in to vote Hi, Recently we have been facing issues when using our PXE service. We are getting PXE-E55: ProxyDHCP service did
Dhcp Proxy Mode
not reply to request on port 4011when we try to pxe boot Physical machines. However, if we try the same with VM's, we can successfully deploy an OS using the PXE service. Our WDS server is not on the same server having the DHCP service. I'm really not sure what's causing the dhcp proxy 4011 problem since we can make it wotk on vm's but not on physical machines. I don't know if it has something to do with our DHCP having 95% IP addresses being used. Help is much appreciated. Ron Thursday, February 16, 2012 3:02 AM Reply | Quote Answers 0 Sign in to vote Hi Ron, Please try to set the network boot referral and see whether it works. In order to do this, please configure the following DHCP options in DHCP scope. It will direct PXE clients to an appropriate NBP. Option 60= PXEClient Option 66= WDS server name or IP address Option 67= Boot file name For detailed information about configure network boot grogram, please refer to the following article: Managing Network Boot Programs http://technet.microsoft.com/en-us/library/cc732351(WS.10).aspx#BKMK3 In addition, also check the same question answered at the following thread. Hope it helps. WDS - PXE No reply from DHCP port 4011 http://social.technet.microsoft.com/Forums/en-US/windowsserver2008r2general/thread/852e57f3-50b4-48ae-a7a9-6e706afd3bbe Best Regards, AidenAid
not reply to request on port 4011" SYMPTOM When being dhcp proxy mode dd wrt started, the PXE client comes up with the
Dhcp Proxy Vs Relay
PXE copyright message, then displays DHCP.... After a while, the following error
Dhcp Proxy Setting
message is displayed: PXE-E55: proxyDHCP did not reply to request on port 4011 Depending on the PXE client's system setup https://social.technet.microsoft.com/Forums/windowsserver/en-US/3747b974-ba4f-41e4-abd9-a2e7a38e994b/pxee55-proxydhcp-service-did-not-reply-to-request-on-port-4011-on-physical-machines?forum=winservergen 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. CAUSE The "PXE-E55" error indicates that the PXE client has sent a request to the proxyDHCP https://www.bootix.com/support/problems_solutions/pxe_e55_proxydhcp_service_did_not_reply_to_request_on_port_4011.html server on port 4011, but did not receive a reply. This problem can only 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, and let both 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. Back to Problems & Solutions overview
7Windows XPForumsSoftware Search Sunday, October 9, 2016HomeBooksForumsAbout MeAdvertisePrivacy PolicyVideosContact Me Sign inWelcome! Log into your accountyour usernameyour password Forgot your password? Get helpPassword recoveryRecover your passwordyour email A password will be e-mailed to you. PrajwalDesai.Com ExchangeExchange 2010Exchange 2013Exchange 2016LyncSystem CenterSCCMSCCM TroubleshootingSCOMCloudAzureIntunePowerShellWindowsWindows ServerWindows Server 2016Windows Server 2012 R2Windows Server 2008 R2Windows ClientWindows http://prajwaldesai.com/pxe-e55-proxydhcp-did-not-reply-to-request-on-port-4011/ 10Windows 8.1Windows 7Windows XPForumsSoftware SCCMSCCM Troubleshooting PXE-E55 ProxyDHCP did not reply to request on port 4011By Prajwal Desai - September 14, 201526534 Share on Facebook Tweet on Twitter 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 dhcp proxy 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.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 dhcp proxy mode 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). TAGSOSDSCCM 2012 R2SHARE Facebook Twitter Previous articleSCCM 2012 R2 SP1 Upgrade GuideNext articleSecure Your Email Account from HackersPrajwal Desaihttp://prajwaldesai.comI am Prajwal Desai and I have been working in the IT for over 8 years with a strong focus on Microsoft Server Technologies. For the last fi