Article ID: 923492
Article Last Modified on 10/11/2007
APPLIES TO
- Microsoft Windows Server 2003 SP1, when used with:
- Microsoft Windows Server 2003, Standard Edition (32-bit x86)
- Microsoft Windows Server 2003, Enterprise Edition
- Microsoft Windows Server 2003, Standard x64 Edition
- Microsoft Windows Server 2003, Enterprise x64 Edition
- Microsoft Windows Server 2003, Enterprise Edition for Itanium-based Systems
SYMPTOMS
Consider the following scenario. On a Microsoft Windows Server 2003 Service Pack 1 (SP1)-based server, you use the netsh dump command to export a Dynamic Host Configuration Protocol (DHCP) server configuration to a file. You then use the netsh exec command to import this same configuration file to a different DHCP server.
In this scenario, the configuration file that you import may lead to wrong values in the Byte option values. Additionally, there is no error message when you import the configuration.
RESOLUTION
Service pack information
To resolve this problem, obtain the latest service pack for Windows Server 2003. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
889100 How to obtain the latest service pack for Windows Server 2003
Hotfix information
Prerequisites
You must have Windows Server 2003 SP1 installed to apply this hotfix.
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 item in Control Panel.
Windows Server 2003 with SP1, x86-based versions
File name | File version | File size | Date | Time | Platform |
---|---|---|---|---|---|
Dhcpmon.dll | 5.2.3790.2762 | 386,048 | 02-Aug-2006 | 17:24 | x86 |
Windows Server 2003 with SP1, x64-based versions
File name | File version | File size | Date | Time | Platform | SP requirement | Service branch |
---|---|---|---|---|---|---|---|
Dhcpmon.dll | 5.2.3790.2762 | 475,136 | 02-Aug-2006 | 03:10 | x64 | SP1 | Not Applicable |
Wdhcpmon.dll | 5.2.3790.2762 | 386,048 | 02-Aug-2006 | 03:10 | x86 | SP1 | WOW |
Windows Server 2003 with SP1, Itanium-based versions
File name | File version | File size | Date | Time | Platform | SP requirement | Service branch |
---|---|---|---|---|---|---|---|
Dhcpmon.dll | 5.2.3790.2762 | 650,240 | 02-Aug-2006 | 03:13 | IA-64 | SP1 | Not Applicable |
Wdhcpmon.dll | 5.2.3790.2762 | 386,048 | 02-Aug-2006 | 03:13 | x86 | SP1 | WOW |
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This problem was first corrected in Windows Server 2003 Service Pack 2.
MORE INFORMATION
When you run the netsh dhcp server 10.0.0.1 dump command to create a script file for your current DHCP configuration, you will find output that resembles the following if you use the Byte option values in DHCP:
DHCP Server 10.0.0.1 Scope 192.168.0.0 set optionvalue 222 BYTE 101
Note The 101 value represents the decimal interpretation of the 222 option that was defined as a Byte value.
When you use the netsh Dhcp Server 10.0.0.1 Scope 192.168.0.0 set optionvalue 222 BYTE 101 command to create a new Byte option value or to change an existing one, the 101 value is then interpreted as a hexadecimal value instead of a decimal value. Therefore, the 222 option is set to 0x01, a decimal value of 1, instead of 0x65, a decimal value of 101. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates
Keywords: kbbug kbfix kbqfe kbpubtypekc kbhotfixserver kbwinserv2003sp2fix KB923492