PXE-E55: proxyDHCP service did not reply to request on port 4011
|Article:TECH12489|||||Created: 2006-02-15|||||Updated: 2014-11-12|||||Article URL http://www.symantec.com/docs/TECH12489|
The PXE client receives the error "PXE-E55: proxyDHCP service did not reply to request on port 4011."
Deployment Solution, all versions
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.
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)
The following are resolutions to the above mentioned causes:
- If the PXE server is responding with corrupt packets, most likely you will need to do a full complete reinstall of PXE. Article 3724, " How do I reinstall PXE Manager and PXE server cleanly from a DS 6.5, DS 6.8 and DS 6.9 environment??" explains how to do this. If this error persists after reinstalling, you might need to update to the latest release of Deployment Solution as well.
- If the problem is being caused by a network error, there really isn't anything that can be done with the Deployment Server configuration or installation to fix the error. The core issue has to be resolved in the configuration of your network devices. To determine if this really is the case, however, check to make sure that that same "bootp" packets that are leaving the client are getting to the PXE server, and vice versa. This would have to be verified in network traces.
- Rename the pxe.ini to pxe.ini.old and restart the PXE Config Helper service. If the PXE Server and PXE MTFTP Server services start, check your PXE.ini file for the correct IP of the server.
Article URL http://www.symantec.com/docs/TECH12489