Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

Error message on a Windows Server 2003 or a Windows XP computer trying to join a Windows Server 2003 domain: "Access is denied"


View products that this article applies to.

Source: Microsoft Support

↑ Back to the top


Rapid publishing

RAPID PUBLISHING ARTICLES PROVIDE INFORMATION DIRECTLY FROM WITHIN THE MICROSOFT SUPPORT ORGANIZATION. THE INFORMATION CONTAINED HEREIN IS CREATED IN RESPONSE TO EMERGING OR UNIQUE TOPICS, OR IS INTENDED SUPPLEMENT OTHER KNOWLEDGE BASE INFORMATION.

↑ Back to the top


Symptom



�When a Windows Server 2003 or a Windows XP computer tries to join a Windows Server 2003 domain, the following error message is received:

The following error occurred attempting to join the domain "domain_name":

Access is denied.

↑ Back to the top


Cause



In the Netsetup.log file, I get the following:



09/21 15:09:19 NetpValidateName: checking to see if 'domain_name' is valid as type 3 name

09/21 15:09:19 NetpCheckDomainNameIsValid [ Exists ] for 'domain_name' returned 0x0

09/21 15:09:19 NetpValidateName: name 'domain_name' is valid for type 3

09/21 15:09:19 NetpDsGetDcName: trying to find DC in domain 'domain_name', flags: 0x1020

09/21 15:09:22 NetpDsGetDcName: failed to find a DC having account 'account': 0x525 -> Access denied

09/21 15:09:22 NetpDsGetDcName: found DC '\\DC-NM.domain_name' in the specified domain

09/21 15:09:22 NetUseAdd to \\DC-NM.domain_name\IPC$ returned 5

09/21 15:09:22 NetpJoinDomain: status of connecting to dc '\\DC-NM.domain_name': 0x5

09/21 15:09:22 NetpDoDomainJoin: status: 0x5

↑ Back to the top


Resolution



On the member server or client machine, we enabled the following policies:

  • Microsoft network client: Digitally sign communications (if server agrees)

  • Microsoft network server: Digitally sign communications (if client agrees)


After that, we rebooted the member servers or client machines. Then we successfully joined those machines to the domain.

↑ Back to the top


Disclaimer

MICROSOFT AND/OR ITS SUPPLIERS MAKE NO REPRESENTATIONS OR WARRANTIES ABOUT THE SUITABILITY, RELIABILITY OR ACCURACY OF THE INFORMATION CONTAINED IN THE DOCUMENTS AND RELATED GRAPHICS PUBLISHED ON THIS WEBSITE (THE �MATERIALS�) FOR ANY PURPOSE. THE MATERIALS MAY INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS AND MAY BE REVISED AT ANY TIME WITHOUT NOTICE.

TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, MICROSOFT AND/OR ITS SUPPLIERS DISCLAIM AND EXCLUDE ALL REPRESENTATIONS, WARRANTIES, AND CONDITIONS WHETHER EXPRESS, IMPLIED OR STATUTORY, INCLUDING BUT NOT LIMITED TO REPRESENTATIONS, WARRANTIES, OR CONDITIONS OF TITLE, NON INFRINGEMENT, SATISFACTORY CONDITION OR QUALITY, MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, WITH RESPECT TO THE MATERIALS.

↑ Back to the top


Note This is a "FAST PUBLISH" article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use for other considerations.

↑ Back to the top


Keywords: kbnosurvey, kbarchive, kbrapidpub, kbnomt, KB969264

↑ Back to the top

Article Info
Article ID : 969264
Revision : 2
Created on : 1/15/2015
Published on : 1/15/2015
Exists online : False
Views : 265