Solved

Dell Optiplex 7010 not booting WDS server.

Posted on 2013-11-22
1
2,785 Views
Last Modified: 2016-11-23
Hi

I've just set up WDS on a clean VM. Carefully followed instruction to do so.

For some reason I can't get our fleet of Dell Optiplex 7010 units to talk to the WDS server. I know it's not the server as I can successfully boot to it from a Toshiba laptop.

When booting from the NIC I get error " PXE-E51 - No DHCP or proxyDHCP offers were received"

Has any experienced this issues. Please ask for more details if needed.
0
Comment
Question by:smiffy07
1 Comment
 
LVL 3

Accepted Solution

by:
1md earned 400 total points
ID: 39668545
Hello,

There is a Technet article with some ideas that might help you here:

http://social.technet.microsoft.com/Forums/en-US/d06413a4-af2b-4736-a510-c0a68eb880cf/cannot-get-certain-machines-to-pxe-boot?forum=mdt

PXE-E51 errors take place before any booting of WIMs occurs. There should be no OS drivers, it's strictly between the card firmware and the PXE server. It is most likely some type of network problem.Usually no IP helper, or the WDS service is stopped.

If it is truly PC-specific, that is some PCs boot, while others don't on the same subnet, that is very odd. I had 790's and E6420's that wouldn't PXE boot on 1 gb segments, but were fine on 100 mbit. That was resolved by a BIOS upgrade. Are you sure the network folks haven't changed something on the network without telling you?

• PXE-E51: No DHCP or proxyDHCP offers were received.
The client did not receive any valid DHCP, BOOTP or proxyDHCP offers. To resolve this issue, check each of the following network configuration items:

•      DHCP services are not available on the network to which the PXE-enabled NIC is connected.
•      A DHCP proxy or IP helper address is not configured for the subnet on which the PXE client is connected.
•      The switch port connected to the PXE NIC is running Spanning Tree Protocol, EtherChannel Protocol, or Port Aggregation Protocol and is thus not activated immediately when a link is detected. This forces the DHCP request from the PXE client to timeout.
•      DHCP is available on the network, but PXE is not.
•      The network cable is not attached to the PXE-enabled NIC on the target server.
0

Featured Post

NAS Cloud Backup Strategies

This article explains backup scenarios when using network storage. We review the so-called “3-2-1 strategy” and summarize the methods you can use to send NAS data to the cloud

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Welcome to my series of short tips on migrations. Whilst based on Microsoft migrations the same principles can be applied to any type of migration. My first tip Migration Tip #1 – Source Server Health can be found listed in my profile here: http:…
Many admins will agree: WSUS is is a nice invention but using it on the client side when updating a newly installed computer is still time consuming as you have to do several reboots and furthermore, the procedure of installing updates, rebooting an…
Windows 8 comes with a dramatically different user interface known as Metro. Notably missing from the new interface is a Start button and Start Menu. Many users do not like it, much preferring the interface of earlier versions — Windows 7, Windows X…
With the advent of Windows 10, Microsoft is pushing a Get Windows 10 icon into the notification area (system tray) of qualifying computers. There are many reasons for wanting to remove this icon. This two-part Experts Exchange video Micro Tutorial s…

839 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question