The "netsh" command changes the Byte option value when you export and then import a DHCP server configuration file in Windows Server 2003 SP1 (923492)



The information in this article applies to:

  • Microsoft Windows Server 2003 SP1, when used with:
    • Microsoft Windows Server 2003, Standard Edition
    • 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

Hotfix information

A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Windows Server 2003 service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

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 nameFile versionFile sizeDateTimePlatform
Dhcpmon.dll5.2.3790.2762386,04802-Aug-200617:24x86
Windows Server 2003 with SP1, x64-based versions
File nameFile versionFile sizeDateTimePlatformSP requirementService branch
Dhcpmon.dll5.2.3790.2762475,13602-Aug-200603:10x64SP1Not Applicable
Wdhcpmon.dll5.2.3790.2762386,04802-Aug-200603:10x86SP1WOW
Windows Server 2003 with SP1, Itanium-based versions
File nameFile versionFile sizeDateTimePlatformSP requirementService branch
Dhcpmon.dll5.2.3790.2762650,24002-Aug-200603:13IA-64SP1Not Applicable
Wdhcpmon.dll5.2.3790.2762386,04802-Aug-200603:13x86SP1WOW

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

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


Modification Type:MajorLast Reviewed:8/18/2006
Keywords:kbBug kbfix kbQFE kbhotfixserver kbpubtypekc KB923492 kbAudITPRO