When WDS and DNS running on the same server may introduce some problems. This happens when the DNS is installed first.
- The DNS service binds to all ports needed by WDS- The Default WDS port range is 64,000 to 65,000
- A specific patch can also cause this problem, watch out!
For how to set various DHCP options, see the following link https://techdirectarchive.com/2020/05/26/wds-and-dhcp-deployment-scenarios-how-to-configure-dhcp-server-option-60-66-and-67-for-windows-deployment-services/
Note: In my case, since I do not have any issue since I am using Windows Server 2019. I have the option to obtain a dynamic port from Winsock as shown below!
But if you are running Windows Server 2008 or 2012 you will run into this issue.
Method 1: To resolve this, you will have to navigate to the WDS Server properties as shown below.
– Click the Network settings tab,
– Change the range from say 64100 to 64200 (Note: You have to ensure other applications are not making use of these ports).
That is all you need to do 🙂
Method 2: You can also set this from the command line using WDSUTIL, see the syntax below.
wdsutil /set-Server /Transport /StartPort:65100 /EndPort:65200
Method 3: If you are running Windows Server 2008 R2 you can also configure WDS to dynamically query WinSock for available ports instead of using a port range. This is done by setting the UdpPortPolicy value in the registry to 0.
– You will find it in the HKLM\System\CurrentControlSet\Services\WDSServer\Parameters key.
– You need to restart WDS after changing the value.
For more similar errors, see the following links below.
Note: These links below may not work for you! Use the method above if both DNS and WDS are sitting on the same server.