We hit this issue recently when we went from a setup where the WDS server and clients were on the same subnet to one where they are on separate subnets. As our set had a Cisco router between the two subnets we resolved the issue by also adding the WDS server IP to the Cisco IP Helper-Address (in addition to MS's recommendations)
We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.