This issue has been posted a number of times beofre but I am unable to solve my problem - during PXE boot -I get DHCP address then this error- "pxe-e55 proxydhcp service did not reply to request on port 4011 ". I have got WDS installed (with do not listen to port 67), os images wim file are added to the OS files, task sequence created and advertised on a collection on which it has the computer's MAC address. Also DHCP has option 60 as PXEClient (SCCM and DHCP on the same server). Unblocked all PXE certificates on SCCM. Few ppl solved it by re-installing WDS/other servicesc but I do not want to uninstall anything services. Thanks

Hi, For error "pxe-e55 proxydhcp service did not reply to request on port 4011 " 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. This offer fails if the PXE server is on another computer. 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. PXE clients computers do not start when you configure the Dynamic Host Configuration Protocol server to use options 60, 66, 67 http://support.microsoft.com/kb/259670/en-usPlease 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.

Hi Eric Why/How do I configure the routers IP helper table? I have got WDS, SCCM, DHCP and Domain controller on the same server. thanks

Hi sshoaib, I got this issue before... Some say that this issue is because of the options 60, 66 & 67 in the DHCP... But without them, you'll face problems... My problem was simply solved by restarting the WDS service... So restart it & check what happens...MCTS, MCP

I restarted the server - it did not help

Check the WDS configuration...MCTS, MCP

This is my WDS config: Respond to all client (known and unknown) - does not require administrator password... DHCP: (1) Do not listen on port 67 ticked on and (2) Configure DHCP options 60 to inidicate that this server is also a PXE server - ticked on On my DHCP server: 60: PXEClient 66: Name of the server 67: not configured thanks

re-installed DHCP, WDS and SCCM PXE Service Point - no success. I am guessing the issue is with the SCCM itself

Try configuring Option 67 with the string "boot.com"... Also, Can you tell us which version of the boot image are you using... (X86) or (X64) ?!!!MCTS, MCP

Adding the option 67 with boot.com did not help. The boot image (in SCCM task sequence) is x86 - thanks

On my DHCP server: 60: PXEClient 66: Name of the server 67: not configured Remove option 60 and set 67 to SMSboot\x86\wdsnbp.com

Hi Tordten tried your suggestions - now I get this error: TFTP PXE-T04: Access violation PXE-E36 Error received from TFTP server PXE-M0F - Exiting broadcom PXE ROM

hi, 1) Are your clients located in another VLAN than your WDS server ? 2) After having added the WDS role on your server, did you configured it (opened WDS console and then right click on the server) ? 3) after having added the "PXE service point" in SCCM, have you added boot images on the SMSPXEDistribution point ? Régis

Hi Avironix2 1. Same VLAN 2. On WDS - 'do not listen on port 67' is ticked on and un-ticked dhcp 60 as Torsten suggested. Turned on - 'respond to all known and unknown computers' 3. I am using the SCCM default x86 image for PXE boot and Task sequence has a custom wim file for OS deployment thanks

I re-installed sccm and now have dhcp and sql on different machines. All good now.