WDS Server - PXE + Diffrent DHCP Scope + Diffrent Network

Dear All,
I have a WDS Server + DHCP on one server and OS Deployment is working properly.
but i have a different network with different DHCP Server + DHCP Scope and wanted to deploy the WDS images on that.
so please guide me how to do this..
Explanation : DHCP + WDS on 172.27.11.XX  (OS Deployment working properly)
DHCP on 172.27.3.XX (Not Able to find PXE Server on this..) all ports are open and tried to add 66 and 67 port with WDS  name or IP but did not work.. please help..
Thanks in advance
Dhiraj Gaikawd

Hi,
You should configure IP helper on your router to point to your DHCP and WDS server.
And make sure port 4011 on WDS is reachable accross router.
Hope this helps.

Similar Messages

  • On which port number WDS server will listen & service when installing on server which is also DHCP server?

    hi frineds
    in documents we read when we install WDS on the server which is also DHCP server, we must select this check mark :
    "do not listen on port 67"
    it means we instruct the WDS service not to listen on port UDP 67  to avoid a port conflict between WDS server service and DHCP server service.
    So now on which port number WDS server will listen & service ?
    thanks in advance

    Hi john.s2011,
    If Windows Deployment Services and DHCP are running on the same physical computer, this means that the DHCP server is listening on port 67 and is responsible ensuring authorization.
    The related KB:
    How the PXE Server Works
    http://technet.microsoft.com/en-us/library/cc732649(v=ws.10).aspx
    The related thread:
    DHCP is not responding for WDS
    http://social.technet.microsoft.com/Forums/windowsserver/en-US/07f98ac7-cc6f-4385-ba21-2e85bb460c03/dhcp-is-not-responding-for-wds
    I’m glad to be of help to you!
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.
    hi Alex.
    sorry for delay
    thanks a lot
    regards

  • SCCM 2012 R2, DHCP and WDS and PXE same server

    hi
    I am using DHCP and PXE on same server and getting error PXE-E55: proxyDHCP did not reply to request on port 4011

    HI,
    To get WDS and DHCP to work on the same machine, you need to configure WDS to share the same server as DHCP, here is how it is done.
    You must have a functioning DHCP server with an active scope. WDS will utilize PXE which requires a DHCP server.
    Whether you plan to co-host WDS and DHCP on the same server or use two different servers you must configure WDS to listen on a specific port. DHCP and WDS both require port number 67. If you have co-hosted WDS and DHCP you can move DHCP or the PXE site role
    to a separate server or use the procedure below to configure the WDS server to listen on a different port.
    Modify the following registry key:
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WDSServer\Providers\WDSPXE              
    Set the registry value to:
    UseDHCPPorts = 0              
    For the new configuration to take effect run the following command on the co-located DHCP and WDS server:
    WDSUTIL /Set-Server /UseDHCPPorts:No /DHCPOption60:Yes
    https://technet.microsoft.com/en-us/library/bb680753.aspx
    -- My System Center blog ccmexec.com -- Twitter
    @ccmexec

  • ASA Migration of DHCP Scope to a Server

    Hello All,
    We migrated the DHCP scope from the ASA to a MS DHCP server with this configuration:
    group-policy BV-SSL1 internal
    group-policy BV-SSL1 attributes
    no address-pools value remotepool4 remotepool2 remotepool3
    no intercept-dhcp enable
    dhcp-network-scope 10.180.49.0
    exit
    tunnel-group BVVPN10 general-attributes
    no address-pool remotepool2
    no address-pool remotepool3
    no address-pool remotepool4
    dhcp-server 10.182.14.55
    exit
    tunnel-group BV-SSL general-attributes
    no address-pool remotepool2
    no address-pool remotepool3
    no address-pool remotepool4
    dhcp-server 10.182.14.55
    exit
    no vpn-addr-assign aaa
    no vpn-addr-assign local
    vpn-addr-assign dhcp
    This is running good, until we used all 254 addresses that was specified in the dhcp-network-scope.
    My question is should i have specified dhcp-network-scope none to allow for all 3 scopes can be used to hand out IP addresses for the remote users?
    Thanks,
    Kimberly

    Okay, that's at least a good start. Can you monitor the ULS logs while you attempt to browse to the site to see what form of error(s) you're getting?
    Trevor Seward
    Follow or contact me at...
    &nbsp&nbsp
    This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

  • WDS Server DHCP configuration

    Hi,
    we have installed WDS server on windows server 2012. Our DHCP is a CISCO 2911 Router. what do we need to configure on the WDS and DHCP server for the clients to have a PXE boot.
    Thanks in advance

    "If the local DHCP server is not a Microsoft DHCP server, we will have to manually configure the DHCP server to forward the request to the WDS server."
    How will the clients ( laptops/desktops) do the PXE boot and pull the image from WDS server ?
    "If you have any problem, please configure DHCP option 66 and 67."  -- on which device do we need to configure this ?
    Thanks

  • MDT/WDS PXE Deployment - DHCP Options for both x64 and x86

    Alright, I've found out the option 66 & 67 information, as what to set for each. The problem I'm trying to figure out is what to use for the boot file for option 67. So far all the info I've found says this:
    Configure DHCP option 67 with the right boot image file.
    For 32-bits systems \boot\x86\wdsnbp.com
    For 64-bits systems \boot\x64\wdsnbp.com
    I want to be able to use this for both 32 and 64 bit Windows clients, but cannot find anywhere that specifies how I would be able to do both.

    DHCP Options (specifically 067) can have a significant impact on which NBP your client can access.  If you specify \Boot\x86\Wdsnbp.com you are forcing the client to the 32bit NBP.
    If you specify \Boot\x64\Wdsnbp.com you are forcing the client to the 64bit NBP.
    Niether option is an ideal solution, especially if you have a varied environment.
    I would take a look at the following article and see if it sheds some light on your question:
    PXE booting with WDS – DHCP Scope vs IP Helpers

  • DHCP on 'hybrid' network - how to point clients to specific DHCP server

    Moving computers off of a private 'hybrid' network to a different private network.
    ISSUE: The clents will boot and ask for an IP from DHCP, problem is the 'hybrid' network runs a DHCP server with address range of 192.99.x.x  whereas the DHCP server we need to hit is on the 10.2.xx address range.  Is there a simple method to point
    clients to a specific DHCP server? 
    Note: I have requested Network Srvcs to block UDP traffice on ports 67 and 68 for the address range of the 'hybrid' network.
    Users still need access to the hybrid.
    Please advise,
    Many Thanks in advance

    DHCP is rather a simple minded service. The client broadcasts out and the first guy responds. If you ahve two DHCP servers on the same subnet or wire, even if they have different IP addresses on that subnet, and they both have scopes corresponding to
    the IP address of their interface on that subnet/wire, then they will offer DHCP services. DHCP won't give out an IP on an interface that the scope doesn't match the subnet.
    For example, if I have a DHCP server with an IP of 10.200.1.200/24, and a scope of 10.200.1.100-150/24, then it will give out IPs on that interface. However, if that same DHCP server has an interface configured with 192.168.20.150, then DHCP will not give
    out IPs on an interface configured with 10.200.1.100, unless there is a Relay Agent or IP Helper from the router or switch VLAN that is connected to that subnet. You can test this out yourself.
    A separate VLAN for each subnet solves the problem because you are separating the two servers to hostg DHCP on their own, respective subnets.
    Ace Fekay
    MVP, MCT, MCSE 2012, MCITP EA & MCTS Windows 2008/R2, Exchange 2013, 2010 EA & 2007, MCSE & MCSA 2003/2000, MCSA Messaging 2003
    Microsoft Certified Trainer
    Microsoft MVP - Directory Services
    Complete List of Technical Blogs: http://www.delawarecountycomputerconsulting.com/technicalblogs.php
    This posting is provided AS-IS with no warranties or guarantees and confers no rights.

  • PXE not working from WDS Server 2012

    Hello,
    when i try to deploy a VM using WDS/MDT the startup for contacting the WDS-server is very slow :
    The WDS-server is a Server2012R2 (not preview)-server. 
    I have reinstalled WDS already but nothing will help.
    Anybody with a solution?
    Thx

    Hi,
    Did the installation just stuck there?
    Do you have any phycial machines with the same problem?
    Acctually, there is some problem when deploy VMware using WDS:
    Check this article:
    Issues using Enteo Netinstall or Microsoft Windows Deployment Services (WDS) to PXE boot virtual machines (1009104)
    http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1009104
    Please Note: Since the web site is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • Getting "Error in setting DHCP Scope Network and Netmask"

    Hello Cisco Experts - I'm trying to setup a new DHCP scope on my Cisco 2504 and am getting the error referenced above.  Here are the settings I am using:
    I have another range setup in exactly the same way only it runs from 10.35.209.65 through 10.35.209.90.  Can anyone point me in the right direction for what I'm doing wrong?  Thanks in advance!

    Good question.
    Here is the screeshot of the scope I just activated:
    What IOS Version are you running?  I have 7.4.100.0 on mine.
    Please Rate Helpful posts and mark this question as answered if, in fact, this does answer your question.  Otherwise, feel free to post follow-up questions.
    Charles Moreton

  • Ip source guard feature and dhcp DHCP scope exhaustion (client spoofs other clients)

    Hi everybody.
    A dhcp server assigns ip adress based on mac address carried by client hardware field in dhcp packets.
    One potential attack is when a rogue host mimics different mac addresses and causes dhcp server to assign the ip addresses until no ip address is left for legitimate host.
    For e.g a host h1 with mac1 has assigned ip address by dhcp server as:
    199.199.199.1 mac1
    Dhcp server has the above entry in its database.
    Using hacking tools such as Yersinia or Gobbler one can create a dhcp discover messages each time creating a different mac for client hardware field in dhcp server thereby causing a dhcp server to assign ip addresses because to dhcp server , these are legitimate dhcp discover messages with each carrying a different mac in client hardware addresses.
    You might say use dhcp snooping and it will prevent that (  dhcp scope exhaustion) and configure the switch to check if src mac matches the client hardware address in dhcp message. But still we can creat spoofed discover messages where src mac in ethernet header will match the client hardware address in dhcp discover message. We still did not overcome the problem.
    You might say use IP source guard feature but will it really prevent that problem from happening?
    Let me illustrate it :
    h1---------f1/1SW---------DHCP server
    Let say we have configured dhcp snooping on sw1 and f1/1 is untrusted port.  The switch has following dhcp binding
    199.199.199.1    mac1   vlan1  f1/1
    Next we configure ip source guard to  validate both src mac and src ip against the dhcp bindings  . When  we configures ip source guard first  , it will allow dhcp communication only so a host can request ip address and a dhcp binding can be built. After that ip source guard will validate src ip or src mac or both against the dhcp binding.depending upon how we configure ip source guard.
    In our case we have configured ip source guard to validate both src mac and src ip against the dhcp binding.
    A dhcp binding is already created as:
    199.199.199.1 mac1 vlan 1 f1/1
    Now using the hacking tools Yersinia or Gobbler on h1, we create our first spoofed dhcp discover message  where src mac=mac2 in ethernet header and  client harware address= mac2 in dhcp discover message. Since switch is configured with ip source guard feature and therefore allows dhcp discover message to pass through. Dhcp server upon receiving the dhcp message assigns another ip address from the pool. Now the dhcp server has following entries:
    199.199.199.1 mac1
    199.199.199.2 mac2.
    We can continue to craft spoofed dhcp discover messages as mentioned above and have dhcp server keep assigning ip addresses until the whole pool is exhausted.
    So my question is how does  ip source guard in conjuction with dhcp snooping prevent this particular attack from happening? ( i.e DHCP scope exhaustion)
    I really appreciate your input.
    thanks and have a great week.

    Thanks Karthikeyan.
    First of all, we gather all the information about the  locations of legitimate dhcp servers in our network. Once we have this information, we will configure the ports used to reach them as trusted. All the ports where end users will connect will be untrusted and therefore subject to dhcp snooping .
    it means if any of user connected in that switch/vlan runs a dhcp  services like vmware for eg. Snooping will prevent the dhcp/bootp  servers connected to that port will not be able to process.
    Yes that is correct. Because dhcp snooping feature will check these ports for the messages usually sent by dhcp server such as dhcp offer, etc. If the end user is running dhcp server using virtual machine, that port should be configured as trusted if it is dertermined  that end user is running a legitimate dhcp server using vm ware.
    When we have the dhcp snooping it prevents the 1st level of hacking  itself. I don't think so it will have any impact on dhcp address  releasing.
    I am sorry. You lost me here. What is 1 level of hacking?
    Dhcp snooping checks for dhcp messages such as dhcp release, dhcp decline.on untrusted port against the dhcp bindings.
    Here is why;
    h1---------SW1-------dhcp server
                   |
                 h2
    Let say we don't have dhcp snooping in above attack and  h2 is a legitimate user has already assigned ip address 199.199.199.2 by dhcp server. Thus the dhcp server has an entry:
    199.199.199.2 mac2
    Next we connect rogue user and it gets ip address 199.199.199.1 now the dhcp server has entries:
    199.199.199. 1  mac1
    199.199.199.2   mac2
    Now using hacking tools, h1 create a fake dhcp release message  with  199.199.199.199.2   mac2
    Dhcp server upon receiving this message, will release the ip address and returns it to the pool.
    By using DHCP snooping, switch will peer inside dhcp release message and checks against the binding. If there is conflict, it will drop the message.
    IFor e.g
    If have dhcp snooping configured , then switch will have adhcp binding as:
    199.199.199.1    mac1    vlan 1   f1/1  lease time
    199.199.199.2     mac2    vlan 2    f1/2 lease time.
    If h1 tries to send fake dhcp release with ip address 199.199.199.2    mac2
    Switch will check ip address 199.199.199.2  and mac2 against the binding related to f1/1 . Sw will find a conflict and therefore drops the dhcp release packet.
    Thanks

  • WDS Server Service won't start - 'An error occurred trying to start the Windows Deployment Services Server.'

    I'm having issues installing starting the WDS server service on Win 2008 R2,  this is happening on multiple (all 2008 R2) systems on this domain so I'm beginning to think it's either AD or network related, in event viewer I get the following error.
    'An error occurred trying to start the Windows Deployment Services Server.'
    Error Information: 0x0906
    EventID : 257 
    single domain, single forest, 2008 R2 functional level, both system are virtual plugged into same vswitch on a flat network.
    any ideas what might be the issue?  I've never had an issue getting this working on many occasions before today and I've come to many a dead end looking at other articles thus far... 
    With WDS tracing enabled I get the following error information:
    [4304] 09:22:11: ===>Starting logging of module [WDSServer]
    [4304] 09:22:11: [UDPPorts] Policy: 1, Dynamic Port Range: 64001-65000.
    [4304] 09:22:11: [RPC] Using Tcp Port 5040 for Rpc Calls.
    [4304] 09:22:11: [RPC] Client Impersonation Logging=Disabled
    [4304] 09:22:11: [RPC] Host Name: sccm.domain.local
    [4304] 09:22:11: [RPC] NTLM/Kerberos Spn: ldap/sccm.domain.local
    [4304] 09:22:11: [RPC] Initialized
    [3756] 09:22:11: [RPC] Server Started.
    [4304] 09:22:11: [BINLSVC][RPC][Ep={5F4FB9F0-C0E3-41C1-AA00-9A7C690AC3A3}] Registered
    [4304] 09:22:11: [BINLSVC] Provider Initialized.
    [4304] 09:22:11: [WDSDDPS][RPC][Ep={FA0A27E1-C2BA-4B3B-94B2-025E82FFAA6D}] Registered
    [4304] 09:22:11: [WDSDDPS][RPC][Ep={011D24AC-CB3A-4739-A339-5D2E1B5306CE}] Registered
    [4304] 09:22:11: [51][WDSDDPS] [d:\w7rtm\base\ntsetup\opktools\wds\ddp\server\ddpprovider.cpp:196] Expression: , Win32 Error=0x906
    [4304] 09:22:11: [WDSDDPS][RPC][Ep={FA0A27E1-C2BA-4B3B-94B2-025E82FFAA6D}] Closed
    [4304] 09:22:11: [WDSDDPS][RPC][Ep={011D24AC-CB3A-4739-A339-5D2E1B5306CE}] Closed
    [4304] 09:22:11: [d:\w7rtm\base\ntsetup\opktools\wds\wdssrv\server\src\wdsprovider.cpp:144] Expression: , Win32 Error=0x906
    [4304] 09:22:11: [WDSDDPS] Initialization Failed (rc=2310)
    [4304] 09:22:11: [d:\w7rtm\base\ntsetup\opktools\wds\wdssrv\server\src\wdsprovhdl.cpp:172] Expression: , Win32 Error=0x906
    [4304] 09:22:11: [WDSDDPS] Deleted.
    [4304] 09:22:11: [d:\w7rtm\base\ntsetup\opktools\wds\wdssrv\server\src\wdsservice.cpp:178] Expression: , Win32 Error=0x906
    [4304] 09:22:11: [Udp] Listen Shutdown.
    [3756] 09:22:11: [RPC] Server terminated (rc=0)
    [4304] 09:22:11: [RPC] Listen Stopped.
    [4304] 09:22:11: [BINLSVC] Shutting down
    [4304] 09:22:11: [BINLSVC][RPC][Ep={5F4FB9F0-C0E3-41C1-AA00-9A7C690AC3A3}] Closed
    [4304] 09:22:11: [BINLSVC] Deleted.

    It seems I've found out the solution myself,  the issue seems to be caused when DHCP and WDS are on the same server, The installation must identify this during the first installation of WDS but not on subsequent installations, the method to
    get it working again is:
    1.      
    Install WDS Role (using defaults)
    2.      
    Make the following registry change:
    HKLM\SYSTEM\CurrentControlSet\services\WDSServer\Providers\WDSPXE\UseDhcpPorts  =  0
    3.      
    Run the following command line to initialize Windows Deployment Services:
    wdsutil /initialize-server /reminst:D:\RemoteInstall
    4.      
    Run the following command to enable the DHCP port registry setting
    wdsutil /Set-Server /UseDHCPPorts:No /DHCPOption60:Yes

  • Testing moving to new Windows Server 2008 R2 DHCP Server.

    HI all,
    I want to bring up a new DCHP server on an existing Windows Server 2008 R2 Domain Controller.  The current DHCP server is a Windows 2003 Domain Controller.  I have moved all the FSMO Roles to the new 2008 R2 domain controller
    with the plan to eventually demote the 2003 server and take it off the network. I have the dhcp role installed on the new Windows Server 2008 R2 and have duplicated the exact settings (reservations, scope, etc.) from the old windows 2003 server
    on the new 2008 R2 server.  My plan was simply to disable the dhcp service on the old windows server 2003 and then authorize the new Windows Server 2008 R2 DHCP Server.  However, after reading several articles, I understand that once you authorize
    a new dhcp server, the old dhcp sever is unauthorized.  I also read where several people had major issues with the new dhcp server not handing out IP Addresses even though the new dhcp server was authorized successfully.  Since this is
    a production network, I would like to employ the correct method to bring up the new dhcp server.  Also, if there is a problem, is there an easy way to go back to the original dhcp server?  Thanks for your help.
    FD
    Bob Andres

    You can authorize multiple DHCP servers on a network.
    You can activate and deactivate different scopes independently. So you can test DHCP functionality with a test scope.
    Also, you can stop the old server in many ways that allow it to be online very rapidly: stop the dhcp server service, deactivate the scopes and yes even de-authorize the server.
    My advice would be to built a test so you are confident (=very important) and not to fear the final onlining too much. DHCP is no rockets science. If you've replicated the configuration and are aware of possible IP Helper configurations on your routers/switches,
    it should all work out fine.
    MCP/MCSA/MCTS/MCITP

  • DHCP scope full, event ID 1020

    Hi, one of our Windows 2008 R2 Domain controllers is returning the following warning message on almost a daily basis:
    Log Name:      System
    Source:        Microsoft-Windows-DHCP-Server
    Date:          19/11/2014 11:32:41 AM
    Event ID:      1020
    Task Category: None
    Level:         Warning
    Keywords:      Classic
    User:          N/A
    Computer:      computername.domain.x.x
    Description:
    Scope, 10.x.x.0, is 83 percent full with only 39 IP addresses remaining.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Microsoft-Windows-DHCP-Server" Guid="{xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}" EventSourceName="DhcpServer" />
        <EventID Qualifiers="0">1020</EventID>
        <Version>0</Version>
        <Level>3</Level>
        <Task>0</Task>
        <Opcode>0</Opcode>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2014-11-19T00:32:41.000000000Z" />
        <EventRecordID>12980</EventRecordID>
        <Correlation />
        <Execution ProcessID="0" ThreadID="0" />
        <Channel>System</Channel>
        <Computer>computer.domain.x.x</Computer>
        <Security />
      </System>
      <EventData>
        <Data>10.x.x.x</Data>
        <Data>83</Data>
        <Data>39</Data>
      </EventData>
    </Event>
    Upon review of Microsoft Support online, I found the following article which illustrates a few options:
    http://support.microsoft.com/kb/255999/en-au
    What would be the logical choice for us, having the 10.x.x network?
    Ideally, it would be good not having to re-subnet anything if possible, or re-create the scope.
    Would a scope extension require a reboot of the server? Never done this before, so thought I should ask.

    Hi,
    According to your description, my understanding is that DC prompts an warning event ID 1020, indicate 83% full with DHCP scope.
    By default, the threshold value for firing of event 1020 is 80%. Estimate devices number, contrast with the number of IP address in this scope, if the percentage is less than 80%, you may try to reduce the lease duration and decrease the cleanup interval.
    This can help to speed the reclaiming of expired scope IP addresses.
    To reduce the lease duration:
    1.At the DHCP server, click Start, point to Administrative Tools, and then click
    DHCP.
    2.In the DCHP console tree, right-click the scope you want to configure, and then click
    Properties.
    3.On the General tab, under Lease duration for DHCP clients, type the new lease duration.
    To use a Netsh command to set the cleanup interval time:
    1.At the DHCP server, click Start, click Run, type
    cmd, and then press ENTER.
    2.Type netsh dhcp set databasecleanupinterval <NewInterval> (where "NewInterval" is the amount of time in minutes between DHCP database cleanups).
    As an existing DHCP scope, its subnet mask can’t be changed. If the Start Address and
    End Address do not currently include all addresses for your specific subnet, you can increase the number of addresses in the scope by extending the
    Start Address or End Address in the scope properties. This operation needn’t reboot.
    If neither of above 2 suggestions is applicable, new a DHCP scope or reference
    KB255999 (resubnetting and superscoping). At the same time, you need to change your network topology.
    Best Regards,           
    Eve Wang

  • Trouble booting to WDS server to deploy or capture image

    Hello, we have an existing WDS server running Server 2008 R2 with SP1.  I am having trouble getting a Surface Pro 3 to boot to the WDS (even after creating updated deploy and capture boot images).  I can get the Surface to PXE boot, and I am
    able to choose the Deploy or Capture boot image, but then I get the message that an error occurred obtaining an IP address from the DHCP server.  During the PXE boot, the device does obtain an IP address in the correct range.  I tried adding the
    Surface ethernet adapter drivers to the boot wims but since they are not signed I get errors that they cannot be added.  Any suggestions?

    Added drivers to boot images using DISM with the /ForceUnsigned override.

  • WDS and PXE

    I'm trying to set up WDS on server2008r2. the dhcp server is runnning server 2003. I have option 66 enable pointing to 172.18.4.23 and option 67 boot\x64\boot.wim 
    when i try to boot up a client to install the first instance to build my company image i get a TFTP open timeout.  
    i have tried everything that i can find and nothing is getting me any closer to success. 
    Not sure if this will help or not but I also had a linuxpxe sent up on this network that was working until i switch the options 66 and 67 to coincide with the windows instead of the linux box. but in attempt to put it back the way it was so linux can boot
    on our zero clients i get the same TFTP timeout error. 
    Oh did i mention that this is the first time wds is being used in this enviroment so no one really know how to set it up to get it to work. there are vlans on the network but one thing at a time. 

    Hi TCUTech,
    You can try the following simlar thread solution first.
    WDS server and DHCP server on two different servers
    https://social.technet.microsoft.com/Forums/pt-BR/e84c8a4c-a6da-4c4a-8ca6-2a1007b205ae/wds-server-and-dhcp-server-on-two-different-servers?forum=winserversetup
    I’m glad to be of help to you!
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Maybe you are looking for