PXE error 53?

[andyturpie]

Morning,

 

We brought in a fleet of Tosh C50-A laptops a couple of years ago and we have noticed all of a sudden that a few of them have ceased to PXE boot with the old E53 message. I know that all are identical specs and all were actually built onto our network by PXE boot. I took one laptop stripped all the hardware out (that was removable) and tested, still the same. I built this machine from an OS disk and installed the LAN driver - worked fine.

 

Just wondering if there is anything DNS or IP address related which can cause this error?

 

Any ideas?

 

TIA Andy T

[sted]

i seem to remember those being a total pita to image with pxe booting i THINK you needed to explicit state the boot file/server in dhcp option 66 iirc or bios updating them may help

[Norphy]

Are other PCs on the same network segment building properly?

 

Option 60/66/67 should not be used unless WDS and DHCP are sharing a server.

[sted]

Are other PCs on the same network segment building properly?

 

Option 60/66/67 should not be used unless WDS and DHCP are sharing a server.

66 can be used to stop rogue pxe servers being used on the network 60/67 need altering for wds 66 as far as i remember is nothing to do with it

[chazzy2501]

I've had this with various machines over the years. It's WDS being a pain, stop the service and delete the db. you'll start working again with the pending device id's starting at 1 again.

 

VERY SUPER rare (like twice in a decade) it's been a bad gigabit port (one of the pair damaged so it can't work at a gigabit but can at 100 but doesn't PXE gets maddd)

[dapaulio]

I bought 12 of the original one before Toshiba decide to rerelease the c50. We had no reason to doubt Toshiba as we have had many of the C850 before them and image deployment was no bother.

The only work around we found was specifying the 66/67 option within DHCP under the vlan you use to deploy the image

66: IP address of your WDS server

67: boot\x86\wdsnbp.com

 

We also had to put an IP helper within the VLAN on our HP core switch pointing to the wds server.

 

these can be enabled and disabled whenever you require them if you are security conscious

hope this helps

 

EDIT: I assume you have also disabled secure boot and enabled legacy boot within the c50 BIOS

 

2nd EDIT realised that you must have done to actually get the PXE E53 error

Edited May 17, 2016 by dapaulio

[andyturpie]

Morning all, I have got this troublesome laptop top built, it even failed with a CC4 build disk at first (CD ISO) - I removed the driver and reimported the driver (same version) back in and it could then build possibly a corrupted driver. However, as I have witnessed the 53 error on only a handful of laptops I am starting to believe that it may be the database playing up, so will wait until the next laptop gives me grief then try some of the suggestions above