we've had a problem with our PXE boot. (LD 8.7 SP5)
After switching our network hardware our PXE boot didn't work for newer client hardware. The new hardware (for example Dell OptiPlex 320, 330; Latitude D630/631, E6xxx, with Broadcom UNDI PXE-2.1 v2.1.0) got the message:
CLIENT MAC ADDR: xx xx xx xx xx xx GUID: xxxxxxxx xxxx xxxx xxxx xxxxxxxxxxxx
PXE-E53: No boot filename received
PXE-M0F: Exiting Broadcom PXE ROM.
All hardware with an other PXE ROM (for example Dell OptiPlex GX520, Latitude D600, Broadcom UNDI PXE-2.1 v8.1.8) can boot...
We checked all settings on PXE server, but nothing is changed. We checked the eventlog on the PXE and found a issue with the inventory scan.
So we checked the core... no error scans after network change... mmh that's not possible :-)
So check if the inventory service is running and ... No, the inventory service is stopped (why? We've rebooted the core after network change...)
Restart of the inventory service and now we can boot our newer hardware with PXE too, no error messages. . . (Why?)
I tested it again, stop the service manually and try network boot with two different clients (GX 520, 320). The older one got the PXE menu the newer got the error message.
- Why do we need the inventory service on core be started for some hardware to start PXE boot?
- Why doesn't it happen for all hardware types?
- Does the PXE server communicate in a very early phase of PXE boot with the core and why?
- Why do we haven't this problem with the older DOS based method?