none
加域报错 RRS feed

  • Question

  • 加域报错:将该计算机的主域DNS名称更改为“失败,名称任然为”域名。错误为:远程过程调用失败且未执行

    两台2012R2 DC,客户端无论win7 还是 win10 目前加域提示上面的报错,重启客户端后,也正常加入到域,但是输入域用户登录时,提示服务器上的安全数据库没有此工作站信任关系的计算机账号。在DC上的用户和计算机中可以看到该客户端,dns中也注册到了该主机,退域加域依旧无法解决该问题

    Thursday, July 15, 2021 8:08 AM

All replies

  • 您好,

    非常感谢您的发帖。

    我之前在测试环境中遇到相同的情况,加域成功后,输入域用户登录时,有报错。我当时的情况是,把相同名称的计算机加入域中,所以导致了这样的情况。

    上面的情况下,在加域的过程中会有提示:网络中有重名存在,必须选择一个不用的名称。



    按照我们的描述,我们加域时的报错是远程过程调用失败且未执行。请先确保计算机的首选DNS server是否配置正确。如果我们的DC也是DNS服务器的话,首选DNS服务器将配置为DC的IP地址。其次,加域失败的话,我们可以查看此日志C:\Windows\Debug\Netsetup.log。里面会记录加域过程以及失败的原因。请帮忙检查下,并告知里面的报错信息。

    另外也建议检查下DC的健康状态和AD复制状态。请在两台DC上运行以下命令查看:

    Dcdiag /v
    repadmin /showrepl
    repadmin /replsum


    如有问题,请随时联系我们。

    Best regards,
    Hannah Xiong


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.


    Thursday, July 15, 2021 8:57 AM
  • hi 很高兴看到你的回复,

    1:客户端的首选DNS是域控的IP地址,DC与DNS为同一服务器,此设置没有问题。

    输入域名后,可以弹出身份验证对话框,输入用户名、密码后,也提示加域成功,接下来会显示:

    :将该计算机的主域DNS名称更改为“失败,名称任然为”域名。错误为:远程过程调用失败且未执行

    客户端重启后,输入域账号密码提示“服务器上的安全数据库没有此工作站信任关系的计算机账号”

    DC上也能有该主机的A记录以及计算机对象

    2:通过dcdiag命令检查,所有测试均通过无误

    3:复制的情况也没有问题,

    4:日志上传如下

    07/15/2021 15:07:53:364 -----------------------------------------------------------------
    07/15/2021 15:07:53:364 NetpDoDomainJoin
    07/15/2021 15:07:53:365 NetpDoDomainJoin: using new computer names
    07/15/2021 15:07:53:365 NetpDoDomainJoin: NetpGetNewMachineName returned 0x0
    07/15/2021 15:07:53:365 NetpMachineValidToJoin: 'WIN-950TL3QU0MA'
    07/15/2021 15:07:53:367 NetpMachineValidToJoin: status: 0x0
    07/15/2021 15:07:53:367 NetpJoinWorkgroup: joining computer 'WIN-950TL3QU0MA' to workgroup 'WORKGROUP'
    07/15/2021 15:07:53:367 NetpValidateName: checking to see if 'WORKGROUP' is valid as type 2 name
    07/15/2021 15:07:53:375 NetpCheckNetBiosNameNotInUse for 'WORKGROUP' [ Workgroup as MACHINE]  returned 0x0
    07/15/2021 15:07:53:375 NetpValidateName: name 'WORKGROUP' is valid for type 2
    07/15/2021 15:07:53:391 NetpJoinWorkgroup: status:  0x0
    07/15/2021 15:07:53:391 NetpDoDomainJoin: status: 0x0
    07/15/2021 15:16:42:525 -----------------------------------------------------------------
    07/15/2021 15:16:42:527 NetpValidateName: checking to see if 'DJ-TRAINING' is valid as type 1 name
    07/15/2021 15:16:42:531 NetpCheckNetBiosNameNotInUse for 'DJ-TRAINING' [MACHINE] returned 0x0
    07/15/2021 15:16:42:531 NetpValidateName: name 'DJ-TRAINING' is valid for type 1
    07/15/2021 15:16:42:535 -----------------------------------------------------------------
    07/15/2021 15:16:42:535 NetpValidateName: checking to see if 'DJ-training' is valid as type 5 name
    07/15/2021 15:16:42:535 NetpValidateName: name 'DJ-training' is valid for type 5
    07/15/2021 15:44:04:180 -----------------------------------------------------------------
    07/15/2021 15:44:04:181 NetpValidateName: checking to see if 'DJERXIAN-TRAINI' is valid as type 1 name
    07/15/2021 15:44:07:192 NetpCheckNetBiosNameNotInUse for 'DJERXIAN-TRAINI' [MACHINE] returned 0x0
    07/15/2021 15:44:07:192 NetpValidateName: name 'DJERXIAN-TRAINI' is valid for type 1
    07/15/2021 15:44:07:198 -----------------------------------------------------------------
    07/15/2021 15:44:07:198 NetpValidateName: checking to see if 'DJerxian-training' is valid as type 5 name
    07/15/2021 15:44:07:198 NetpValidateName: name 'DJerxian-training' is valid for type 5
    07/15/2021 15:44:18:389 -----------------------------------------------------------------
    07/15/2021 15:44:18:389 NetpValidateName: checking to see if 'DJEX-TRAINING' is valid as type 1 name
    07/15/2021 15:44:21:435 NetpCheckNetBiosNameNotInUse for 'DJEX-TRAINING' [MACHINE] returned 0x0
    07/15/2021 15:44:21:435 NetpValidateName: name 'DJEX-TRAINING' is valid for type 1
    07/15/2021 15:44:21:445 -----------------------------------------------------------------
    07/15/2021 15:44:21:445 NetpValidateName: checking to see if 'DJEX-training' is valid as type 5 name
    07/15/2021 15:44:21:445 NetpValidateName: name 'DJEX-training' is valid for type 5
    07/15/2021 15:53:06:004 -----------------------------------------------------------------
    07/15/2021 15:53:06:005 NetpValidateName: checking to see if 'DJEX-TRAINING' is valid as type 1 name
    07/15/2021 15:53:06:012 NetpCheckNetBiosNameNotInUse for 'DJEX-TRAINING' [MACHINE] returned 0x0
    07/15/2021 15:53:06:012 NetpValidateName: name 'DJEX-TRAINING' is valid for type 1
    07/15/2021 15:53:06:018 -----------------------------------------------------------------
    07/15/2021 15:53:06:018 NetpValidateName: checking to see if 'DJEX-training' is valid as type 5 name
    07/15/2021 15:53:06:018 NetpValidateName: name 'DJEX-training' is valid for type 5
    07/15/2021 15:53:06:021 -----------------------------------------------------------------
    07/15/2021 15:53:06:021 NetpValidateName: checking to see if 'test.com' is valid as type 3 name
    07/15/2021 15:53:06:141 NetpCheckDomainNameIsValid [ Exists ] for 'test.com' returned 0x0
    07/15/2021 15:53:06:141 NetpValidateName: name 'test.com' is valid for type 3
    07/15/2021 15:53:12:859 -----------------------------------------------------------------
    07/15/2021 15:53:12:859 NetpDoDomainJoin
    07/15/2021 15:53:12:859 NetpDoDomainJoin: using current computer names
    07/15/2021 15:53:12:859 NetpDoDomainJoin: NetpGetComputerNameEx(NetBios) returned 0x0
    07/15/2021 15:53:12:859 NetpDoDomainJoin: NetpGetComputerNameEx(DnsHostName) returned 0x0
    07/15/2021 15:53:12:859 NetpMachineValidToJoin: 'DJEX-TRAINING'
    07/15/2021 15:53:12:862 NetpMachineValidToJoin: status: 0x0
    07/15/2021 15:53:12:863 NetpJoinDomain
    07/15/2021 15:53:12:863 HostName: DJEX-training
    07/15/2021 15:53:12:863 NetbiosName: DJEX-TRAINING
    07/15/2021 15:53:12:863 Domain: test.com
    07/15/2021 15:53:12:863 MachineAccountOU: (NULL)
    07/15/2021 15:53:12:863 Account: test.com\root
    07/15/2021 15:53:12:863 Options: 0x25
    07/15/2021 15:53:12:868 NetpValidateName: checking to see if 'test.com' is valid as type 3 name
    07/15/2021 15:53:12:944 NetpCheckDomainNameIsValid [ Exists ] for 'test.com' returned 0x0
    07/15/2021 15:53:12:944 NetpValidateName: name 'test.com' is valid for type 3
    07/15/2021 15:53:12:944 NetpDsGetDcName: trying to find DC in domain 'test.com', flags: 0x40001010
    07/15/2021 15:53:13:839 NetpDsGetDcName: failed to find a DC having account 'DJEX-TRAINING$': 0x525, last error is 0x0
    07/15/2021 15:53:13:855 NetpDsGetDcName: status of verifying DNS A record name resolution for 'Dc-AD02.test.com': 0x0
    07/15/2021 15:53:13:855 NetpDsGetDcName: found DC '\\Dc-AD02.test.com' in the specified domain
    07/15/2021 15:53:13:855 NetpJoinDomainOnDs: NetpDsGetDcName returned: 0x0
    07/15/2021 15:53:13:855 NetpDisableIDNEncoding: using FQDN test.com from dcinfo
    07/15/2021 15:53:13:869 NetpDisableIDNEncoding: DnsDisableIdnEncoding(UNTILREBOOT) on 'test.com' succeeded
    07/15/2021 15:53:13:869 NetpJoinDomainOnDs: NetpDisableIDNEncoding returned: 0x0
    07/15/2021 15:53:14:197 NetpJoinDomainOnDs: status of connecting to dc '\\Dc-AD02.test.com': 0x0
    07/15/2021 15:53:14:197 NetpGetDnsHostName: PrimaryDnsSuffix defaulted to DNS domain name: test.com
    07/15/2021 15:53:14:201 NetpProvisionComputerAccount:
    07/15/2021 15:53:14:201 lpDomain: test.com
    07/15/2021 15:53:14:201 lpHostName: DJEX-training
    07/15/2021 15:53:14:201 lpMachineAccountOU: (NULL)
    07/15/2021 15:53:14:201 lpDcName: Dc-AD02.test.com
    07/15/2021 15:53:14:201 lpMachinePassword: (null)
    07/15/2021 15:53:14:201 lpAccount: test.com\root
    07/15/2021 15:53:14:201 lpPassword: (non-null)
    07/15/2021 15:53:14:201 dwJoinOptions: 0x25
    07/15/2021 15:53:14:201 dwOptions: 0x40000003
    07/15/2021 15:53:14:258 NetpLdapBind: Verified minimum encryption strength on Dc-AD02.test.com: 0x0
    07/15/2021 15:53:14:258 NetpLdapGetLsaPrimaryDomain: reading domain data
    07/15/2021 15:53:14:259 NetpGetNCData: Reading NC data
    07/15/2021 15:53:14:260 NetpGetDomainData: Lookup domain data for: DC=test,DC=com
    07/15/2021 15:53:14:266 NetpGetDomainData: Lookup crossref data for: CN=Partitions,CN=Configuration,DC=test,DC=com
    07/15/2021 15:53:14:272 NetpLdapGetLsaPrimaryDomain: result of retrieving domain data: 0x0
    07/15/2021 15:53:14:273 NetpCheckForDomainSIDCollision: returning 0x0(0).
    07/15/2021 15:53:14:326 NetpGetComputerObjectDn: Unable to bind to DS on '\\Dc-AD02.test.com': 0x6bf
    07/15/2021 15:53:14:326 NetpCreateComputerObjectInDs: NetpGetComputerObjectDn failed: 0x6bf
    07/15/2021 15:53:14:326 NetpProvisionComputerAccount: LDAP creation failed: 0x6bf
    07/15/2021 15:53:14:327 ldap_unbind status: 0x0
    07/15/2021 15:53:14:327 NetpJoinCreatePackagePart: status:0x6bf.
    07/15/2021 15:53:14:327 NetpJoinDomainOnDs: Function exits with status of: 0x6bf
    07/15/2021 15:53:14:327 NetpJoinDomainOnDs: status of disconnecting from '\\Dc-AD02.test.com': 0x0
    07/15/2021 15:53:14:336 NetpResetIDNEncoding: DnsDisableIdnEncoding(RESETALL) on 'test.com' returned 0x0
    07/15/2021 15:53:14:336 NetpJoinDomainOnDs: NetpResetIDNEncoding on 'test.com': 0x0
    07/15/2021 15:53:14:336 NetpDoDomainJoin: status: 0x6bf
    07/15/2021 15:53:14:341 -----------------------------------------------------------------
    07/15/2021 15:53:14:341 NetpDoDomainJoin
    07/15/2021 15:53:14:341 NetpDoDomainJoin: using current computer names
    07/15/2021 15:53:14:341 NetpDoDomainJoin: NetpGetComputerNameEx(NetBios) returned 0x0
    07/15/2021 15:53:14:341 NetpDoDomainJoin: NetpGetComputerNameEx(DnsHostName) returned 0x0
    07/15/2021 15:53:14:341 NetpMachineValidToJoin: 'DJEX-TRAINING'
    07/15/2021 15:53:14:348 NetpMachineValidToJoin: status: 0x0
    07/15/2021 15:53:14:348 NetpJoinDomain
    07/15/2021 15:53:14:348 HostName: DJEX-training
    07/15/2021 15:53:14:348 NetbiosName: DJEX-TRAINING
    07/15/2021 15:53:14:348 Domain: test.com
    07/15/2021 15:53:14:348 MachineAccountOU: (NULL)
    07/15/2021 15:53:14:348 Account: test.com\root
    07/15/2021 15:53:14:348 Options: 0x27
    07/15/2021 15:53:14:354 NetpValidateName: checking to see if 'test.com' is valid as type 3 name
    07/15/2021 15:53:14:438 NetpCheckDomainNameIsValid [ Exists ] for 'test.com' returned 0x0
    07/15/2021 15:53:14:438 NetpValidateName: name 'test.com' is valid for type 3
    07/15/2021 15:53:14:439 NetpDsGetDcName: trying to find DC in domain 'test.com', flags: 0x40001010
    07/15/2021 15:53:15:323 NetpDsGetDcName: failed to find a DC having account 'DJEX-TRAINING$': 0x525, last error is 0x0
    07/15/2021 15:53:15:336 NetpDsGetDcName: status of verifying DNS A record name resolution for 'Dc-AD01.test.com': 0x0
    07/15/2021 15:53:15:336 NetpDsGetDcName: found DC '\\Dc-AD01.test.com' in the specified domain
    07/15/2021 15:53:15:336 NetpJoinDomainOnDs: NetpDsGetDcName returned: 0x0
    07/15/2021 15:53:15:336 NetpDisableIDNEncoding: using FQDN test.com from dcinfo
    07/15/2021 15:53:15:344 NetpDisableIDNEncoding: DnsDisableIdnEncoding(UNTILREBOOT) on 'test.com' succeeded
    07/15/2021 15:53:15:344 NetpJoinDomainOnDs: NetpDisableIDNEncoding returned: 0x0
    07/15/2021 15:53:15:430 NetpJoinDomainOnDs: status of connecting to dc '\\Dc-AD01.test.com': 0x0
    07/15/2021 15:53:15:430 NetpGetDnsHostName: PrimaryDnsSuffix defaulted to DNS domain name: test.com
    07/15/2021 15:53:15:433 NetpProvisionComputerAccount:
    07/15/2021 15:53:15:433 lpDomain: test.com
    07/15/2021 15:53:15:433 lpHostName: DJEX-training
    07/15/2021 15:53:15:433 lpMachineAccountOU: (NULL)
    07/15/2021 15:53:15:433 lpDcName: Dc-AD01.test.com
    07/15/2021 15:53:15:433 lpMachinePassword: (null)
    07/15/2021 15:53:15:433 lpAccount: test.com\root
    07/15/2021 15:53:15:433 lpPassword: (non-null)
    07/15/2021 15:53:15:433 dwJoinOptions: 0x27
    07/15/2021 15:53:15:433 dwOptions: 0x40000003
    07/15/2021 15:53:15:489 NetpLdapBind: Verified minimum encryption strength on Dc-AD01.test.com: 0x0
    07/15/2021 15:53:15:489 NetpLdapGetLsaPrimaryDomain: reading domain data
    07/15/2021 15:53:15:489 NetpGetNCData: Reading NC data
    07/15/2021 15:53:15:492 NetpGetDomainData: Lookup domain data for: DC=test,DC=com
    07/15/2021 15:53:15:492 NetpGetDomainData: Lookup crossref data for: CN=Partitions,CN=Configuration,DC=test,DC=com
    07/15/2021 15:53:15:500 NetpLdapGetLsaPrimaryDomain: result of retrieving domain data: 0x0
    07/15/2021 15:53:15:511 NetpCheckForDomainSIDCollision: returning 0x0(0).
    07/15/2021 15:53:15:555 NetpGetComputerObjectDn: Unable to bind to DS on '\\Dc-AD01.test.com': 0x6bf
    07/15/2021 15:53:15:555 NetpCreateComputerObjectInDs: NetpGetComputerObjectDn failed: 0x6bf
    07/15/2021 15:53:15:555 NetpProvisionComputerAccount: LDAP creation failed: 0x6bf
    07/15/2021 15:53:15:555 NetpProvisionComputerAccount: Retrying downlevel per options
    07/15/2021 15:53:15:829 NetpProvisionComputerAccount: retry status of creating account: 0x0
    07/15/2021 15:53:15:829 NetpDeleteMachineAccountKey: called for computer 'DJEX-TRAINING'
    07/15/2021 15:53:15:862 NetpGetComputerObjectDn: Unable to bind to DS on '\\Dc-AD01.test.com': 0x6bf
    07/15/2021 15:53:15:862 NetpDeleteMachineAccountKey: NetpGetComputerObjectDn failed for computer 'DJEX-TRAINING'. Status: 1727
    07/15/2021 15:53:15:862 NetpDeleteMachineAccountKey: returning Status: 1727 
    07/15/2021 15:53:15:862 NetpProvisionComputerAccount: Attempt at deleting machine auth key failed: 0x6bf.
    07/15/2021 15:53:15:862 ldap_unbind status: 0x0
    07/15/2021 15:53:15:862 NetpJoinCreatePackagePart: status:0x0.
    07/15/2021 15:53:15:863 NetpJoin3CreatePackagePart: RID and\or SID was not found, exiting as a no-op.
    07/15/2021 15:53:15:891 NetpJoinDomainOnDs: Setting netlogon cache.
    07/15/2021 15:53:15:920 NetpJoinDomainOnDs: status of setting netlogon cache: 0x0
    07/15/2021 15:53:15:920 NetpJoinDomainOnDs: Function exits with status of: 0x0
    07/15/2021 15:53:15:932 NetpJoinDomainOnDs: status of disconnecting from '\\Dc-AD01.test.com': 0x0
    07/15/2021 15:53:15:933 NetpJoinDomain: DsrIsDeviceJoined returned false
    07/15/2021 15:53:16:178 NetpJoinDomain: NetpCompleteOfflineDomainJoin SUCCESS: Requested a reboot :0x0
    07/15/2021 15:53:16:178 NetpDoDomainJoin: status: 0x0
    : Setting backup/restore privileges.
    07/15/2021 15:53:15:869 NetpProvGetWindowsImageState: IMAGE_STATE_COMPLETE.
    07/15/2021 15:53:15:869 NetpAddPartCollectionToRegistry.
    07/15/2021 15:53:15:870 NetpProvGetTargetProductVersion: Target product version: 10.0.18362.1
    07/15/2021 15:53:15:876 NetpAddPartCollectionToRegistry: delete OP state key status: 0x2.
    07/15/2021 15:53:15:877 NetpConvertBlobToJoinState: Translating provisioning data to internal format
    07/15/2021 15:53:15:877 NetpConvertBlobToJoinState: Selecting version 1
    07/15/2021 15:53:15:877 NetpConvertBlobToJoinState: exiting: 0x0
    07/15/2021 15:53:15:886 NetpJoin2RequestPackagePartInstall: Successfully persisted all fields
    07/15/2021 15:53:15:887 NetpAddPartCollectionToRegistry: Successfully initiated provisioning package installation: 2/2 part(s) installed.
    07/15/2021 15:53:15:887 NetpAddPartCollectionToRegistry: status: 0x0.
    07/15/2021 15:53:15:887 NetpOpenRegistry: status: 0x0.
    07/15/2021 15:53:15:887 NetpSetPrivileges: status: 0x0.
    07/15/2021 15:53:15:887 NetpRequestProvisioningPackageInstall: status: 0x0.
    07/15/2021 15:53:15:938 -----------------------------------------------------------------
    07/15/2021 15:53:15:938 NetpProvContinueProvisioningPackageInstall:
    07/15/2021 15:53:15:938 Context: 0
    07/15/2021 15:53:15:938 NetpProvGetWindowsImageState: IMAGE_STATE_COMPLETE.
    07/15/2021 15:53:15:942 NetpCreatePartListFromRegistry: status: 0x0.
    07/15/2021 15:53:15:943 NetpCompleteOfflineDomainJoin
    07/15/2021 15:53:15:943 fBootTimeCaller: FALSE
    07/15/2021 15:53:15:943 fSetLocalGroups: TRUE
    07/15/2021 15:53:15:943 NetpJoinDomainLocal: NetpHandleJoinedStateInfo returned: 0x0
    07/15/2021 15:53:16:100 NetpJoinDomainLocal: NetpManageMachineSecret returned: 0x0.
    07/15/2021 15:53:16:100 Calling NetpQueryService to get Netlogon service state.
    07/15/2021 15:53:16:101 NetpJoinDomainLocal: NetpQueryService returned: 0x0.
    07/15/2021 15:53:16:108 NetpJoinDomainLocal: status of setting LSA pri. domain: 0x0
    07/15/2021 15:53:16:108 NetpManageLocalGroupsForJoin: Adding groups for new domain, removing groups from old domain, if any.
    07/15/2021 15:53:16:132 NetpManageLocalGroupsForJoin: status of modifying groups related to domain 'TEST' to local groups: 0x0
    07/15/2021 15:53:16:133 NetpManageLocalGroupsForJoin: INFO: No old domain groups to process.
    07/15/2021 15:53:16:133 NetpJoinDomainLocal: Status of managing local groups: 0x0
    07/15/2021 15:53:16:146 NetpJoinDomainLocal: status of setting ComputerNamePhysicalDnsDomain to 'test.com': 0x0
    07/15/2021 15:53:16:147 NetpJoinDomainLocal: Controlling services and setting service start type.
    07/15/2021 15:53:16:148 NetpJoinDomainLocal: Updating W32TimeConfig
    07/15/2021 15:53:16:165 NetpCompleteOfflineDomainJoin: status: 0x0
    07/15/2021 15:53:16:165 NetpJoinProvider2OLContinuePackagePartInstall: ignoring Context=0 (work finished already).
    07/15/2021 15:53:16:166 NetpProvContinueProvisioningPackageInstall: Provisioning package installation completed successfully.
    07/15/2021 15:53:16:172 NetpProvContinueProvisioningPackageInstall: delete OP state key status: 0x0.
    07/15/2021 15:53:16:172 NetpProvContinueProvisioningPackageInstall: status: 0xa99.
    07/15/2021 15:53:17:937 -----------------------------------------------------------------
    07/15/2021 15:53:17:937 NetpChangeMachineName: from 'DJEX-TRAINING' to 'DJEX-training' using 'test.com\root' [0x1000]
    07/15/2021 15:53:17:937 NetpChangeMachineName: using DnsHostnameToComputerNameEx
    07/15/2021 15:53:17:937 NetpChangeMachineName: generated netbios name: 'DJEX-TRAINING'
    07/15/2021 15:53:17:937 NetpDsGetDcName: trying to find DC in domain 'test.com', flags: 0x1010
    07/15/2021 15:53:18:563 NetpDsGetDcName: found DC '\\Dc-AD01.test.com' in the specified domain
    07/15/2021 15:53:18:564 NetpGetDnsHostName: Read NV Domain: test.com
    07/15/2021 15:53:18:674 NetpGetComputerObjectDn: Unable to bind to DS on '\\Dc-AD01.test.com': 0x6bf
    07/15/2021 15:53:18:674 NetpSetDnsHostNameAndSpn: NetpGetComputerObjectDn failed: 0x6bf
    07/15/2021 15:53:18:674 ldap_unbind status: 0x0
    07/15/2021 15:53:18:674 NetpChangeMachineName: status of setting DnsHostName and SPN: 0x6bf

    Friday, July 16, 2021 2:41 AM
  • Hi,

    非常感谢您的回复。

    根据提供的netsetup日志,加域并没有成功。

    1727报错是远程过程调用失败且未执行。

    但是我们的情况有点特殊,因为在加域的过程中,按照我们说的,提示加域成功了,并且在DC上也有这个计算机账号了。接下来我们可以尝试以下方法:

    1. 选定一台有报错的客户端,如果之前尝试过加域,请删除在DC上的A记录和计算机对象。

    2. 使用本地管理员账号登录这台客户端。

    3. 以管理员身份打开CMD.

    4. 输入Netdom resetpwd /s:target_server /ud:mydomain\domain_admin /pd:*并按回车键。

    /s:后面跟一台域控制器的名字 
    /ud:后面跟域管理员的账号 
    /pd:* 后面跟域管理员账号对应的密码

    5. 此命令用于重置计算机的密码。如果命令运行成功了的话, 我们再次尝试加域,看看这次是否可以成功。

    如有问题,请随时联系我们。

    Best regards,
    Hannah Xiong


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Friday, July 16, 2021 8:24 AM
  • 感谢你的回复,我尝试了netdom命令,提示'netdom' 不是内部或外部命令,也不是可运行的程序或批处理文件。

    目前来看不是这一台客户端机器存在这个问题,最近加域的两三台均有上面的情况,所以我的疑问在于是否是DC域控上出现了上面问题,今天再次dcdiag了两台DC,均可以通过测试。

    我检查了计算机对象,发现有如下问题,

    这是正常的客户端情况:DNS名称注册正常

    这是出现问题的客户端,DNS名称为空

    但是在DNS中可以找到异常客户端的A记录,

    还望再次帮忙确认故障原因

    Monday, July 19, 2021 2:30 AM
  • 您好,

    非常感谢您的回复。

    目前我们有2台域控,并且域控均运行正常,测试都可以通过,而且之前的复制命令运行结果显示,复制正常。

    正常加域成功的话,会显示DNS名称。很奇怪的是,在这种情况下,DNS中还会有异常的客户端的A记录。

    我们尝试了netdom命令,但是有报错,是因为普通的桌面系统默认不带这个命令,我们需要自己安装。我们可以在客户端上下载Remote Server Administration Tools,然后再尝试使用此命令。
    更多信息,可以参考:Remote Server Administration Tools - Windows Server | Microsoft Docs

    另外,如果上面的尝试无法解决问题的话,可能需要收集更多的日志,比如说抓取网络包进一步分析。这样的话,建议我们联系Microsoft开case解决此问题。

    Best regards,
    Hannah Xiong

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Monday, July 19, 2021 6:44 AM
  • 您好,

    我们正在跟踪您所遇到问题的进展,请问,目前有进展吗?

    如果您有任何的问题,请随时联系我们。

    Best regards,
    Hannah Xiong

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Wednesday, July 21, 2021 2:54 AM
  • 我的问题我已经解决了,但是这是一次遗憾、失望、糟糕的客户支持体验经历。

    1:我提供了加域的客户端日志,根据上面的报错并没有给到有效的回复。

    2:netdom命令未测试直接给到我,我在实际环境中出现错误后,才在你的环境中测试该命令,在你给到我netdom命令之前难道不应该先测试下?

    3:我进一步提供报错的截图,你建议我收集更多的日志,没有明确日志来源?是客户端or域控端,日志类型

    4:没有任何实际性帮助情况下,建议我联系Microsoft开case解决此问题,也没有告知我开case的途径。

    总体来说,是一次特别遗憾、失望、糟糕的客户支持体验,我也不清楚这个论坛是否还是Microsoft的官方支持途径,也不再清楚这个论坛的支持范围和支持程度,总之非常失望、糟糕。

    Wednesday, July 21, 2021 7:01 AM
  • 您好,

    很高兴听到我们的问题已经解决了,可以知道我们是怎么解决问题的吗?

    很抱歉这次给您带来不满意的客户支持体验。根据您提供的netsetup日志,我们分析了报错以及提供了重置计算机密码的方案。这个方案也是我这边跟同事讨论后,提供给您这边的。希望我们可以尝试下这个方法。这个命令我们之前都是在环境中测试过的。可能表达有点问题,我之前说的是您这边尝试了这个命令,但是有报错。可能用了“我们”,让您误解了。

    我们在提供任何信息之前,或者是提供任何操作的话,都提前会测试的。但是因为局限性,我们也不能完全了解客户的环境,可能会有一些出入。但是有问题的话,我们都会尽力再去解决问题。

    很抱歉我这边未能跟您这边解释清楚,涉及到收集日志的话,因为安全问题,论坛这边就不支持了。所以建议您这边开case。链接如下:
    Support for business (microsoft.com)

    关于日志这边,根据我的经验,可以在客户端收集网络包(network trace)并结合Netlsetup日志一起分享。可能需要根据分享的结果,还抓取其他的日志。

    不管怎样,我们很抱歉给您带来不好的体验。很感谢您的反馈,让我深刻认识到自己在这次支持中的不足和欠缺。这将对我有很大的帮助,能让我在今后的支持中提供更好的用户体验。

    感谢您的理解和支持。

    Best regards,
    Hannah Xiong

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Thursday, July 22, 2021 8:54 AM