"Access denied" error message when you use the "netsh dhcp server import" command to import a DHCP database from a Windows NT Server 4.0-based computer to a Windows Server 2003-based computer

Consider the following scenario. You are migrating a Dynamic Host Configuration Protocol (DHCP) database from a Microsoft Windows NT Server 4.0-based computer to a Microsoft Windows Server 2003-based computer. On the Windows Server 2003-based computer, you receive an "Access denied" error message when you try to import the DHCP database by using the following command:Note The text string C:\dhcpdatabase.txt is a placeholder for the name and path of the import file that you want to use.

When this problem occurs, the following event may appear in the System log in Event Viewer: For more information about how to import a DHCP database from a Windows NT Server 4.0-based computer to a Windows Server 2003-based computer, click the following article number to view the article in the Microsoft Knowledge Base:

This problem occurs when the user account that is being used to import the DCHP database is not an explicit member of the local Administrators group of the source DHCP server. For example, you may experience this problem with a user account that belongs to the Domain Admins group that is a member of the local Administrators group of the destination DHCP server.

Note This problem occurs only with the DHCP IMPORT and EXPORT commands. When this problem occurs, you are still able to perform all other database administrative and configuration operations on the Windows Server 2003-based destination DHCP server.

To work around this problem, log on as a user who is an explicit member of the local Administrators group of the source DHCP server. When you do this, the following commands will work as you expect:

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:

Hotfix information

You can also resolve this problem by obtaining the hotfix that is described in the following article in the Microsoft Knowledge Base:

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

For more information about how to use the Netsh utility, click the following article number to view the article in the Microsoft Knowledge Base: