All servers are located in server's subnet (172.22.x.x) All clients - in other subnets (10.130.x.x). There is DHCP works in client's subnet. DHCP works on some Cisco device to which I have no access. What I did: Installed SCCM 2007 R2 (in server's subnet). Installed WDS. Installed PXE service point. PXEsetup.log demonstrates no errors. There are no any errors in Component Status. Created Operating System install Package (Win XP + drivers), it was deployed by Task Sequence Media - succesful. By office memo added DHCP options: 66 - 172.22.101.27 67 - SMSBoot\x86\wdsnbp.com When I have attempt to boot I got error PXE-E32: TFTP open timeout (after getting IP, mask and gateway). Attempts with 2 other network adapter (intel and realtek). On my workstation I installed TFTP-client (Windows 7) and downloaded file: C:\Windows\System32>tftp -i 172.22.101.27 get smsboot\x86\wdsnbp.com Transfer successful: 31124 bytes in 1 second(s), 31124 bytes/s What can I do anymore to resolve this problem? " м , , " ( )

did you configure IP Helpers on the switch which is separating the subnets ? My step by step SCCM Guides I'm on Twitter > ncbrady

No I didn't. Our Cisco administrator said that if he enables IP helper then all DHCP traffic will go to server's subnet, and clients could not retrieve any settings. But is not what we would like or we don't understand something. " м , , " ( )

ok then, have a read of what Dominic says here My step by step SCCM Guides I'm on Twitter > ncbrady

He says about 2 variants: 1) SCCM=DHCP and it is in a subnet other then clients. In this case we need IP-helper. Then client's request going through it, reaches SCCM-DHCP and coming back with settings. 2) SCCM!=DHCP. DHCP in same subnet as clients. SCCM somewhere else. In this case " options 66 and 67 are not delivered by the SCCM server, but configured on the DHCP ... It should work, if you configure the wdsnbp as the bootstrap file. ". Is my case. But it doesn't work. Isn't it? " м , , " ( « »)

He says about 2 variants: 1) SCCM=DHCP and it is in a subnet other then clients. In this case we need IP-helper. Then client's request going through it, reaches SCCM-DHCP and coming back with settings. 2) SCCM!=DHCP. DHCP in same subnet as clients. SCCM somewhere else. In this case " options 66 and 67 are not delivered by the SCCM server, but configured on the DHCP ... It should work, if you configure the wdsnbp as the bootstrap file. ". Is my case. But it doesn't work. " м , , " ( )

Can I deploy distribution point for a boot image in same subnet as a client without an additional SCCM? What I need to do for it? Except publishing DP in the CM console." м , , " ( )