Hello, I am running Windows 2003 Enterprise SP2. I've been trying to figure out why RRAS was not able to get IP Addresses from DHCP. I came across a random post online that asked if the user was running WDS on the same server, which I am. I stopped WDS, started RRAS, and RRAS started working correctly. There appears to be a conflict when running WDS and RRAS on the same server. I guess this makes sense because they both hand out IP addresses to their clients. So, my question is, is there a way to get both WDS and RRAS to peacefully coexist on the same server? Thanks in advance! Joe Rojas

Hi Joe, Thanks for posting in Microsoft TechNet forums. As I understand that you set WDS and RRAS on the same server, you encountered the problem of conflicts between WDS and RRAS. If I misunderstand, please feel free to let me know. Based on my research, this issue occurs because both RRAS and the WDS server create socket that binds to the same address/port by using setsockopt with SO_REUSERADDR (in our scenario it is the UDP:67 port). In this case, both RRAS and WDS server can receive the UDP packets which is broadcast by the PXE client. In order for the WDS and RRAS to be supported on the same server, the RRAS should be first allowed to create a socket and bind to port 67, then WDS should reuse the address before bind. If the WDS server has started first and is listening on the port 67, when Relay Agent starts, it reuses the address to listen on the port 67. As a simple work around, you can stop WDS service, start RRAS service, then start WDS service. Then you should be able to use WDS and RRAS at the same time. Alternatively, you can take the following steps to configure WDS and DHCP in your scenarios: If the WDS is working in Legacy mode, the work aground steps are: 1) Set REG key HKLM\System\CCS\Services\WDSServer\Providers\WDSPXE\UseDhcpPorts to 0 to stop the port 67 listening by WDS. 2) In DHCP server, set tag#66 to IP address of the WDS server and set #67 to boot file “OSChooser\i386\startrom.com” Note: this workaround method doesn’t support multi WDS server referral feature. If the WDS is working in Mix mode, the scenarios will be supported more fine: 1) Set REG key HKLM\System\CCS\Services\WDSServer\Providers\WDSPXE\UseDhcpPorts to 0 to stop the port 67 listening by WDS. 2) In DHCP server, set tag#66 to IP address of the WDS server and set #67 to the boot file name like “boot\x86\wdsnbp.com” In this case, even there are more than one WDS servers exist, the referral function will lead client to the right WDS server. Best Regards Dale Qiao TechNet Subscriber Support in forum. If you have any feedback on our support, please contact tngfb@microsoft.com 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.

Dale, Thank you for your help. Your solution worked perfectly!

I'm glad to see the issue was resolved. Cheers~ Best Regards Dale Qiao TechNet Subscriber Support in forum. If you have any feedback on our support, please contact tngfb@microsoft.comPlease 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.