PXE-E55: proxyDHCP service did not reply to request on port 4011
search cancel

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

book

Article ID: 152207

calendar_today

Updated On:

Products

Deployment Solution Ghost Solution Suite

Issue/Introduction

The PXE client receives the error "PXE-E55: proxyDHCP service did not reply to request on port 4011."

Environment

Deployment Solution 8.x

Cause

For all versions of Deployment Solution (6.x and 7.x), this issue could show up as follows:

  1. When looking at TCPVIEW (https://learn.microsoft.com/en-us/sysinternals/downloads/tcpview), the services are binding to the correct ports. These ports are 67, 69, 4011.
  2. When a wireshark (http://www.wireshark.org/download.html) trace is run, the user will see that the client is repeating it’s attempts to communicate with the PXE/NBS server because Option 60 is set up in the DHCP Scope Options Having Option 60 enabled will cause the client to attempt to communicate with the DHCP server as it’s PXE/NBS server and ignore the server that is actually hosting PXE/NBS

Resolution

For all versions of Deployment Solution (6.x and 7.x)

The most common issue that causes this is DHCP Scope Options being configured when they don’t need to be. Most common among these is Option 60. If DHCP and PXE/NBS are hosted from separate servers, then Option 60 (as well as options 43, 66, and 67) should not be enabled.
 
To fix the corrupted pxemanager.ini file, the following needs to be done on the server that has the PXE manager installed on it.
  1.     Open the services panel.
  2.     Stop the PXE manager service.
  3.     Go to the eXpress share.
  4.     Go to the PXE folder.
  5.     Open the pxemanager.ini file.
  6.     Find the following section > [PXEServer\Shared\ProxyDHCP].
  7.     Highlight that section and delete it.
  8.     Highlight and copy all of the above [PXEServer\Shared\ProxyDHCP] section in the Cause section to the pxemanager.ini file.
  9.     Save the file.
  10.     Go back to the services panel
  11.     Start the pxe manager service.
  12.     This will then download a new pxe.ini.tmp file to the PXE servers.
  13.     PXE will now work and download the PXE boot menu and work as expected.