PXE: Error E53

[RuralGeek]

Last week I installed and configured WDS on our MDT server to push images. I thought everything was working correctly as I was able to PXE boot various virtual machines and another laptop. Well today I tried to pxe boot a Optiplex 580 and a Latitude E5500. Both of these have broadcom nics in them. I recieved the dreaded PXE-E53: No boot filename received. I fired up my working virtual machine and checked it, worked right away. I tried with another box that had an intel nic and it worked as well. My Setup: DHCP Server, WDS/MDT Server both on the same vlan but different virtual servers. My clients are all on a seperate vlans. I double checked to make sure that the helper address was added to the client vlans, which it is. I did not do option 66 or 67 on the DHCP server. I updated the bios on both the failing clients and still no luck. Any ideas as to why intel works and broadcom isn't? Am I missing a driver somewhere? Thank you for any help.

[newpersn]

Are you running any vlans?

 

Scrap that.....

 

Have you checked each dns/dhcp servers on each vlan?

Edited February 28, 2014 by newpersn

[RuralGeek]

I checked on this first thing this morning. Each Vlan has two ip helper addresses. One for DHCP/DNS, and the other for WDS/MDT.

[RuralGeek]

Ok so on a whim - I added option 66 and 67. Magically the laptop with the Broadcom card works now. I then checked my virtual machine and a laptop with intel nic- no go. It wanted me to hit F12 again (which the Broadcom didn't) and when I do, I received- File:\boot\bcd, Error Code 0x00000F. This is getting weird

[mp42871]

Did you ever find a solution to this issue? I am having the exact same problem!