The PXE client receives the error "PXE-E55: proxyDHCP service did not reply to request on port 4011."
For all versions of Deployment Solution (6.x and 7.x), this issue could show up as follows:
1. When looking at TCPVIEW (http://www.microsoft.com/technet/sysinternals/default.mspx ), 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
For 6.x only:
1. In Deployment Solution 6.9 and later, this error can occur in initial deployment if the option in PXE configuration under the DS tab is selected to only PXE boot computers that have Deployment jobs assigned to them.
2. Looking in the pxemanager.ini file in the proxy DHCP section as seen below.
[PXEServer\Shared\ProxyDHCP]
Discovery_BCast_Disabled=True
Discovery_Local_Bstrap=True
Discovery_Local_Image="BStrap"
Discovery_MCast_Addr="224.0.1.2"
Discovery_MCast_Disabled=True
Discovery_Server_List_Only=False
ServerName=""
DomainName=""
IsDomain=False
Parsers="PXEParser"
PROC_ARCH="0,X86PC","2,IA64","32,X64"
StartBootService=True
StartProxy=True
AllowIPFragmentation=True
The two highlighted lines above are the key to this issue. The above section is what a good, uncorrupted section should look like.
The PXE server will send out the PXE menu even if one of those lines are set to =False. If both of them are set to =False, the PXE server will not sent out the PXE boot menu.
If both of those lines are set to =False, then some corruption has entered the pxemanager.ini file.
For all versions of Deployment Solution (6.x and 7.x)
Applies To
Deployment Solution, all versions