I am about to raise the DFL and FFL of a single Domain (no forest/trusts).
It is currently at 2003, we need to go to 2008 minimum for CRM 2015/16.
Our setup is fairly simple.
5x DC's, all Server 2008R2
NATTHN39 :
Schema Master & Domain Naming Master
NATRHN08 :
PDC / RID Pool Manager / Infrastructure Master
Remaining Servers hold no special roles.
All 5 are DNS/WINS
I have been planning this change for a week or so, all of this was working fin on the 27th.
Yesterday I was running a bunch of checks prior to making the change to the DFL when I noticed replication errors. Specifically replication from NATRHN08 (PDC) to NATTHN39 (Operations Master).
The same error is apparent in any attempt to connect DS functions from NATRHN08 to NATTHN39. Here is the output of NTDSUTIL run on NATRHN08 :
ntdsutil: local roles
local roles: connections
server connections: connect to server NATTHN39
Binding to NATTHN39 ...
DsBindWithSpnExW error 0x80090322(The target principal name is incorrect.)
server connections: connect to server NATTHN80
Binding to NATTHN80 ...
Connected to NATTHN80 using credentials of locally logged on user.
server connections: connect to server NATRHN01
Disconnecting from NATTHN80...
Binding to NATRHN01 ...
Connected to NATRHN01 using credentials of locally logged on user.
It is just the connection NATRHN08 -> NATTHN39 that is problematic. All other scenarios work OK, including NATTHN39 -> NATRHN08.
To fix I have attempted to use NETDOM to rest the password as follows
NET STOP KDC on NATTHN39
Reboot NATTHN39
klist purge
NETDOM /RESETPWD /S:NATRHN08 /UD:domain\user /PD:*
Reboot NATTHN39
NET START KDC
repadmin /syncall
This has not resolved the issue. The "The target principal name is incorrect" issue still exists.
Whilst looking into this I've also discovered a bunch of other issues I'm not sure about.
If i run DCDIAG all tests other than replication pass. If I run dcdiag /v I get a load failures on CrossRefValidation
If I use ADSI edit to check the schema version I get <not set>, running dsquery for the same returns objectversion 47.
I feel that the issue is to do with the execution of the netdom password reset but I can't see how I'm doing it wrong.