Here is a bit of info for you, but I think you have covered all these options.
Configuring DHCP and WDS | Networking content from Windows IT Pro
I have indeed but thanks for the link :)
It gets stranger....theres only 1 port in our office that works with WDS and i have checked the tagging on the port and its exactly the same as the other ports in our office which dont work. Am i right in thinking something must have been configured on just that port that does work on the switch?
Maybe some kind of port security? MAC filtering or some such? Would be a very odd setup if it was though.
Literally, all you should need is the ip helper-address bit in your core switch and options 66 and 67 configure in your DHCP server (I set them in server options rather than scope options, that way they get passed down into each vlan scope of addresses). Option 66 is the IP of DHCP server, option 67 is boot\x86\wdsnbp.com
What are you getting on screen when you try to network boot from other ports in your office?
I dont think it can be MAC auth as it will literally work on any device connected to that 1 port in the office.
I just tried setting the DHCP settings and will check again in the morning.
The other ports in the office give the same error, no DHCP or ProxyDHCP offering
Yep it's the IP of the WDS server - probably a typo.
Could you post the config of the switch with the port that works over WDS? Mask IP addresses and Names if you don't want us to see them.
It was a typo - my bad :doh:
No problem. I have set the options on the server options and its still saying the same error. When it does work this is the screen:
I will screenshot a machine that does not and will report back
Out of interest, in the WDS console settings, under the PXE Response Settings tab - do you have it set to respond to both known and unknown client computers? Just wondered if for some strange reason the previous person had used the prestaged-computers settings?? Its probably not that tbh.
Looking at your screenshot, the one that works is obviously on the same vlan as the DHCP server (going by subnet and IP's). Are you sure that the other ports in your office are tagged/untagged on the same VLAN number as this one working port? As @IrritableTech says above, if you could post the switch config it would help...
Just to let you know i found the problem! I was using a Server 2008 box for the DHCP snap in and i realised its linking to a different DC. I logged onto the DC that has DHCP which is a 2012 box, made the changes in there and its now working! Must have been because the snap in was not making changes on the DC hosting DHCP.
Tested 3 machines on different VLAN's and all picking it up now although we are yet to test an actual build
So just to clarify @Darylrese - when you say the changes you've made - that was adding the DHCP options 66 & 67?
That is correct, however i was doing it through a snap-in on a server 2008 box and it wasn't updating the settings on the server which is running Server 2012