locked
WDS Client 無法接收到開機程式 RRS feed

  • 問題

  • 請教,目前我在公司架設一部 WDS,在測試階段的時候,Server與Client同Subnet的時候是完全無問題的

    但將Server移到公司Server專用網段之後,Client端的網段就無法使用了

    會出現 PXE-53:No boot filename received   &  PXE-M0F:Exiting Intel Boot Agent

    我知道DHCP需要設定 Relay,但是我的疑問是

    已經安裝OS的Client都已經可以透過DHCP拿到 IP應該代表 DHCP Relay沒問題才對吧?!?!

    還是有哪裡沒有設定到呢?

    (DHCP與WDS不同Server & 公司是以Cisco Router做 vLan)

    EX:

    Server Scope : 10.1.1.0 --->同網段可用PXE boot
    Client1 Scope : 10.1.2.0 --->無法PXE boot 但已安裝OS的Client 可正常拿到 ip
    Client2 Scope : 10.1.3.0 --->無法PXE boot 但已安裝OS的Client 可正常拿到 ip

    2009年12月8日 上午 08:46

解答

  • Hi, Pat Mok

    感謝您提供的連結,昨天我再另外一個國外網站找到了一些資訊,跟你所提供的連結內容差不多

    你說的IP Helper我知道,但我的問題是出在這裡(第三個小圓點),但是在同網段的情況之下,卻不用刻意去修改DHCP Scope的 Option
    而指定開機的也不是boot\x86\wdsnbp.com 而是另外一個boot\x86\pxeboot.com
    不過針對以上兩個問題去做設定即修改就可以解決問題了
    感謝您的協助 :p
    • If DHCP is installed on a server that is located in a different subnet, you will need to do one of the following:

      • (Recommended) Configure your router to forward broadcast packets. All DHCP broadcasts by client computers on UDP port 67 should be forwarded directly to both the DHCP server and the Windows Deployment Services server. Also, all traffic on UDP port 4011 from the client computers to the Windows Deployment Services server should be routed appropriately (these requests direct traffic, not broadcasts, to the server). 
      • Add DHCP options 66 and 67. Option 66 should be set to the Windows Deployment Services server, and option 67 should be set to boot\x86\wdsnbp.com. For more information, see Managing Network Boot Programs (http://go.microsoft.com/fwlink/?LinkId=115304 ).
    • If Windows Deployment Services and DHCP are running on the same computer, configuring Windows Deployment Services to not respond to any client computers will not work. This is because although Windows Deployment Services will not respond, DHCP will. You can try to work around this issue by disabling DHCP option 60 on the DHCP tab
    • 已標示為解答 Jackie.C 2009年12月9日 上午 01:56
    2009年12月9日 上午 01:56

所有回覆

  • Hi JACKIE,

    你的WDS 與DHCP 是否設定在同一部server? 我在microsoft windows deployment service on server 2008 文章找了以下一段關於不同subnet 的設定

    If DHCP is installed on a server that is located in a different subnet, you will need to do one of the following:

    ·      (Recommended) Configure your IP Helper tables. All DHCP broadcasts by client computers on UDP port 67 should be forwarded directly to both the DHCP server and the Windows Deployment Services PXE server. Also, all traffic on UDP port 4011 from the client computers to the Windows Deployment Services PXE server should be routed appropriately (these requests direct traffic, not broadcasts, to the server).

    詳細請看http://technet.microsoft.com/en-us/library/cc771670(WS.10).aspx#BKMK_ConfiguringDS

    2009年12月9日 上午 01:44
  • Hi, Pat Mok

    感謝您提供的連結,昨天我再另外一個國外網站找到了一些資訊,跟你所提供的連結內容差不多

    你說的IP Helper我知道,但我的問題是出在這裡(第三個小圓點),但是在同網段的情況之下,卻不用刻意去修改DHCP Scope的 Option
    而指定開機的也不是boot\x86\wdsnbp.com 而是另外一個boot\x86\pxeboot.com
    不過針對以上兩個問題去做設定即修改就可以解決問題了
    感謝您的協助 :p
    • If DHCP is installed on a server that is located in a different subnet, you will need to do one of the following:

      • (Recommended) Configure your router to forward broadcast packets. All DHCP broadcasts by client computers on UDP port 67 should be forwarded directly to both the DHCP server and the Windows Deployment Services server. Also, all traffic on UDP port 4011 from the client computers to the Windows Deployment Services server should be routed appropriately (these requests direct traffic, not broadcasts, to the server). 
      • Add DHCP options 66 and 67. Option 66 should be set to the Windows Deployment Services server, and option 67 should be set to boot\x86\wdsnbp.com. For more information, see Managing Network Boot Programs (http://go.microsoft.com/fwlink/?LinkId=115304 ).
    • If Windows Deployment Services and DHCP are running on the same computer, configuring Windows Deployment Services to not respond to any client computers will not work. This is because although Windows Deployment Services will not respond, DHCP will. You can try to work around this issue by disabling DHCP option 60 on the DHCP tab
    • 已標示為解答 Jackie.C 2009年12月9日 上午 01:56
    2009年12月9日 上午 01:56