I have a Zentyal 4.1 Dev edition server on my LAN acting as an AD DC. I know it works because my Windows 8.1 machine joined the domain without issue and domain admins have admin access on it.
I also have a Windows 10 N Pro running on a Hyper-V VM on the same LAN. Its network shows Private Network, the DNS is set as the DC, so is the "Internet Time" NTP sync. Its fully updated.
However, when I try to join the domain using a domain admin account, it tells me that the username or password is incorrect. This is true for using both the username and domain_name\username formats. Here is the relevant NetSetup log:
08/30/2015 09:08:56:372 ----------------------------------------------------------------- 08/30/2015 09:08:56:372 NetpDoDomainJoin 08/30/2015 09:08:56:372 NetpDoDomainJoin: using current computer names 08/30/2015 09:08:56:388 NetpDoDomainJoin: NetpGetComputerNameEx(NetBios) returned 0x0 08/30/2015 09:08:56:388 NetpDoDomainJoin: NetpGetComputerNameEx(DnsHostName) returned 0x0 08/30/2015 09:08:56:388 NetpMachineValidToJoin: 'WIN10TEST' 08/30/2015 09:08:56:388 NetpMachineValidToJoin: status: 0x0 08/30/2015 09:08:56:388 NetpJoinDomain 08/30/2015 09:08:56:388 HostName: win10test 08/30/2015 09:08:56:388 NetbiosName: WIN10TEST 08/30/2015 09:08:56:388 Domain: hq.vladnet.ca 08/30/2015 09:08:56:388 MachineAccountOU: (NULL) 08/30/2015 09:08:56:388 Account: hq.vladnet.ca\zenadmin 08/30/2015 09:08:56:388 Options: 0x27 08/30/2015 09:08:56:466 NetpValidateName: checking to see if 'hq.vladnet.ca' is valid as type 3 name 08/30/2015 09:08:56:607 NetpCheckDomainNameIsValid [ Exists ] for 'hq.vladnet.ca' returned 0x0 08/30/2015 09:08:56:607 NetpValidateName: name 'hq.vladnet.ca' is valid for type 3 08/30/2015 09:08:56:607 NetpDsGetDcName: trying to find DC in domain 'hq.vladnet.ca', flags: 0x40001010 08/30/2015 09:08:57:075 NetpDsGetDcName: failed to find a DC having account 'WIN10TEST$': 0x525, last error is 0x0 08/30/2015 09:08:57:138 NetpDsGetDcName: status of verifying DNS A record name resolution for 'zentyallatest.hq.vladnet.ca': 0x0 08/30/2015 09:08:57:138 NetpDsGetDcName: found DC '\\zentyallatest.hq.vladnet.ca' in the specified domain 08/30/2015 09:08:57:138 NetpJoinDomainOnDs: NetpDsGetDcName returned: 0x0 08/30/2015 09:08:57:138 NetpDisableIDNEncoding: using FQDN hq.vladnet.ca from dcinfo 08/30/2015 09:08:57:138 NetpDisableIDNEncoding: DnsDisableIdnEncoding(UNTILREBOOT) on 'hq.vladnet.ca' succeeded 08/30/2015 09:08:57:138 NetpJoinDomainOnDs: NetpDisableIDNEncoding returned: 0x0 08/30/2015 09:08:57:200 NetUseAdd to \\zentyallatest.hq.vladnet.ca\IPC$ returned 1326 08/30/2015 09:08:57:200 NetpJoinDomainOnDs: status of connecting to dc '\\zentyallatest.hq.vladnet.ca': 0x52e 08/30/2015 09:08:57:200 NetpJoinDomainOnDs: Function exits with status of: 0x52e 08/30/2015 09:08:57:216 NetpResetIDNEncoding: DnsDisableIdnEncoding(RESETALL) on 'hq.vladnet.ca' returned 0x0 08/30/2015 09:08:57:216 NetpJoinDomainOnDs: NetpResetIDNEncoding on 'hq.vladnet.ca': 0x0 08/30/2015 09:08:57:216 NetpDoDomainJoin: status: 0x52e
Here is the funny part though. If I run the admin Powershell command:
Add-Computer -DomainName hq.vladnet.ca -Credential Get-Credential
Using the normal DC domain admin username and pass, it works.
Sadly, once I restart the PC to start using it, any attempt to use Domain users also produces incorrect name or password error.
Here is the NetSetup log for when the powershell cmd succeeds.
08/30/2015 09:29:53:964 NetpDoDomainJoin 08/30/2015 09:29:53:964 NetpDoDomainJoin: using current computer names 08/30/2015 09:29:53:964 NetpDoDomainJoin: NetpGetComputerNameEx(NetBios) returned 0x0 08/30/2015 09:29:53:964 NetpDoDomainJoin: NetpGetComputerNameEx(DnsHostName) returned 0x0 08/30/2015 09:29:53:995 NetpMachineValidToJoin: 'WIN10TEST' 08/30/2015 09:29:54:027 NetpMachineValidToJoin: status: 0x0 08/30/2015 09:29:54:027 NetpJoinDomain 08/30/2015 09:29:54:027 HostName: win10test 08/30/2015 09:29:54:027 NetbiosName: WIN10TEST 08/30/2015 09:29:54:027 Domain: hq.vladnet.ca 08/30/2015 09:29:54:027 MachineAccountOU: (NULL) 08/30/2015 09:29:54:027 Account: zenadmin 08/30/2015 09:29:54:027 Options: 0x3 08/30/2015 09:29:54:089 NetpValidateName: checking to see if 'hq.vladnet.ca' is valid as type 3 name 08/30/2015 09:29:54:261 NetpCheckDomainNameIsValid [ Exists ] for 'hq.vladnet.ca' returned 0x0 08/30/2015 09:29:54:261 NetpValidateName: name 'hq.vladnet.ca' is valid for type 3 08/30/2015 09:29:54:261 NetpDsGetDcName: trying to find DC in domain 'hq.vladnet.ca', flags: 0x40001010 08/30/2015 09:29:54:745 NetpDsGetDcName: failed to find a DC having account 'WIN10TEST$': 0x525, last error is 0x0 08/30/2015 09:29:54:824 NetpDsGetDcName: status of verifying DNS A record name resolution for 'zentyallatest.hq.vladnet.ca': 0x0 08/30/2015 09:29:54:824 NetpDsGetDcName: found DC '\\zentyallatest.hq.vladnet.ca' in the specified domain 08/30/2015 09:29:54:824 NetpJoinDomainOnDs: NetpDsGetDcName returned: 0x0 08/30/2015 09:29:54:824 NetpDisableIDNEncoding: using FQDN hq.vladnet.ca from dcinfo 08/30/2015 09:29:54:855 NetpDisableIDNEncoding: DnsDisableIdnEncoding(UNTILREBOOT) on 'hq.vladnet.ca' succeeded 08/30/2015 09:29:54:855 NetpJoinDomainOnDs: NetpDisableIDNEncoding returned: 0x0 08/30/2015 09:29:55:636 NetpJoinDomainOnDs: status of connecting to dc '\\zentyallatest.hq.vladnet.ca': 0x0
Help?
- Moved by Carey FrischMVP, Moderator 1 hour 50 minutes ago Relocated