If you have multiple DCs then potentially it could be replication at fault here but usually if a host is missing from the domain controller it queries then a different error is shown (service not found in the database).
Is the host you are connecting to sharing the same hostname as an older host that it's potentially replacing? If so the SPN could be registered under the newer host on 1 DC but still not been replicated to another DC where it still thinks hostname is another host. Each host would technically have it's own unique key and when the server goes to check the credentials it is unable to decrypt the secret because it's using a different key than the one the DC thought it had (older host) and thus think the credentials were bad. -- You received this message because you are subscribed to the Google Groups "Ansible Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/473b6cc3-5ac7-4c3a-82e0-06e5b15ae750%40googlegroups.com.
