The following registry subkey controls whether the PXE server listens on the DHCP port: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WDSServer\Providers\WDSPXE In the Server Properties dialog box, select the DHCP tab.Ĭlick to select the Do not listen on port 67 check box, and then select Apply.
BATTLENET WON'T START WINDOWS 10 WINDOWS
In the Windows Deployment Services window, expand Servers, right-click the WDS server name, and then select Properties. Select Start, select Run, type wdsmgmt.msc, and then press OK. Method 1Īt the command prompt, type the following command, and then press ENTER: wdsutil /set-Server /UseDhcpPorts:No Method 2 To do it, use one of the following methods, as appropriate for your situation. To resolve this issue, configure the WDS Pre-boot execution Environment (PXE) client to stop listening on port 67. However, the DHCP server already uses this port. When the DHCP server and the WDS server are installed on the same computer, the WDS Service tries to use the port 67.
Additionally, you may receive an error message, and the message is logged in the WDS Server Log.
On a Windows 2008 Server-based computer, when you try to start WDS server, the WDS server may not start. This article provides a solution to an issue that occurs when you start the Windows Deployment Services (WDS) server, the WDS server may not start.Īpplies to: Windows Server 2012 R2 Original KB number: 954410 Symptoms