+ Post New Thread
Page 2 of 2 FirstFirst 12
Results 16 to 29 of 29
O/S Deployment Thread, WDS Across VLAN's Not Working in Technical; Originally Posted by ADMaster I don’t have option 66 or 67 set in my DHCP and it works fine. Also ...
  1. #16
    Darylrese's Avatar
    Join Date
    Sep 2010
    Location
    Portsmouth
    Posts
    422
    Thank Post
    10
    Thanked 7 Times in 6 Posts
    Rep Power
    10
    Quote Originally Posted by ADMaster View Post
    I don’t have option 66 or 67 set in my DHCP and it works fine.
    Also is your WDS running on the same machine as DHCP. There is a tick box that needs ticking if you are.
    Nope, its a dedicated WDS Server.

  2. #17
    ADMaster's Avatar
    Join Date
    May 2012
    Posts
    332
    Thank Post
    5
    Thanked 35 Times in 30 Posts
    Rep Power
    23
    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

  3. #18
    Darylrese's Avatar
    Join Date
    Sep 2010
    Location
    Portsmouth
    Posts
    422
    Thank Post
    10
    Thanked 7 Times in 6 Posts
    Rep Power
    10
    I have indeed but thanks for the link

  4. #19
    Darylrese's Avatar
    Join Date
    Sep 2010
    Location
    Portsmouth
    Posts
    422
    Thank Post
    10
    Thanked 7 Times in 6 Posts
    Rep Power
    10
    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?

  5. #20
    themightymrp's Avatar
    Join Date
    Dec 2009
    Location
    Leeds, West Yorkshire
    Posts
    1,217
    Thank Post
    215
    Thanked 226 Times in 195 Posts
    Rep Power
    73
    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?

  6. #21
    Darylrese's Avatar
    Join Date
    Sep 2010
    Location
    Portsmouth
    Posts
    422
    Thank Post
    10
    Thanked 7 Times in 6 Posts
    Rep Power
    10
    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
    Last edited by Darylrese; 14th October 2013 at 08:19 PM.

  7. #22
    Darylrese's Avatar
    Join Date
    Sep 2010
    Location
    Portsmouth
    Posts
    422
    Thank Post
    10
    Thanked 7 Times in 6 Posts
    Rep Power
    10
    Quote Originally Posted by themightymrp View Post
    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?
    The DHCP server? I thought 66 was supposed to be the IP of the WDS Server?

  8. #23
    IrritableTech's Avatar
    Join Date
    Nov 2007
    Location
    West Yorkshire
    Posts
    806
    Thank Post
    84
    Thanked 175 Times in 144 Posts
    Rep Power
    65
    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.

  9. #24
    themightymrp's Avatar
    Join Date
    Dec 2009
    Location
    Leeds, West Yorkshire
    Posts
    1,217
    Thank Post
    215
    Thanked 226 Times in 195 Posts
    Rep Power
    73
    It was a typo - my bad

  10. #25
    Darylrese's Avatar
    Join Date
    Sep 2010
    Location
    Portsmouth
    Posts
    422
    Thank Post
    10
    Thanked 7 Times in 6 Posts
    Rep Power
    10
    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:

    20131014_150544.jpg

    I will screenshot a machine that does not and will report back

  11. #26
    themightymrp's Avatar
    Join Date
    Dec 2009
    Location
    Leeds, West Yorkshire
    Posts
    1,217
    Thank Post
    215
    Thanked 226 Times in 195 Posts
    Rep Power
    73
    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...

  12. #27
    Darylrese's Avatar
    Join Date
    Sep 2010
    Location
    Portsmouth
    Posts
    422
    Thank Post
    10
    Thanked 7 Times in 6 Posts
    Rep Power
    10
    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
    Last edited by Darylrese; 16th October 2013 at 12:31 PM.

  13. #28
    IrritableTech's Avatar
    Join Date
    Nov 2007
    Location
    West Yorkshire
    Posts
    806
    Thank Post
    84
    Thanked 175 Times in 144 Posts
    Rep Power
    65
    So just to clarify @Darylrese - when you say the changes you've made - that was adding the DHCP options 66 & 67?

  14. #29
    Darylrese's Avatar
    Join Date
    Sep 2010
    Location
    Portsmouth
    Posts
    422
    Thank Post
    10
    Thanked 7 Times in 6 Posts
    Rep Power
    10
    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

SHARE:
+ Post New Thread
Page 2 of 2 FirstFirst 12

Similar Threads

  1. WDS Across VLAN
    By cpjitservices in forum Windows Server 2008 R2
    Replies: 1
    Last Post: 25th April 2013, 10:55 AM
  2. [WDS] WDS over VLAN
    By newpersn in forum O/S Deployment
    Replies: 4
    Last Post: 28th August 2012, 08:01 PM
  3. Using Server 2008 WDS to deploy images accross VLANs
    By Rav-Singh in forum O/S Deployment
    Replies: 6
    Last Post: 1st June 2012, 08:15 PM
  4. Intresting issue - WDS / Multicasting /PXE and Vlans
    By craigg in forum Enterprise Software
    Replies: 0
    Last Post: 17th August 2011, 08:23 AM
  5. [WDS] VLANs, Hyper-V and WDS
    By bmittleider in forum O/S Deployment
    Replies: 2
    Last Post: 22nd July 2010, 10:25 PM

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •