<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: pxe-e55 proxydhcp service did not reply to request on port 4011 in Operating System - Microsoft</title>
    <link>https://community.hpe.com/t5/operating-system-microsoft/pxe-e55-proxydhcp-service-did-not-reply-to-request-on-port-4011/m-p/6764292#M12756</link>
    <description>&lt;P&gt;I realise this is a very old thread but as we had the same problem recently and it wasn't fixed by any&amp;nbsp;of the fixes posted on this or&amp;nbsp;the altiris forums (which are locked now anyway, so can't be updated) I though I'd post our fix here in case it helps anyone else.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Somehow we got the error PXE-E55 after regenerating our PXE images after adding additional drivers. After a lot of dead ends it turned out that the configuration file 'pxe.ini' had updated itself&amp;nbsp;somehow using the wrong IP.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We have all this running from one maching (Deployment Services, PXE, DHCP for the PXE boot network) but the machine is multi-homed&amp;nbsp;and&amp;nbsp;PXE had replaced all instances of the correct IP in the above config file&amp;nbsp;with a different IP on the same server (but that has nothing to do with PXE or &amp;nbsp;DHCP etc). It's never done it before so no idea why it did it that time.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;So basically while the server was listening for and responding to DHCP requests on the correct network, it was then listening to requests for the boot image location on a different (wrong) network. This could be checked by &amp;lt;netstat -a -p UDP | findstr "4011"&amp;gt; which confirmed that the server was listening on port 4011 but on the wrong network.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;After correcting this, and possibly restarting PXE services,&amp;nbsp;all worked as expected.&lt;/P&gt;</description>
    <pubDate>Mon, 13 Jul 2015 13:40:20 GMT</pubDate>
    <dc:creator>zeroagemain</dc:creator>
    <dc:date>2015-07-13T13:40:20Z</dc:date>
    <item>
      <title>pxe-e55 proxydhcp service did not reply to request on port 4011</title>
      <link>https://community.hpe.com/t5/operating-system-microsoft/pxe-e55-proxydhcp-service-did-not-reply-to-request-on-port-4011/m-p/5309513#M12755</link>
      <description>&lt;DIV&gt;&lt;DIV&gt;&lt;P&gt;I am having problems&amp;nbsp;with this error.&amp;nbsp;&lt;STRONG&gt;pxe-e55 proxydhcp service did not reply to request on port 4011.&amp;nbsp; &lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;This is Deployment Server 6.9 SP5 running on Windows 2008.&amp;nbsp; The DHCP server gives me an IP.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;When running Deployment Server 6.9 SP2&amp;nbsp;on Windows 2003,&amp;nbsp;the same Blade and&amp;nbsp; IP, I had no problems.&lt;/P&gt;&lt;P&gt;It was not upgraded, it was a clean install&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have done the following.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;1- Added port 4011 and 402 to the Windows 2008 Firewall - rebooted server&lt;/P&gt;&lt;P&gt;2- Disabled the Firewall - rebooted server&lt;/P&gt;&lt;P&gt;3- Checked the PXE.ini to make sure it was correct&lt;/P&gt;&lt;P&gt;4- Checked the PXE Configuration and all is good&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Any help would be appreciated.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Cheers,&lt;/P&gt;&lt;P&gt;Terry&lt;/P&gt;&lt;/DIV&gt;&lt;/DIV&gt;</description>
      <pubDate>Tue, 23 Aug 2011 11:46:20 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-microsoft/pxe-e55-proxydhcp-service-did-not-reply-to-request-on-port-4011/m-p/5309513#M12755</guid>
      <dc:creator>TConn</dc:creator>
      <dc:date>2011-08-23T11:46:20Z</dc:date>
    </item>
    <item>
      <title>Re: pxe-e55 proxydhcp service did not reply to request on port 4011</title>
      <link>https://community.hpe.com/t5/operating-system-microsoft/pxe-e55-proxydhcp-service-did-not-reply-to-request-on-port-4011/m-p/6764292#M12756</link>
      <description>&lt;P&gt;I realise this is a very old thread but as we had the same problem recently and it wasn't fixed by any&amp;nbsp;of the fixes posted on this or&amp;nbsp;the altiris forums (which are locked now anyway, so can't be updated) I though I'd post our fix here in case it helps anyone else.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Somehow we got the error PXE-E55 after regenerating our PXE images after adding additional drivers. After a lot of dead ends it turned out that the configuration file 'pxe.ini' had updated itself&amp;nbsp;somehow using the wrong IP.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We have all this running from one maching (Deployment Services, PXE, DHCP for the PXE boot network) but the machine is multi-homed&amp;nbsp;and&amp;nbsp;PXE had replaced all instances of the correct IP in the above config file&amp;nbsp;with a different IP on the same server (but that has nothing to do with PXE or &amp;nbsp;DHCP etc). It's never done it before so no idea why it did it that time.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;So basically while the server was listening for and responding to DHCP requests on the correct network, it was then listening to requests for the boot image location on a different (wrong) network. This could be checked by &amp;lt;netstat -a -p UDP | findstr "4011"&amp;gt; which confirmed that the server was listening on port 4011 but on the wrong network.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;After correcting this, and possibly restarting PXE services,&amp;nbsp;all worked as expected.&lt;/P&gt;</description>
      <pubDate>Mon, 13 Jul 2015 13:40:20 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-microsoft/pxe-e55-proxydhcp-service-did-not-reply-to-request-on-port-4011/m-p/6764292#M12756</guid>
      <dc:creator>zeroagemain</dc:creator>
      <dc:date>2015-07-13T13:40:20Z</dc:date>
    </item>
  </channel>
</rss>

