Sign in
 
HomeWindows Server “8” Beta20082003LibraryForums
Windows Server TechCenter > Windows Server Forums > Setup Deployment > WDS

Answered WDS

    •  
      Monday, June 09, 2008 9:57 AM
       
       
      Sign In to Vote
      0
      Sign In to Vote
      Problem WDS.

      There is local-area network done on 3 Vlan-a. In the centre kernel from switch 3Com 5500.

      1 - Vlan 172.16.0.1-172.16.126.255
      2 - Vlan 172.17.0.1-172.17.126.255
      3 - Vlan 172.18.0.1-172.18.126.255

      In 1-Vlan three servers (Primary DC, Secondary DC, WDS server)
      172.16.0.1 - Primary DC (DNS,DHCP)
      172.16.0.2 - Secondary DC (DNS,DHCP)
      172.16.0.3 - WDS Server
      In other Vlan - workstation

      If boot WDS images load in Scope 172.16.0.1-172.16.126.255 boot pass successful.
      If boot WDS images load other Vlan to boot end unsuccessful "ProxyDHCP service did not reply to request on port 4011"

      On the Primary and Secondary DC DHCP Scopes have this settings
      "

      003 Router - 172.17.0.10

      006 Dns Servers -  172.16.0.1, 172.16.0.2

      015 Dns Domain Name - Company.local

      044 Wins/Nbns Servers - 172.16.0.1, 172.16.0.2

      060 PXEClient - PXEClient

      066 Boot Server Host Name - 172.16.0.3

      067 Boot file Name - REMINST\boot\x86\pxeboot.com

      "

      "

      003 Router - 172.18.0.10

      006 Dns Servers -  172.16.0.1, 172.16.0.2

      015 Dns Domain Name - Company.local

      044 Wins/Nbns Servers - 172.16.0.1, 172.16.0.2

      060 PXEClient - PXEClient

      066 Boot Server Host Name - 172.16.0.3

      067 Boot file Name - REMINST\boot\x86\pxeboot.com"

      "

      Why ProxyDHCP not work for WDS boot from other VLAN ?????

      Workstation in other Vlan ping Primary and Seconadry DC and WDS server. They receive DHCP from your Scopes without trouble.




       

    Answers

    • Wednesday, June 11, 2008 2:51 AM
       
       Answered
      Sign In to Vote
      0
      Sign In to Vote
      Sergey.K said:

      067 Boot file Name - REMINST\boot\x86\pxeboot.com"



       The paths for TFTP are relative to your REMINST share, so your path above is wrong. You should also be using wdsnbp.com as your boot program, and not pxeboot.com as using wdsnbp.com is the only supported method of doing this.

      Putting this together, your boot file name should be "\boot\x86\wdsnbp.com"
       

    All Replies

    • Wednesday, June 11, 2008 2:51 AM
       
       Answered
      Sign In to Vote
      0
      Sign In to Vote
      Sergey.K said:

      067 Boot file Name - REMINST\boot\x86\pxeboot.com"



       The paths for TFTP are relative to your REMINST share, so your path above is wrong. You should also be using wdsnbp.com as your boot program, and not pxeboot.com as using wdsnbp.com is the only supported method of doing this.

      Putting this together, your boot file name should be "\boot\x86\wdsnbp.com"
       
    • Wednesday, June 11, 2008 12:39 PM
       
       
      Sign In to Vote
      0
      Sign In to Vote
      Thank. Problem go away :))
       
    • Tuesday, December 15, 2009 6:34 PM
       
       
      Sign In to Vote
      0
      Sign In to Vote
      Thank you!

      Having the same problem, just a year and a half later. 

      I didn't see this
      -067 Boot file Name - REMINST\boot\x86\pxeboot.com"
      in the WDS docs anywhere.