You receive an error message when you try to move a DHCP database by using Netsh.exe on Windows Server 2003

Article translations Article translations
Article ID: 885687 - View products that this article applies to.
Expand all | Collapse all

SUMMARY

This article describes an issue that occurs when you try to move a Dynamic Host Configuration Protocol (DHCP) database by using an export operation followed by an import operation with the Netsh.exe command prompt tool. This issue occurs when you export a DHCP database on a Microsoft Windows Server 2003-based computer, and then import the DHCP database on another server that has a different language version of Windows Server 2003.

SYMPTOMS

If you use the Netsh.exe tool to export and then import a DHCP server database between different language versions of Windows Server 2003, the import process does not succeed. The Netsh.exe tool reports a conflict with class names. Additionally, you receive the following error message:
Error while importing class "Default BOOTP Class". This class conflicts with the existing class "Default BOOTP Class".
Note This message is different depending on the language version of Windows Server 2003 that you have.

CAUSE

This issue occurs if the following conditions are true.
  • The version of Windows Server 2003 where the DHCP data is exported is a different language version than the version of Windows Server 2003 where the DHCP data is imported.
This problem occurs on the German language versions of Windows Server 2003 if either of the following conditions is true.
  • You try to import DHCP data that was exported from a Microsoft Windows 2000 Server-based computer. Additionally, this computer has been recently upgraded to Windows Server 2003.
  • You try to import DHCP data on a computer that was upgraded from Windows 2000 Server to Windows Server 2003. Additionally, the server that exported the DHCP data is a Windows Server 2003-based computer.

RESOLUTION

To resolve this issue, delete the DHCP classes that are from the original language version of Windows server, and then add the correct DHCP classes for the current language version of Windows Server 2003. To do this, follow these steps.

Note In the following example, the server that the DHCP database is exported from has an IP address of 169.168.2.1 and is the English version of Windows Server 2003. The server that the DHCP database is imported to has an IP address of 10.10.0.1 and is the German language version of Windows Server 2003.
  1. Create a dump file on the server where you want to export the DHCP database. To do this, follow these steps:
    1. Click Start, click Run, type cmd, and then click OK.
    2. At the command prompt, type netsh dhcp server dump > exportdump.txt, and then press ENTER.
    The dump file is named Exportdump.txt and it should look similar to the following dump file:
    # ==============================================================
    # Configuration Information for Server 169.168.2.1
    # ==============================================================
    
    # =====================================
    # Add Classes
    # =====================================
    
    Dhcp Server 169.168.2.1 Add Class "Default Routing and Remote Access Class" "User class for remote access clients" 525241532e4d6963726f736f6674 0 b
    Dhcp Server 169.168.2.1 Add Class "Default BOOTP Class" "User class for BOOTP Clients" 424f4f54502e4d6963726f736f6674 0 b
    Dhcp Server 169.168.2.1 Add Class "Microsoft Windows 2000 Options" "Microsoft vendor-specific options for Windows 2000 Clients" 4d53465420352e30 1 b
    Dhcp Server 169.168.2.1 Add Class "Microsoft Windows 98 Options" "Microsoft vendor-specific options for Windows 98 Clients" 4d534654203938 1 b
    Dhcp Server 169.168.2.1 Add Class "Microsoft Options" "Microsoft vendor-specific options applicable to Windows 98 and Windows 2000 Clients" 4d534654 1 b
    
    # =====================================
    # Add Classes End
    # =====================================
    
  2. Create a dump file on the server where you want to import the DHCP data. To do this, follow these steps on the server where you want to import DHCP data:
    1. Click Start, click Run, type cmd, and then click OK.
    2. At the command prompt, type netsh dhcp server dump > importdump.txt, and then press ENTER.
    The dump file is named Importdump.txt and it should look similar to the following dump file:
    # =====================================
    # Klassen hinzufügen
    # =====================================
    
    Dhcp Server 10.10.0.1 Add Class "Standardrouting- und RAS-Klasse" "Benutzerklasse RAS-Clients" 525241532e4d6963726f736f6674 0 b
    Dhcp Server 10.10.0.1 Add Class "Standard BOOTP-Klasse" "Benutzerklasse BOOTP-Clients" 424f4f54502e4d6963726f736f6674 0 b
    Dhcp Server 10.10.0.1 Add Class "Microsoft Windows 2000-Optionen" "Herstellerspezifische Optionen für Microsoft Windows 2000-Clients" 4d53465420352e30 1 b
    Dhcp Server 10.10.0.1 Add Class "Microsoft Windows 98-Optionen" "Herstellerspezifische Optionen für Microsoft Windows 98-Clients" 4d534654203938 1 b
    Dhcp Server 10.10.0.1 Add Class "Microsoft-Optionen" "Herstellerspezifische Optionen für Microsoft Windows 98- und Windows 2000-Clients" 4d534654 1 b
    
    # =====================================
    # Ende - Klassen hinzufügen
    # =====================================
    
  3. Copy the Importdump.txt file to the server where you want to export the DHCP database.
  4. Create a script file. To do this, use any text editor, such as Notepad. This script must do the following:
    1. Create the classes to delete. To do this you must add to the script file the class names and class descriptions that are in the Add Classes section of the export file and are different from the corresponding class names and class descriptions that are in the import file. For example, note the following line from the Exportdump.txt file:
      Dhcp Server 169.168.2.1 Add Class "Default Routing and Remote Access Class" "User class for remote access clients" 525241532e4d6963726f736f6674 0 b
      Note the corresponding line from the Importdump.txt file:
      Dhcp Server 10.10.0.1 Add Class "Standardrouting- und RAS-Klasse" "Benutzerklasse RAS-Clients" 525241532e4d6963726f736f6674 0 b
      From this example, the class name for the Exportdump.txt file is "Default Routing and Remote Access Class". Conversely, the class name for the Importdump.txt file is "Standardrouting- und RAS-Klasse". Additionally, the description name for the Exportdump.txt file is "User class for remote access clients". Conversely, the description name for the Importdump.txt file is "Benutzerklasse RAS-Clients".
    2. Add the netsh command at the beginning of each line in the script where you will delete a class.
    3. Change the netsh command keyword from Add to Delete for each line of text in the script where you will delete a class.
    4. Create the classes to add. To do this you must add to the script file the class names and class descriptions that are in the Add Classes section of the import file and that are different from the corresponding class names and class descriptions that are in the export file.
    5. Add the netsh command at the beginning of each line in the script for each line of text where you will add a class.
    6. Change the IP address to the IP address of the server that you want to export the DHCP database to. Do this for each line in the script where you will add a class.
    In this example, the script must look similar to the following script:
    # ------------------ start of resulting script -----------------
    # Script to delete and add classes with NETSH
    
    # ===== Delete old classes ======
    
    netsh Dhcp Server 169.168.2.1 Delete Class "Default Routing and Remote Access Class" "User class for remote access clients" 525241532e4d6963726f736f6674 0 b
    netsh Dhcp Server 169.168.2.1 Delete Class "Default BOOTP Class" "User class for BOOTP Clients" 424f4f54502e4d6963726f736f6674 0 b
    netsh Dhcp Server 169.168.2.1 Delete Class "Microsoft Windows 2000 Options" "Microsoft vendor-specific options for Windows 2000 Clients" 4d53465420352e30 1 b
    netsh Dhcp Server 169.168.2.1 Delete Class "Microsoft Windows 98 Options" "Microsoft vendor-specific options for Windows 98 Clients" 4d534654203938 1 b
    netsh Dhcp Server 169.168.2.1 Delete Class "Microsoft Options" "Microsoft vendor-specific options applicable to Windows 98 and Windows 2000 Clients" 4d534654 1 b
    
    # ===== End delete old classes =====
    
    # ===== Add new classes =====
    
    netsh Dhcp Server 169.168.2.1 Add Class "Standardrouting- und RAS-Klasse" "User class for remote access clients" 525241532e4d6963726f736f6674 0 b
    netsh Dhcp Server 169.168.2.1 Add Class "Standard BOOTP-Klasse" "User class for BOOTP Clients" 424f4f54502e4d6963726f736f6674 0 b
    netsh Dhcp Server 169.168.2.1 Add Class "Microsoft Windows 2000-Optionen" "Herstellerspezifische Optionen für Microsoft Windows 2000-Clients" 4d53465420352e30 1 b
    netsh Dhcp Server 169.168.2.1 Add Class "Microsoft Windows 98-Optionen" "Herstellerspezifische Optionen für Microsoft Windows 98-Clients" 4d534654203938 1 b
    netsh Dhcp Server 169.168.2.1 Add Class "Microsoft-Optionen" "Herstellerspezifische Optionen für Microsoft Windows 98- und Windows 2000-Clients" 4d534654 1 b
    
    #===== End Add new classes =====
    
    # ------------------ end of resulting script -----------------
    
    
  5. Save the script file with a .bat file name extension. For example, save the file as Addclass.bat.
