WDS and DHCP on the same SCCM site server
Hi, Our SCCM primary site server is running SCCM 2007 SP2 R2 on a Windows 2008 R2 server. The SCCM secondary site server is running on a Windows 2008 R2 server and also configured as DHCP server. I did the following to add the PXE role to the secondary site server: - added WDS role to the secondary site server - changed the usedhcpport registry to 0 - wdsutil /initialize-server /reminst:D:\RemoteInstall - wdsutil /set-server /usedhcpports:no /dhcpoption60:yes - added pxe role to the secondary site server by using cm console After all done, I get an error "the PXE service point is not responding to PXE request... error 16389". When I try to boot a test computer by using pxe, it fails to get a reply from the dhcp server and the error is "proxy dhcp service did not reply to request on port 4011". We have only one LAN in our office. So VLAN, IPhelper, etc should not be the problem. I have tried everything (at least most of them) I could've found from google and still can't find something works. I'm stuck. Any help??? THANKS.
November 26th, 2010 7:40pm

A few questions for you: Is the firewall blocking port 4011 on the server? Have you tried Restarting the WDS Server Service? Do you get errors if you open the WDS MMC from Administrative Tools? Also, I would enable logging for WDS if you haven't already and review the logs: http://support.microsoft.com/kb/936625 Also, someone else had a similar problem and solved it by reinstalling WDS: http://social.technet.microsoft.com/Forums/en-US/winserversetup/thread/c9bae966-017a-478f-aed5-a723b4619615
Free Windows Admin Tool Kit Click here and download it now
November 27th, 2010 2:30am

A few questions for you: Is the firewall blocking port 4011 on the server? Have you tried Restarting the WDS Server Service? Do you get errors if you open the WDS MMC from Administrative Tools? Also, I would enable logging for WDS if you haven't already and review the logs: http://support.microsoft.com/kb/936625 Also, someone else had a similar problem and solved it by reinstalling WDS: http://social.technet.microsoft.com/Forums/en-US/winserversetup/thread/c9bae966-017a-478f-aed5-a723b4619615
November 27th, 2010 2:30am

Here are my answers: 1. The firewall is disabled on the server. 2. Restarting and Reinstalling the WDS and PXE many times already (including rebooting the servers) 3. No error when I open the WDS MMC. I can see all tabs in the MMC without any issues. I'll enable the WDS logging and send out any error. I have tried that post but didn't help. Shouldn't the test computer get an ip from the dhcp server even if there is any CM OSD issues such as boot image not available and so on? Thanks for the reply. I'm really stuck.
Free Windows Admin Tool Kit Click here and download it now
November 28th, 2010 8:01pm

Hi, This issue can occur when the DHCP server has the following Dynamic Host Configuration Protocol (DHCP) options set: #60 = Client Identifier (set to "PXEClient") #66 = Boot Server Host Name #67 = BootFile Name When the initial DHCP offer from the DHCP server contains these boot options, an attempt is made to connect to port 4011 on the DHCP server. Important: Microsoft does not support the use of these options on a DHCP server to redirect PXE clients To resolve this issue, you must remove these options from the DHCP server and configure the routers IP helper table to contain the IP address of the RIS server. See more details in: http://support.microsoft.com/kb/259670/en-us Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
November 28th, 2010 10:12pm

Hi Eric, Thanks for the reply. Since I have DHCP, WDS, PXE and SCCM all on the same server, from the instructions I have I think I need to run "wdsutil /set-server /usedhcpports:no /dhcpoption60:yes", which enables the 060 PXEClient option in the DHCP configuration. Are you saying I need to remove this 060 option from our DHCP? Does that mean I don't need the /dhcpoption60:yes part of the above command? What should the RIS server be in my case, the DHCP/WDS/PXE/SCCM server since I have everything running on one server? THANKS.
Free Windows Admin Tool Kit Click here and download it now
November 29th, 2010 1:07pm

Personally, I would put DHCP on its own server, separate from SCCM and WDS. This would keep IIS off of your DHCP server and improve security, while reducing configuration complexity. That said, since DHCP and WDS are on the same server, you need option 60 and "do not listen on port 67" configured on the DHCP tab. Is it confgured to Respond to all client computers on the PXE Response tab?
November 29th, 2010 3:16pm

I can ask if I can offload dhcp to the Exchange or SQL servers. But I think the odd is not there. We don't have that many servers in the office, only DC, Exch, SQL and this sccm site server. No, it is set to "Do not respond to any client computers" in WDS. But shouldn't this be left for SCCM to configure? In the CM console, the site server is set to "Allow this PXE service point to respond to incoming PXE requests". I can try manually check "Do not respond to any client computers" in WDS and then restart WDS. I'll report back. I have turned on WDS logging. So far I haven't seen any errors/warnings/failures. THANKS.
Free Windows Admin Tool Kit Click here and download it now
November 29th, 2010 3:32pm

Finally works. I did everything from scratch a few more times and it started to work.
December 3rd, 2010 12:20pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics