![]() The errors occur if NT4Emulator is set to 0x1 in the following registry subkey of the helper domain controller used to join the target domain: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Netlogon\Parameters You can also successfully join the same Windows Server 2008 R2 machine to a different Active Directory domain in the same forest specifying the FQDN domain name. NetpLoadParameters: DNSNameResolutionRequired not found, defaulting to '1' 0x2 NetpLoadParameters: DomainCompatibilityMode not found, defaulting to '0' 0x2 NetpLoadParameters: status: 0x2 NetpValidateName: checking to see if 'Domain_Name' is valid as type 3 name NetpValidateName: 'Domain_Name' is not a valid Dns domain name: 0x2554 NetpCheckDomainNameIsValid for 'Domain_Name' returned 0x0 NetpValidateName: name 'Domain_Name' is valid for type 3 NetpDsGetDcName: trying to find DC in domain 'Domain_Name', flags: 0x40001010 NetpDsGetDcName: failed to find a DC in the specified domain: 0x54b, last error is 0x0 NetpJoinDomainOnDs: NetpDsGetDcName returned: 0x54b NetpJoinDomainOnDs: Function exits with status of: 0x54b NetpDoDomainJoin: status: 0x54bĭomain joins by Windows Server 2003 computers to the same target domain succeed by specifying the NetBIOS domain name in the domain join UI. NetpDoDomainJoin NetpMachineValidToJoin: 'CLIENT-NAME' OS Version: 6.1 Build number: 7600 (7600.win7_rtm.090713-1255) SKU: Windows Server 2008 R2 Enterprise NetpDomainJoinLicensingCheck: ulLicenseValue=1, Status: 0x0 NetpGetLsaPrimaryDomain: status: 0x0 NetpMachineValidToJoin: status: 0x0 NetpJoinDomain Machine: CLIENT-NAME Domain: Domain_Name MachineAccountOU: (NULL) Account: Domain_Name\admx054085 Options: 0x27 NetpLoadParameters: loading registry parameters. The specified domain either does not exist or could not be contacted. The following error occurred attempting to join the domain. When trying to join the Windows Server 2008 R2 computer to the domain by specifying the NetBIOS name in the domain join UI, you receive a different error: NetpValidateName: checking to see if is valid as type 3 name NetpCheckDomainNameIsValid for returned 0x54b, last error is 0x0 NetpCheckDomainNameIsValid for returned 0x54b NetpValidateName: checking to see if 'CLIENT-NAME' is valid as type 5 name NetpValidateName: name 'CLIENT-NAME' is valid for type 5 NetpValidateName: checking to see if 'CLIENT-NAME' is valid as type 1 name NetpCheckNetBiosNameNotInUse for 'CLIENT-NAME' returned 0x0 NetpValidateName: name 'CLIENT-NAME' is valid for type 1 In the %windir%\debug\Netsetup.log on the client you see the following sequence: When trying to join the Windows Server 2008 R2 machine to the domain by specifying the fully qualified domain name (FQDN) in the domain join UI, the operation fails and you receive the error:Īn Active Directory Domain Controller (AD DC) for the domain couldn't be contactedĮnsure that the domain name is typed correctly The destination domain has either Windows 2000, Windows Server 2003, or Windows Server 2008 domain controllers and may have Windows NT 4.0 domain controllers present. You try to join a Windows Server 2008 R2 or a Windows 7 machine to an Active Directory domain using Computer Name/Domain Changes under System Properties. This article helps fix an issue where users can't join a computer to an Active Directory domain.Īpplies to: Windows 7 Service Pack 1, Windows Server 2012 R2 Original KB number: 2008652 Symptoms
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |