Your RIS client may not be able to obtain an IP address during the PXE restart on Windows Server 2003 and Windows 2000

Support for Windows Server 2003 ended on July 14, 2015

Microsoft ended support for Windows Server 2003 on July 14, 2015. This change has affected your software updates and security options. Learn what this means for you and how to stay protected.

This article has been archived. It is offered "as is" and will no longer be updated.
If you install Remote Installation Services (RIS) and the DHCP Server service on the same server and if the RIS client is across a router, the RIS client may not be able to obtain an IP address during the Pre-Boot Execution Environment (PXE) restart. The RIS client may receive a DHCP OFFER of all zeros. The RIS client may work correctly if you move RIS and DHCP Server to separate computers or if you remove the router.
This problem can occur if you have configured a router to source the DHCP DISCOVER packet with the IP address of the DHCP-and-RIS side of the router instead of with the IP address of the client side of the router. Because the DISCOVER packet is sourced with an address that is on the same subnet as the DHCP-and-RIS server, the DHCP-and-RIS server assumes that the client is prompting for an RIS PXE DISCOVER instead of for a DHCP IP address DISCOVER. The OFFER that the client receives does not contain a valid IP address offer because it is an OFFER for RIS. Because the client does not have an IP address at this point, the OFFER packet is discarded.

Windows Server 2003

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.
No prerequisites are required.
Restart requirement
You do not have to restart your computer after you apply this hotfix.
Hotfix replacement information
This hotfix does not replace any other hotfixes.
File information
The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
Windows Server 2003, 32-bit editions
   Date         Time   Version           Size     File name   --------------------------------------------------------------   23-Jul-2003  18:12  5.2.3790.71       259,584  Dhcpssvc.dll

Windows Server 2003, 64-bit editions
   Date         Time   Version           Size     File name		Platform   -----------------------------------------------------------------------------   23-Jul-2003  18:13  5.2.3790.71       676,864  Dhcpssvc.dll     	IA-64   23-Jul-2003  18:12  5.2.3790.71       259,584  Wdhcpssvc.dll    	X86

Microsoft Windows 2000

There is currently no resolution for Windows 2000.
To work around this problem, move RIS and DHCP Server to separate computers. Alternatively, you can reconfigure the router to source the packet with the same address that is in the giaddr field. This is the RIS client side of the router.
More information
This problem does not occur if you are using a server that is running a computer that is running Microsoft Windows 2000 or Microsoft Windows NT as the router, nor does it occur with many other commercially available routers. To see detailed information of the DHCP traffic, run a network monitor trace.

RIS and DHCP Server know about each other when you install them on the same computer. The router issue that is described in this article only occurs when the services are on the same computer. Moving the services to separate computers causes DHCP Server to act more independently of RIS and to send an IP address OFFER even when it receives a DISCOVER that is sourced with the same subnet address, instead of handing it off to RIS.For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
244036 Description of PXE interaction among PXE client, DHCP, and RIS server
Microsoft has confirmed that this is a bug in the Microsoft products that are listed in the "Applies to" section.

Article ID: 300034 - Last Review: 01/17/2015 15:03:28 - Revision: 6.0

Microsoft Windows Server 2003, Standard Edition (32-bit x86), Microsoft Windows Server 2003, Enterprise Edition (32-bit x86), Microsoft Windows 2000 Server, Microsoft Windows 2000 Advanced Server, Microsoft Windows 2000 Professional Edition

  • kbnosurvey kbarchive kbautohotfix kbhotfixserver kbqfe kbfasttrack kbwinserv2003presp1fix kbprb kbremoteprog w2000ris KB300034
ERROR: at System.Diagnostics.Process.Kill() at Microsoft.Support.SEOInfrastructureService.PhantomJS.PhantomJSRunner.WaitForExit(Process process, Int32 waitTime, StringBuilder dataBuilder, Boolean isTotalProcessTimeout)