Select the product you need help with
- Internet Explorer
- Windows Phone
- More products
Error message when you try to make a remote connection to the registry of a Windows-based computer from a Windows Server 2003 SP1-based computer: "Access denied"
Article ID: 913327 - View products that this article applies to.
When you try to make a remote connection to the registry of a Microsoft Windows-based computer from a Microsoft Windows Server 2003 Service Pack 1 (SP1)-based computer, you receive the following error message:
This issue may prevent you from using the following programs to deploy agents or clients:
This issue occurs because of security changes that are included in Windows Server 2003 SP1.
Service pack informationTo 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:
(http://support.microsoft.com/kb/889100/ )How to obtain the latest service pack for Windows Server 2003
Hotfix informationA 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:
http://support.microsoft.com/contactus/?ws=supportNote 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.
PrerequisitesYou must be running Windows Server 2003 SP1 to apply this hotfix.
Note x64-based versions of Windows Server 2003 do not require this service pack.
Restart requirementYou must restart the computer after you apply this hotfix. Also, a restart is required after you make the registry key change that is described in the "To enable the hotfix" section.
Hotfix replacement informationThis hotfix does not replace any other hotfixes.
File informationThe 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, x86-based versions
Collapse this tableExpand this table
Windows Server 2003, x64-based versions
Collapse this tableExpand this table
Registry informationImportant This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/322756/ )How to back up and restore the registry in Windows
To enable the hotfix, add the DontUseSecureNPForRemote entry to the following registry subkey. Then, set this entry to a value of 1.
To do this, follow these steps:
If the failure auditing of the "Audit logon events" policy is enabled, Event 529 may also be logged several times per second in the security event log of the cluster node:
Event Type: Failure Audit
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 Microsoft Windows Server 2003 Service Pack 2.
The issue that is described in the "Symptoms" section may affect programs that use the WnetConnection2 function to connect to a Windows-based computer from a Windows Server 2003 SP1-based computer. Specifically, this issue may occur if the following conditions are true:
(http://support.microsoft.com/kb/824684/ )Description of the standard terminology that is used to describe Microsoft software updates
Article ID: 913327 - Last Review: July 6, 2011 - Revision: 7.0