Have you ever installed Windows Deployment Services (WDS) and Dynamic Host Protocol (DHCP) on the same server? Usually installing WDS and DHCP on the same server doesn’t cause a problem, but in some cases, you will have issues with starting the WDS server.
This error is related to the DHCP ports and WDS ports conflicting.
In this blog post, I will briefly explain how WDS and DHCP works and how to solve the issue.
What is Windows Deployment Services (WDS)?
Windows Deployments Services is used to deliver a boot image to the workstation for operating system deployment from the network using PXE.
What is Dynamic Host Protocol (DHCP)?
DHCP is a server role used to deliver IP addresses to clients dynamically.
The error with conflicting WDS and DHCP ports
Looking at the Event Log, you will see this nasty error:
“The Windows Deployment Services Server service terminated with service-specific error Only one usage of each socket address (protocol/network address/port) is normally permitted.”
The reason why this happens is that both WDS and DHCP use the UDP port 67.
How to fix the error
The solution to this problem is manually changing a registry value to force the WDS service not to use the DHCP ports.
Here’s how you do it:
Open Regedit and go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WDSServer\Providers\WDSPXE
Open the reg value UseDhcpPorts and change it from 1 to 0
Now start the WDS Service, and it should work 🙂
There are many scenarios where you might want to have the WDS and DHCP server roles on the same server. If you use the above solution, you can 🙂
Did this article help you? Please leave a comment below!
- How to solve the error 80072ee7 in SCCM
- How to fix error when accessing content directly from a Distribution Point in SCCM
- Where are the SCCM Distribution Point log files?
- What is multicast and how do I enable it in SCCM?
- How to configure deadlines for Automatic Deployment Rules in SCCM
- What are the SCCM log viewers CMTrace and OneTrace?