WDS


problem wds.

there local-area network done on 3 vlan-a. in 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 3 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 boot end unsuccessful "proxydhcp service did not reply request on port 4011"

on primary , secondary dc dhcp scopes have 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 wds boot other vlan ?????

workstation in other vlan ping primary , seconadry dc , wds server. they receive dhcp scopes without trouble.




sergey.k said:

067 boot file name - reminst\boot\x86\pxeboot.com"



 the paths tftp relative reminst share, path above wrong. should using wdsnbp.com boot program, , not pxeboot.com using wdsnbp.com supported method of doing this.

putting together, boot file name should "\boot\x86\wdsnbp.com"


Windows Server  >  Setup Deployment



Comments

Popular posts from this blog

server manager error: ADAM.events.xml could not be enumerated.

Cannot access Anywhere Access using domain name?

WMI Failure: Unable to update Local Resource Group