themightymrp Posted October 16, 2013 Posted October 16, 2013 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...
Darylrese Posted October 16, 2013 Author Posted October 16, 2013 (edited) Hi Guys 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 Edited October 16, 2013 by Darylrese
IrritableTech Posted October 16, 2013 Posted October 16, 2013 So just to clarify @Darylrese - when you say the changes you've made - that was adding the DHCP options 66 & 67?
Darylrese Posted November 6, 2013 Author Posted November 6, 2013 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
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now