I suggest you to update BIOS to the latest available release.
If the problem persists I think the best you should monitor the network traffic with Wireshark and see which phase of DHCP protocol fails.
I probably should have mentioned that we have checked the bios and all related firmware (including the on-board Intel LAN chip). These units are all up to date with regards to that, we have also restarted the inventory service as well. Unfortunately nothing so far has cleared the problem. As mentioned previously the really wierd part is we can connect another newer Lenovo model right next to this one so it's running off the same switch (and in fact have tried several different switch ports), the newer one will always PXE boot whilst this particular model will not. We have even tried three other units of the same model / type with the same results.
Lenovo no longer supports the model so we can't get anything further from them.
Looks like we'll have to let this one go with no resolution. We can at least manually image the model using Acronis so at least that's something.
Cheers and thanks for the pointers.
Are you getting any type of error? Or it just wont get an address?
During the PXE boot we see the normal startup splash and the the following error:
"PXE-E51: No DHCP or proxyDHCP offers were received
PXE-M0F: Exiting Intel Boot Agent"
The only item we have been scratching our heads about is that these units on the PXE screen show "Intel Base-Code PXE-2.1 (build 083):" which is a older version of the PXE boot code from what I've been able to research, however since the LAN and Boot PROM are embedded the Intel firmware update utilities won't allow you to update it.
If this works on other system models it has to be (99% likely) drivers. After you added your drivers did you re-deploy your pxe rep? Did you get the drivers from the vendor. Not Dell or Microsoft. The actual HW mfg.
You may be misunderstanding here or I'm confused. The error is before the client even sees the image and is still whilst the hardware PXE boot is working so I'm not sure where the drivers would come into play...!!
It's not a driver problem. Drivers are used only at PE time.
The only way you can tune PXE proxy is using c:\program files\landesk\pxe\system\pxeconfig.exe in your PXE Rep.
I often disable multicast to avoid compatibility issues.
I always think that sniffing dhcp request and offer would be helpful.
I'm facing a similar problem. I can get any machine to boot from PXE off my switch except for optiplex 755's. However, 755's boot flawlessly on other switches. The switch I am wanting to boot from is slower is the only difference that I can find, however if I boot into XP I'm able to access the network just fine.
Switching to a faster switch may help your problem, but I'm baffled as to why it can't at least get an IP address.
Any other tips would be helpful. I am a student so I may not have access to the PXE rep unless I have good reason to make a change.
If you are having problems booting on just one switch, but that machine can PXE boot on another switch, then the problem is most likely related to the switch.
1. Make sure that the PXE Rep for that subnet is available on the switch. Keep in mind that the PXE DHCP requests a client makes are broadcast and will not be forwarded to another subnet.
2. Check out this list of ports used by LANDesk. Specifically, the ports related to PXE. http://community.landesk.com/support/docs/DOC-1591 make sure these ports are open on the switch in question.
Hope this helps.
I too was going to suggest that you ensure you hav a pxe rep on that subnet and that it is accessible.
I am also having this issue with older models of Dell Optiplex machines. The Optiplex GX150 will never obtain an IP address. The Optiplex GX270 works perfectly. Both machines are on the same subnet (I even plugged the 150 directly into the switch port my 270 was using to test), the 150 has the latest bios, tried different network cables, etc. Dell's support was non existent for this error.
I suspect there's something on the network card that is not playing nice with DHCP. I'm going to try putting a different network card in the machine and seeing if that might fix the issue. Recommend you try it too. If it works, then you know the issue is with the network card, and you will have to resort to primitive methods of imaging those units rather than using the higher evolved LANDesk. Good luck.
you got the same PXE error as Matt said or do you got a other message?
How many memory do your GX150 clients have? You need more than the doubled size of the PE image (512MB is enough)
We've some PXE problems with older Notebooks too, which got a new additional 512MB RAM module. They can't boot. After we plug off the second module, PXE works... (2x512MB, two different manufacturers...)
Yes, we get the same error, PXE-E51. It has nothing to do with the image size, since there is no image yet. I was trying to capture an image from this machine, but it never resolves an IP address so it can find the PXE rep.
The real solution would be to trash the machines and get fresh ones, but that's up to our PC manager, and the way she operates, it's likely not going to happen. There's only so much training you can do on a P3 933 256MB RAM system (XP + LANDesk + SEP11 + Office 2007 generates constant virtual memory errors). But that's a whole other discussion for a entirely different community.