Warning Running this script with information that is not correct can leave your computer in an unstable state. Before you run this script, we recommend that you back up the complete DHCP folder and all its subfolders. The DHCP folder is located in the c:\SystemRoot\System32\DHCP folder.

MORE INFORMATION

The names of the standard DHCP classes are localized for the Windows Server 2003-based language version. The class names and class descriptions may change because of a language version upgrade on the Windows Server 2003-based computer.

DHCP classes have binary data that is associated with them. The data must be unique for each class. When a Windows-based server is installed, the default classes are created. When a Netsh.exe import process is running, Netsh.exe checks for conflicts between the server's classes and the classes that are defined in the exported DHCP database. If the class names are the same, no conflict is detected, and the Netsh.exe import process continues. However, if the class names are different, a conflict is found, and the Netsh.exe import process is stopped. For additional information about related topics, click the following article numbers to view the articles in the Microsoft Knowledge Base:
283318 Cannot export and then import a DHCP server database between different language versions of Windows Server 2003
281626 How to use the Netsh utility to export and import DHCP scopes
325473 How to move a DHCP database from a computer that is running Windows NT Server 4.0, Windows 2000, or Windows Server 2003 to a computer that is running Windows Server 2003
130642 How to move a DHCP database to another Windows server

Properties

Article ID: 885687 - Last Review: December 3, 2007 - Revision: 2.3
APPLIES TO
  • Microsoft Windows Server 2003, Enterprise Edition (32-bit x86)
  • Microsoft Windows Server 2003, Standard Edition (32-bit x86)
  • Microsoft Windows Server 2003, Datacenter Edition (32-bit x86)
  • Microsoft Windows Server 2003, Enterprise x64 Edition
  • Microsoft Windows Server 2003, 64-Bit Datacenter Edition
  • Microsoft Windows Small Business Server 2003 Standard Edition
  • Microsoft Windows Small Business Server 2003 Premium Edition
Keywords: 
kbwinservnetwork kbnetwork kbtshoot kbprb KB885687

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com