+ Post New Thread
Results 1 to 12 of 12
Windows Thread, PXE Broke... in Technical; I suddenly started getting the following error when trying to use PXE. DHCP works fine in Windows. PXE-E51: No DHCP ...
  1. #1
    mrforgetful's Avatar
    Join Date
    May 2006
    Posts
    1,637
    Thank Post
    7
    Thanked 15 Times in 15 Posts
    Rep Power
    22

    PXE Broke...

    I suddenly started getting the following error when trying to use PXE. DHCP works fine in Windows.

    PXE-E51: No DHCP or proxyDHCP

    Now WINS got disabled last week but was reenabled again to fix a different issue. I don't know if this is related in any way.

    I've searched all over Google and Experts Exchange to no avail....any ideas?

  2. #2
    Oops_my_bad's Avatar
    Join Date
    Jan 2007
    Location
    Man chest hair
    Posts
    1,738
    Thank Post
    438
    Thanked 53 Times in 50 Posts
    Rep Power
    30
    What are you using with PXE?

  3. #3
    contink's Avatar
    Join Date
    Jul 2006
    Location
    South Yorkshire
    Posts
    3,791
    Thank Post
    303
    Thanked 327 Times in 233 Posts
    Rep Power
    118
    Have you tried restarting the DHCP service as well as running the RIS check?

  4. #4
    mrforgetful's Avatar
    Join Date
    May 2006
    Posts
    1,637
    Thank Post
    7
    Thanked 15 Times in 15 Posts
    Rep Power
    22
    RIS, or rather WDS in legacy mode in order to load the Ghost Boot Image.

  5. #5
    mrforgetful's Avatar
    Join Date
    May 2006
    Posts
    1,637
    Thank Post
    7
    Thanked 15 Times in 15 Posts
    Rep Power
    22
    Yeh, I've rebooted all my servers and my Core Switch, checked the Automatic services and they're all started.

  6. #6

    Join Date
    Sep 2006
    Location
    West Midlands
    Posts
    410
    Thank Post
    73
    Thanked 75 Times in 58 Posts
    Rep Power
    44
    From What Are The PXE Error Codes?

    PXE-E51: No DHCP or proxyDHCP offers were received. The client did not receive any valid DHCP, BOOTP or proxyDHCP offers. To resolve this issue, check each of the following network configuration items:
    • DHCP services are not available on the network to which the PXE-enabled NIC is connected.
    • A DHCP proxy or IP helper address is not configured for the subnet on which the PXE client is connected.
    • The switch port connected to the PXE NIC is running Spanning Tree Protocol, EtherChannel Protocol, or Port Aggregation Protocol and is thus not activated immediately when a link is detected. This forces the DHCP request from the PXE client to timeout.
    • DHCP is available on the network, but PXE is not.
    • The network cable is not attached to the PXE-enabled NIC on the target server.


    ...and just a thought, but does the server have a firewall enabled?

    mb

  7. #7
    DSapseid's Avatar
    Join Date
    Feb 2007
    Location
    West Sussex
    Posts
    1,152
    Thank Post
    130
    Thanked 54 Times in 47 Posts
    Rep Power
    38
    MY pxe server has 2 network cards on it an i have to disable one if i want to pxe boot for RIS.

  8. #8
    mrforgetful's Avatar
    Join Date
    May 2006
    Posts
    1,637
    Thank Post
    7
    Thanked 15 Times in 15 Posts
    Rep Power
    22
    DHCP must be enabled as all the computers work fine except for the PXE booting.
    Where would I check the DHCP Proxy IP Helper settings?
    The switch doesn't have STP enabled, the Core switch does but always has and even if I disable it (which I just tried) it does not fix the problem.
    It was enabled fine on Friday morning!

    No firewall enabled.

    For some reason Shuttle computers are giving a different error.

    PXE-T01 File Not Found
    PXE-E3B TFTP Error - File Not Found

  9. #9

    Join Date
    Mar 2008
    Location
    California
    Posts
    1
    Thank Post
    0
    Thanked 0 Times in 0 Posts
    Rep Power
    0
    Quote Originally Posted by mrforgetful View Post
    For some reason Shuttle computers are giving a different error.

    PXE-T01 File Not Found
    PXE-E3B TFTP Error - File Not Found
    Hmmm.... doesn't make much sense why you'd see two different responses unless there was a PXEClass there based on the MAC.

    Given how improbable this is I would say your TFTP server is missing a file that was once there. If you're using RIS this file would be OSchooser\i386\startrom.com. If you're using pxelinux obviously this would be pxelinux.0.

    I would verify this directory structure and file(s) are present in your TFTP server's root/boot directory.

    Other than that double-check your DHCP config for the proper boot server hostname/IP address (option 66) and check the boot filename (option 67).

    Another possibility is that a second TFTP server is running on the same server (assuming your boot server name is as it should be) and using a different TFTP server. Shutdown your main TFTP server and do a netstat for port 69 UDP open to see if you still TFTP open even after it is supposedly shut down.

    If the DHCP boot server specification and boot filenames/directory structure is there as it should be the only other possibility I can think of is you're getting IPs from a subnet you do not expect and thus possibly getting unexpected PXE responses. Of course you can tell what IP you're getting when you boot via PXE.

    If all this fails and if you really want to tell what's going on setup Wireshark on your RIS/TFTP server and watch the TFTP traffic when PXE booting. You'll get a very sure and clear idea of what boot file the PXE client is requesting. More importantly if you see no TFTP traffic you definitely know then that something is wrong with your DHCP setup.

    And if you're dead sure you do not have spanning-tree/etherchannel enabled on your ports the first error might point to an exhaustion of the DHCP IP pool space though if see the error above (PXE-T01 File Not Found) definitely points to DHCP working - unless the working piece is intermittent.
    Last edited by boethius; 4th March 2008 at 02:36 AM.

  10. #10
    mrforgetful's Avatar
    Join Date
    May 2006
    Posts
    1,637
    Thank Post
    7
    Thanked 15 Times in 15 Posts
    Rep Power
    22
    I've no idea what it was but all iws working again this morning....

    The last thing I tried last night was recreating the RIS options using Ghost, so this morning I tried again and it all worked.

    Thanks for all the suggestions.

  11. #11
    adamchapman's Avatar
    Join Date
    Aug 2007
    Location
    North Lincolnshire
    Posts
    187
    Thank Post
    29
    Thanked 14 Times in 14 Posts
    Rep Power
    17
    I'm getting the same error... But only on about 10 machines!!!

    I've successfully imaged 250 using WDS, but these 10 just will not work!!

    I've tried removing the reservations from DHCP to see if there was an issue there.
    PXE-51 no DHCP or proxy DHCP offers were received.

    any advice - things to check?

  12. #12

    Join Date
    Sep 2006
    Location
    West Midlands
    Posts
    410
    Thank Post
    73
    Thanked 75 Times in 58 Posts
    Rep Power
    44
    The first thing that you must ask is what is different about those 10 machines (compared to the other 250)?

    Are they identical hardware?
    Are they on the same subnet?
    Are they connected to a different switch?
    etc.

    Try plugging one of the 10 into a port originally used by one the successfull 250 and try again!

    mb

SHARE:
+ Post New Thread

Similar Threads

  1. [CLOSED] Bug/Error: You broke my google reader... grrr ;)
    By Scruff in forum EduGeek.net Site Problems
    Replies: 5
    Last Post: 15th January 2008, 04:34 PM
  2. ajax broke?!
    By browolf in forum Windows
    Replies: 4
    Last Post: 18th April 2007, 01:33 PM
  3. delprof broke java HELP
    By spacemanvic in forum Windows
    Replies: 7
    Last Post: 14th December 2006, 10:58 PM

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

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