Ghost Solution Suite

 View Only
  • 1.  PXE E55 proxyDHCP

    Posted Nov 27, 2016 09:50 AM

    Hello everyone,
    I am encountering some issues with the network boot in one of our servers.
    I use windows server 2003, on this server i have 3Com TFTP Server(TFTPCTRL.EXE), DHCP server and Symantec GhostCast Server 7.5 - we use this same configuration on other servers and do not encounter PXE-E55 error, i have tried to compare an error in configs without succes.

    DHCP options are:
    003 : Router
    004: Time server
    006: DNS server
    012: Host name
    013: Boot file size
    046: WINS/NBT Node type
    066: Boot server host name
    067: Bootfile name

    Client gets an ip adress after booting from PXE, also mask and DHCP ip is shown but afterwards PXE-E55 appears.



  • 2.  RE: PXE E55 proxyDHCP

    Posted Nov 27, 2016 09:56 AM

    <SEE ABOVE>



  • 3.  RE: PXE E55 proxyDHCP
    Best Answer

    Posted Nov 28, 2016 08:11 AM

    Check port 4011 is open on any firewall involved.

    Check there are no other PXE servers on the subnet that may be responding too.



  • 4.  RE: PXE E55 proxyDHCP

    Posted Nov 28, 2016 11:35 AM

    Hello andykn101, thank you for the answer.

    We got no other PXE servers on the subnet.

    Port 4011 is open on our router. On symantec endpoint protection console i did not see anything in logs, however i have uninstalled SEP completly.

    Still the same message appears, PXE-E55 Proxy DHCP



  • 5.  RE: PXE E55 proxyDHCP

    Posted Dec 01, 2016 01:14 PM

    Are the DHCP requests being forwarded to the PXE server?



  • 6.  RE: PXE E55 proxyDHCP
    Best Answer

    Posted Dec 20, 2016 04:53 PM

    PXE-E55 error "No Boot File Name Received", 99% of the time has to do with the configuration of scope options on the dhcp server and or port 4011 not being open.

    I.P. Helpers make the process of PXE booting across Vlan's much easier than manually assigning scope options. If you have a managed router/switch you should have access to I.P. helpers.

    See Microsofts Article for microsoft documentation on the matter.