Client Can’t Connect to WDS Server

Since I posted this I've come into the problem many times, and in nearly all of them it was Scope Options

Having any of the following options set caused problems, 60, 66, 67. In the case of only 60 being set it still allowed connection to an SCCM PXE point outside of the subnet with IP Helpers enabled but failed at providing a boot image.

In addition I've also seen incorrect vlan id's causing very similar issues. So in general if you get to the point that PXE starts, talks to CM but doesn't complete (and no error is reported), check your IP Helpers, your vLANs and your Scope options.

Your problem is likely to do with the fact that PXE boot communication is broadcast and cant cross vlans without the configuration of ip-helper like address configuration.i would reference offical setup guides from microsoft on wds setup and read about the function of ip helpers.

OK, so your just currently messing with hyper v virtual networking to configure and test wds..which is strange as you would normally extend this out to your switching infastructure aswell. This is a bit problematic if you don't completly understand the comunication that takes place in a traditional scenario.

In a traditional scenario you may have; A WDS/PXE/TFTP server on a server Vlan A DHCP Server on a server Vlan

A Switch in the middle with interfaces on the different vlans and configured for ip helper address. A Client Workstation on the Client Workstation Vlan

Explains the communication process: http://technet.microsoft.com/en-us/magazine/2008.07.desktopfiles.aspx

Scenario 1 Error. WDS and DHCP cant be on the same server without additonal configuration as they use a port required for DHCP. IF you want to do this you need to set optoin 60 in dhcp

Senario 2 Error. THis will work if the client and server are on the same vlan, but not if they are on different vlans without configuring ip helpers like features on your hyper-v switches. Read this: http://windowsitpro.com/networking/configuring-dhcp-and-wds