question

ItsKoda avatar image
0 Votes"
ItsKoda asked ItsKoda answered

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
windows-serverwindows-active-directorywindows-server-2019
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

ItsKoda avatar image
1 Vote"
ItsKoda answered

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.

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

DSPatrick avatar image
1 Vote"
DSPatrick answered

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--



5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

FanFan-MSFT avatar image
1 Vote"
FanFan-MSFT answered

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.txt

Best Regards,

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

DSPatrick avatar image
0 Votes"
DSPatrick answered

Any progress or updates?

--please don't forget to Accept as answer if the reply is helpful--


5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.