Go Premium for a chance to win a PS4. Enter to Win

x
?
Solved

Dell Optiplex 7010 not booting WDS server.

Posted on 2013-11-22
1
Medium Priority
?
3,001 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 1600 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

[Webinar] Cloud Security

In this webinar you will learn:

-Why existing firewall and DMZ architectures are not suited for securing cloud applications
-How to make your enterprise “Cloud Ready”, and fix your aging DMZ architecture
-How to transform your enterprise and become a Cloud Enabler

Question has a verified solution.

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

Remote Apps is a feature in server 2008 which allows users to run applications off Remote Desktop Servers without having to log into them to run the applications.  The user can either have a desktop shortcut installed or go through the web portal to…
Citrix XenApp, Internet Explorer 11 set to Enterprise Mode and using central hosted sites.xml file.
In this video, we discuss why the need for additional vertical screen space has become more important in recent years, namely, due to the transition in the marketplace of 4x3 computer screens to 16x9 and 16x10 screens (so-called widescreen format). …
Windows 8 came with a dramatically different user interface known as Metro. Notably missing from that interface was a Start button and Start Menu. Microsoft responded to negative user feedback of the Metro interface, bringing back the Start button a…
Suggested Courses

963 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