"No DHCP or ProxyDHCP offers recieved"
Can anyone suggest anything? We have 500 odd dells here, all T3400/T3500s. All PXE using MDT 2010 to image on server 2k8r2.
All bar 3 PCs are fine..they boot, they load the matrix point driver for the SAS disks, thehy get to the Broadcom UNDI screen, and..they stop. The others immediately get the "DHCP:.../" spinner, and then ask for f12 if you want to image, followed by kicking into Win7.
These 3 just sit. They don't get the "DHCP.../" for a good 5 minutes, they just sit at "Broadcom UNDI" etc. Then when they do proceed to looking for DHCP, they come up after 30-40 seconds with "PXE-e51: No DHCP or ProxyHCP offers were recieved", and kick into Win7 as usual.
Once in Win7, everything LAN wise is bang on, perfectly happy.
Now, I've flashed to BIOS A16 from A10 (thought it was a red herring, the others are all A10). I've swapped 3 cables/lan sockets from trouble free units of the same type to one of the PITA units, no change..all other units are happy, this one not. Into BIOS, flatten it to defaults, total reset, no joy.
It HAS worked fine, they all have, as they've all been imaged last summer with the Win7 build! Just all of a sudden, these 3 decide enough is enough.
They're all encased, so can't be tampered with except by us, and we haven't. LAN ports and cables also. Switches haven't changed at all since they were installed, and besides, other workstations in the socket, with the same cable are fine.
I'm really leaning towards a damaged bit of hardware..but 3 at once? Don't get me wrong, these Dells aren't the most flawless of machines..but...1 has been in place 3 years, bordering on 4..one is coming up for 18 months, and the 3rd had a new motherboard fitted not 6 months ago, for refusing to connect to the LAN come hell or high water, and upon replacement, worked perfectly until now.
Any thoughts? I'm at a bit of a loss...
Re: "No DHCP or ProxyDHCP offers recieved"
Just use the lightouch.iso in the deploy share to burn a boot CD that takes the place of the pxe boot on those ones. Had this before and the time taken to track down dodgey cables, messed STP settings or broadcast throtteling errors was way longer than just doing those few with a boot CD to kick into the MDT share.