PXE 053 error

pts.
Tags:
Hardware
I'd like to how to recover from a PXE error. I've been trying to find the answer to this for months, but get nowhere. When I try to boot up my system, I get a PXE 053 error. Used to be, with this erratic problem I could disconnect the router from the box and it'd start up. However, for the last 6 days, I've not been able to get it to do anything. First, my system: WinXP Home dual processor 733/133 40 GB C drive, 80 GB D drive 512 meg RAM The machine is about 6 years old. It appears that neither the CD, floppy nor hard drive are being seen at the initial startup. It goes through an initial POST at which time it sees none of the drives, then starts on some sort of secondary BIOS utility during which time it finds a primary and secondary master. Next, it loads up MBA followed by PXE. It loads PXE then tries to find DHCP, at which time it crashes. I get a PXE 053 "no boot filename received" message, followed by "insert system disk and press enter" message. However, inserting my system disk into the CD has no effect, since the CD apparently is not being seen at this point. It was recommended at another site that I replace the CMOS battery. I did that ... and it had no effect. The hard drive is fine. The cables are all tight and in the right places. This computer has been doing quite well, except for this issue. Prior to this issue, there had been no hardware or software changes.

Answer Wiki

Thanks. We'll let you know when a new response is added.

Did you make a floppy system disk? In Bios, it presents the order of devices it will look for the bootup. This has probably changed due to changing the battery on your Cmos. Typically your computer will return to default CMOS which may not be looking for bootup from your CD drive as you have seen.
Go to Bios and change which drives are looked for for bootup – there is usually a list and order to what devices it looks for. I do not know that particular computer, but F8 or F10 or F1 key usually goto Bios at startup,.

Good luck,
Squid

Discuss This Question: 8  Replies

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
  • Jonesing
    Yes, the previous advice is good. A PXE server sit out on the network and allows PCs to boot up using the PXE option and then obtain bootup instructions from the PXE server. This is sometimes used to tell the PC or thin-client which operating system to boot up or other various access rules. Since you don't have a PXE server at home it hangs looking for it. It is a boot option and will be the first boot "device" to be looked for. It is found in the bios, usually as an option next to the boot order. Either use PXE or Not use PXE. Your choice is to not use it.
    0 pointsBadges:
    report
  • PDMeat
    As was said already, your problem isn't PXE, it's BIOS related most likely. Try flashing the bios to the latest version or the same version if it's the latest. Make sure you have a new CMOS battery. If this doesn't fix your problem, take a good look at your motherboard and make sure nothing is toast (leaking capacitors have been a persistant problem with Dells, ABIT and other mobos). If you can't recognize any drives, that's BIOS. Try going into the BIOS settings an auto-detect the drives there or manually configure it. If you simply cannot recognize the drives no matter what, you may have a BIOS or mobo problem that is very difficult to resolve if not impossible. Call or email the OEM and usually they will get back to you and make some recommendations.
    0 pointsBadges:
    report
  • VenPhil
    I'll add one more piece of advice to those above (with which I concur). Follow Pournelle's Rule, which is: if a computer that has been working well stops working well, check the cables. You've already made sure they are plugged in well, and in the right slots (which is really what Jerry Pournelle is talking about). But perhaps one of the cables is faulty. There is no easy way to check this except for getting new cables. If you follow the above advices and that doesn't solve the problem, try replacing the cables. Good luck. Phil
    0 pointsBadges:
    report
  • Brandonbates
    What model of motherboard or system do you have?
    0 pointsBadges:
    report
  • SunshineGirl
    I agree with all that has been said above. I happen to have an older Compaq that many moons ago was on a vast network. The PXE kept trying to do its thing. Mine didn't completley fail and would go on to the C drive eventually but it was a giant pain. I ended up updating the BIOS and reconfiguring the BIOS area concerning bootup to reflect no PXE and the message - FINALLY - stopped. Good luck dude/dudette.
    0 pointsBadges:
    report
  • Enterprisephil
    as a h/w tech, I can only assume that you are not regularly using any PXE boot right ? 1) If you are then .... Look at Microsoft Knowledge Base Q259670...... "In some environments, you may try to set the following Dynamic Host Configuration Protocol (DHCP) options in order to direct Pre-Boot Execution Environment (PXE) clients to Windows 2000 Remote Installation Services (RIS) servers: a.. #60 = Client Identifier (set to "PXEClient") b.. #66 = Boot Server Host Name c.. #67 = BootFile Name Note: The DHCP option 60 does not appear in the DHCP manager UI, you must add it using Netsh.exe. These options are added to the DHCP scope so that the routers do not have to be updated with the RIS servers IP information. In order for PXE clients to contact RIS servers that are located across routers, the IP address of the RIS servers must be added to the IP helper tables. Using this method, after the PXE client broadcasts to get an IP address, it is directed to the specific RIS server listed in the DHCP scope instead of broadcasting another DHCP DISCOVER to locate a RIS server." Pay particular attention to option #60, as I believe when RIS is installed it expects to be on the same machine as DHCP. You may want to read up this is article which should show you how to use the netsh utility to administer DHCP. 2) OKAY if you are not...and it started this some time back and then you were able to recover but not anymore....would indicate that you have a failing NIC or network cable or adapter. Do you have another Network card or cable ? Pls try either of them alternately. 3)PXE boot is only invoked in the BIOS of the system. So enter the BIOS (press DELETE or F2 or F10 while booting) and look for the NIC (network) settings. Disable PXE or turn PXE off. Check to see if the system can boot to the OS on the reboot now. 4)If all of this is good then the Network card BIOS sometimes can be invoked (if INTEL) by pressing CTRL+S while booting and the NIC card is displayed in the TEXT screen. There should be an option in the NIC BIOS to disable PXE or to assign a system/client. Assign the client if you really have a PXE client. 5) Check if there is a later Firmware for the Network card or later driver for the network card. Install / Upgrade and then check it out. Good luck
    0 pointsBadges:
    report
  • Dnoakes
    The BIOS / CMOS setting for your network card needs to be checked as it got corrupt or reset. It should be set so that it is "on" and nothing else. Not "on w/ PXE" or "On w/ RPL". This will allow the other boot devices to follow through with their "pecking" order.
    0 pointsBadges:
    report
  • Sinait
    PROBLEM SOLVED! It was a bad NIC. Sometimes the simplest things..... Thanks to all who responded...especially those who suggested I check out the NIC!!
    0 pointsBadges:
    report

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Thanks! We'll email you when relevant content is added and updated.

Following