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

Article:TECH12489  |  Created: 2006-02-15  |  Updated: 2013-09-05  |  Article URL http://www.symantec.com/docs/TECH12489
Article Type
Technical Solution

Product(s)

Issue



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


Environment



Deployment Solution, all versions


Cause



The PXE and DHCP servers were not on the same computer. This problem was caused by a PXE setting on the DHCP server. 

In Deployment Solution 6.9 and later, this error can occur in intial 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.

In Deployment Solution 6.5 and 6.8 (all versions) this issue could be as follows:

 

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.

 

When a wireshark (http://www.wireshark.org/download.html) trace is run, the user will see that the client is sending up a request to the pxe server, but the pxe server does not reply and send out the pxe menu.

 

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.


Solution



 

 

 

 

 

 

A very simple first thing to check if you are ONLY having the error in Deployment Solution 6.9 and later AND are only seeing the problem in Initial Deployment: Go into the PXE configuration Utility and under the DS tab, check to see if the option to only process computers with Deployment jobs is checked. If it is, uncheck it and this should resolve the issue.

If that is not the problem, the best way to diagnose the exact root cause (and then get to a direct resolution) of this error message is to run a network trace (using WireShark or Ethereal) from the PXE server and filter the trace to look for all of the "bootp" packets. The Altiris Knowledgebase article 17282, "Deployment Solution 6.5 PXE IP Communications Detail" gives information on what to look for in a PXE network trace.

The following are resolutions to the above mentioned causes:

  1. Check the DHCP server options on your DHCP server. If PXE and DHCP are on separate computers, none of the PXE DHCP options should be enabled (these include options 043, 060, 066, and 067). For more details on modifying DHCP options refer to article 17347, "Creating and setting option 060 on a DHCP server."
  2. 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 Deployment Solution 6.5 and 6.8 PXE Manager and PXE server cleanly?" explains how to do this. There have also been some cases where, after a reinstall, this error persists on some versions of Deployment Solution. Deployment Solution 6.5 Hotfix 2 (build 248) had this issue occur occasionally. If this error persists after reinstalling, you might need to update to the latest release of Deployment Solution as well.
  3. 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.
  4. 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.

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.


Legacy ID



19677


Article URL http://www.symantec.com/docs/TECH12489


Terms of use for this information are found in Legal Notices