Setting up WDS to PXE boot on server 2003 with DHCP on same server

Posted on 2014-03-03
Last Modified: 2014-03-03
I am trying to set up a WDS server on server 2003 that also has AD, DNS and DHCP configured. It all works when the client connects once in Windows but the server is not providing an IP address over DHCP when booting from the network to PXE boot. I have configured it with the guidelines on the Microsoft website so that WDS does not listen on port 67 and also PXEclient is on port 60 but it does not seem to work. Can anyone help me?
Question by:MSSC_support
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 4
  • 3
LVL 21

Accepted Solution

Radhakrishnan R earned 500 total points
ID: 39900683

By default WDS will use UDP Port 67. But as this is also used by DHCP, a conflict can occur that can stop the DHCP Server service from binding to the network adapter and prevent computers from getting an IP address. This will occur if both services are set to Automatic startup and the server is rebooted. If WDS starts up before DHCP, it will grab port 67 and DHCP will subsequently issue errors such as:

"Error: The DHCP service is not servicing any clients because none of the active network interfaces have statically configured IP addresses, or there are no active interfaces."

If the DHCP Server service starts up before WDS service, then DHCP will use Ports 67 and 68, and WDS will use port 69.

To ensure this situation does not occur set the WDS service to Manual start.

Hope this helps.

Author Comment

ID: 39900726
Ok, I tried that and manually started the WDS service but it still does not receive an IP over PXE. I get the message no DHCP OR proxyDHCP offers were received.
LVL 21

Expert Comment

by:Radhakrishnan R
ID: 39900759
You need to make the service manual, reboot the server, start the service and see it works?
Optimize your web performance

What's in the eBook?
- Full list of reasons for poor performance
- Ultimate measures to speed things up
- Primary web monitoring types
- KPIs you should be monitoring in order to increase your ROI

LVL 21

Expert Comment

by:Radhakrishnan R
ID: 39900770
In addition to my earlier post. Open WDS>>Select the server>>Right click and properties>DHCP>>make sure both options are ticked "Do not listen on port 67" and "Configure DHCP options 60 to indicate that this server is also a PXE server"
LVL 21

Expert Comment

by:Radhakrishnan R
ID: 39900774
Also, make sure that you have added 060 PXEClient in DHCP>>Server Options? String value "PXEClient"

Author Comment

ID: 39900789
I have done that but I still get the same error message.

Author Comment

ID: 39900815
I have it working thank you! I had to authorise the DHCP as a final step.

Featured Post

Online Training Solution

Drastically shorten your training time with WalkMe's advanced online training solution that Guides your trainees to action. Forget about retraining and skyrocket knowledge retention rates.

Question has a verified solution.

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

Recently, I had the need to build a standalone system to run a point-of-sale system. I’m running this on a low-voltage Atom processor, so I wanted a light-weight operating system, but still needed Windows. I chose to use Microsoft Windows Server 200…
Configuring network clients can be a chore, especially if there are a large number of them or a lot of itinerant users.  DHCP dynamically manages this process, much to the relief of users and administrators alike!
There's a multitude of different network monitoring solutions out there, and you're probably wondering what makes NetCrunch so special. It's completely agentless, but does let you create an agent, if you desire. It offers powerful scalability …
Monitoring a network: how to monitor network services and why? Michael Kulchisky, MCSE, MCSA, MCP, VTSP, VSP, CCSP outlines the philosophy behind service monitoring and why a handshake validation is critical in network monitoring. Software utilized …

617 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