إضغط لتفاصيل الإعلانات



Results 1 to 3 of 3
Share
  1. #1
    Join Date
    Jan 2008
    Location
    Egypt
    Posts
    3,946
    Blog Entries
    1
    Rep Power
    16

    Smile how you can solve Error: PXE-E53: No boot filename received....????

    when you get this error message....




    so the cause of the problem and solution is here

    Problem


    When a client computer is trying to boot to PXE, it receives the following error message:
    PXE-E53: No boot filename received
    PXE-M0F: Exiting Intel PXE Rom.




    Environment


    All versions of Deployment Server.
    Clients are PXE booting.


    Cause


    The main root cause to this issue is that the client computer is trying to PXE boot and, after it makes a DHCP request, it is expecting the Altiris PXE boot menu. If the client computer does not hear back anything from the Altiris PXE server, and does not receive a boot menu, it will show this error. There are a variety of reasons that can cause this to happen. The following is a list of known causes:
    1. After upgrading to DS 6.8 SP2, the "Disable Initial Deployment" box is checked which stops new computers from being able to receive the PXE boot menu.
    2. If the error is occurring in DS 6.9, there is an option in PXE configuration under the DS tab to only PXE boot computers that have DS jobs assigned. If this option is checked computers with no DS job scheduled will get this error if attempting to PXE boot.
    3. The Altiris PXE server service is not running. Either this service failed to start up when the computer first booted, or it started up, and then stopped soon afterwards.
    4. The network infrastructure is not configured properly for the Altiris PXE server to see DHCP requests from the client computers and respond back with the PXE boot menu. This could be caused by the network devices (such as routers and switches) not properly forwarding DHCP broadcast request and response packets between client and PXE server.
    5. The DHCP server scope option 060 has either been set or is not set correctly on the DHCP server. This option is used to inform a client computer where the PXE server resides so that it knows who to contact to make subsequent PXE requests.
    6. Some other program or service on the PXE server is using ports 67, 68, or 4011 and is preventing the Altiris PXE Server from listening on those ports
    7. The PXE server is responding either too quickly, or too slowly for the client computer to receive and understand the response.
    8. The client computer is a pre-PXE 2.0 compliant system and is receiving a corrupted BSTRAP.0 file.
    9. PXE MAC Filtering is enabled.
    10. The installation of the Altiris PXE Server was somehow corrupted, and it is seeing the DHCP requests from the client, but it is either not responding, or is creating an invalid response.
    11. The Windows Firewall, on either the server or the workstation, is not allowing PXE communications.




    Solution



    1. Getting the "PXE-E53: No boot filename received" after upgrading to DS 6.8 SP2. If you can reimage computers already in the Deployment Console, but get new computers to get the PXE boot menu, make sure that the PXE Configuration Utilities' DS tab has the "Disable Initial Deployment" unchecked. If this is checked, the configuration stops new computers that are not already in the database from being able to receive the PXE boot menu. See article 37671.
    2. In PXE configuration under the DS tab, uncheck the box to only PXE boot computers that have a DS job scheduled.
    3. PXE Server Service not running: If the Altiris PXE Server service is not running, start the service up and make sure that it stays running. Verify that the service account has sufficient rights to run the service (it should be set to "Local System"). If the service starts and then stops check the system event logs for more information on why the service is stopping. The PXE installation might be corrupt, and the PXE server might need to be reinstalled if the service will not start or stay running.
    4. Network Infrastructure: Take a computer that is already on the same subnet or VLAN as the PXE server and boot that computer with PXE (if the computers that you are getting the error message are on a different subnet or VLAN) and see if you still get the same error message on that computer. If the computers on the local subnet (or on the same subnet/VLAN as the PXE server)successfully PXE boot, then the issue is being caused by the network infrastructure not properly forwarding DHCP request packets to the PXE server. Most routers in a network will forward DHCP request packets to the DHCP server, however they are not set up by default to forward these same packets to a PXE server (but the PXE server needs to see these packets to respond).

      Cisco routers can use IP helpers to forward these packets to the PXE server. To do this, simply enter the command: ip helper-address xxx.xxx.xxx.xxx, (where xxx.xxx.xxx.xxx represents the IP address of of the computer where the broadcasts should be forwarded to. This command needs to be placed on the device (router, switch or bridge) interface on where the broadcast is received. For information on this, see article 20051.
      If after adding correct IP helpers to forward DHCP request packets to the PXE server the issue is not resolved, and all other steps taken to resolve the issue have not helped out, run an Ethereal network trace on the PXE server filtering with the filter "bootp". For more information on how to run network traces of a PXE boot see article 1393.
    5. Incorrect setting of DHCP scope option 060: If the PXE server and DHCP server are on the same physical computer, DHCP option 60 needs to be set to "PXEClient", if those two components are on different computers, in most circumstances option 060 needs to not be set on the DHCP server. Make sure, however, that your environment is set up that you have DHCP option 060 set correctly. See article 17347 for more information.
    6. Another program using PXE ports: If another program is using the ports 67, 68, or 4011 the Altiris PXE Server will not be able to listen on those ports and will not respond. You will need to remove, disable, or reconfigure the offending program to not use those ports. You can determine if there is another program using those ports by first turning off all Altiris PXE Server services, and then running from a command line the following

      netstat -an

      This command will show a full list of all programs and services that are using a network connection. It will also list the ports that each of these programs are using. Go through this list and see if there are any that are using ports 67, 68, or 4011 while the PXE services are not running. If any are found these need to be removed or corrected.
    7. PXE responding too slowly: Open the PXE Configuration Utility and select the "PXE Server" tab on Deployment Solution 6.5, and "General" on previous versions. The following screenshot is from PXE 6.5.



      The response time on this will need to be changed based on your environment. Try setting this to a Delayed response, or if it is already delayed try setting this to a short delayed response.
    8. BSTRAP.0 file was not created correctly: If your client computers are using PXE 1.0 (they will show this when they are first booting), and the issue first started occurring after making a change to the PXE boot menu (such as adding a new menu option). The problem could be because the BSTRAP.0 file has been corrupted. Almost all client computers since 2001 are PXE 2.0 compliant, so this cause is fairly rare. When this happens the file will not be correctly recreated unless the PXE server is reinstalled.
    9. PXE MAC Filtering is enabled. Check PXE Configuration > MAC Filter tab and disable all filtering or edit configuration to include/exclude necessary MAC addresses.
    10. PXE Server installation is corrupt: If all of the above steps to resolution have not fixed this issue, most likely the cause is a bad installation of the Altiris PXE Server. It is recommended in this circumstance to reinstall your PXE Server. Please refer article 3724 for complete list of steps to uninstall and reinstall a Deployment Solution 6.5 PXE Server.
    11. Create firewall exceptions for Altiris communications by using Administrator Tools > Windows Firewall > Add Program File and browse to eXpress Share > PXE folder. Add PXE.exe, PXEManager.exe, PXE MTFTP.exe to the exception list.
    12. Possible corruption of the pxe.ini file. Stop the PXE Config Helper Service, delete the existing pxe.ini, and the restart the service.
    13. If a network trace is needed to troubleshoot this further, see article 1393 for PXE-WireShark network trace step-by-step instructions.
    14. See article 28035, "PXE forced Mode."

    Legacy ID 17383


    Source: symantec.com/business/support/index?page=content&id=TECH10532

    thanks....
    Last edited by Mohamed Fouad; 21-01-2012 at 09:45 PM. Reason: add content of the link

    MCP,MCSA,MCSE
    ACE,ICDL
    ******
    يا قارئ خطى لا تبكى على موتى
    ******
    فاليوم انا معك وغدا فى التراب فان عشت فانى معك وان مت فللذكرى
    ******

    من مواضيع hopy_braya :



  2. Facebook Comments - تعليقـك على الفيس بوك يسعدنا ويطور مجهوداتنـا


  3. Forum Ads:

  4. Forum Ads:

    اضفط هنا لمعرفة تفاصيل الإعلانات بالموقع


  5. Forum Ads:

    -->

  6. #2
    Join Date
    May 2010
    Location
    Mansoura, Egypt
    Posts
    311
    Rep Power
    11

  7. #3
    Join Date
    Jan 2008
    Location
    Egypt
    Posts
    3,946
    Blog Entries
    1
    Rep Power
    16

  8. Forum Ads:

Similar Threads

  1. Replies: 0
    Last Post: 20-06-2011, 01:59 PM
  2. Replies: 0
    Last Post: 23-11-2010, 05:41 PM
  3. ISA 2004 Error
    By ahmed_desoki in forum Microsoft
    Replies: 6
    Last Post: 14-03-2009, 01:01 PM
  4. Please Solve this problem
    By hopy_braya in forum Engineers discussions
    Replies: 2
    Last Post: 25-10-2008, 11:12 PM
  5. Can You Solve it !!!!!!!!!!!!!!!!!!!!
    By redheart in forum Engineers discussions
    Replies: 5
    Last Post: 31-05-2008, 08:36 PM

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  

أقسام المنتدى

الروابط النصية

تابع جروبنا على الفيس بوك

صفحة Egypt Engineers على الفيس بوك

تابعنا على linkedin

جروبنا على الياهو جروب