I found a security policy that had been set to "Deny all", the policy was "Network security: Restrict NTLM: Outgoing NTLM traffic to remote servers", by setting it to "Audit all" seemed to fix the issue and the systems can now connect to the domain.
Getting 'The request is not supported' when Joining Domain
I've tried connecting on multiple machines in an attempt to fix this but nothing seems to be working, if anyone can assist, here are the logs.
NetpDoDomainJoin
NetpDoDomainJoin: using current computer names
NetpDoDomainJoin: NetpGetComputerNameEx(NetBios) returned 0x0
NetpDoDomainJoin: NetpGetComputerNameEx(DnsHostName) returned 0x0
NetpMachineValidToJoin: 'KODA'
NetpMachineValidToJoin: status: 0x0
NetpJoinDomain
HostName: KODA
NetbiosName: KODA
Domain: horizons.local
MachineAccountOU: (NULL)
Account: HORIZONS\Administrator
Options: 0x27
NetpValidateName: checking to see if 'horizons.local' is valid as type 3 name
NetpCheckDomainNameIsValid [ Exists ] for 'horizons.local' returned 0x0
NetpValidateName: name 'horizons.local' is valid for type 3
NetpDsGetDcName: trying to find DC in domain 'horizons.local', flags: 0x40001010
NetpDsGetDcName: failed to find a DC having account 'KODA$': 0x525, last error is 0x0
NetpDsGetDcName: status of verifying DNS A record name resolution for 'artemis.horizons.local': 0x0
NetpDsGetDcName: found DC '\\artemis.horizons.local' in the specified domain
NetpJoinDomainOnDs: NetpDsGetDcName returned: 0x0
NetpDisableIDNEncoding: using FQDN horizons.local from dcinfo
NetpDisableIDNEncoding: DnsDisableIdnEncoding(UNTILREBOOT) on 'horizons.local' succeeded
NetpJoinDomainOnDs: NetpDisableIDNEncoding returned: 0x0
NetUseAdd to \\artemis.horizons.local\IPC$ returned 50
NetpJoinDomainOnDs: status of connecting to dc '\\artemis.horizons.local': 0x32
NetpJoinDomainOnDs: Function exits with status of: 0x32
NetpResetIDNEncoding: DnsDisableIdnEncoding(RESETALL) on 'horizons.local' returned 0x0
NetpJoinDomainOnDs: NetpResetIDNEncoding on 'horizons.local': 0x0
NetpDoDomainJoin: status: 0x32
3 additional answers
Sort by: Most helpful
-
Dave Patrick 426K Reputation points MVP
2021-04-03T03:09:55.637+00:00 I'd check the domain controller and problem member both have the static ip address of DC listed for DNS and no others such as router or public DNS.
--please don't forget to Accept as answer if the reply is helpful--
-
Fan Fan 15,291 Reputation points Microsoft Vendor
2021-04-05T02:35:07.38+00:00 Hi,
If the issue happens for multiple PCs when joining the domain , it is suggested to check the status of the DCs and the replication among DCs, DNS configuration.
Run command the DCs and confirm if there are any errors:
Dcdiag /v >c:\dcdiag1.log
Repadmin /syncall /APeD
Repadmin /showrepl >C:\repl.txt
Repadmin /showreps *
Ipconfig /all > C:\dc.txtBest Regards,
-
Dave Patrick 426K Reputation points MVP
2021-04-05T02:36:47.077+00:00 Any progress or updates?
--please don't forget to
Accept as answer
if the reply is helpful--