A couple of other suggestions. Is your machine really registered in DNS as 'server.domain.com'? Kerberos really needs DNS lookups to work properly - so if you can ping it and nslookup the host and get back the correct ip address, that's well worth checking as it will not work unless the machine name is properly resolvable.
I suggest working through all the suggestions here: https://docs.ansible.com/ansible/latest/user_guide/windows_winrm.html#troubleshooting-kerberos Also I'm not sure ansible will be able to read your kerberos ticket from the keyring. I have definitely had success with file based credential cache, so worth checking your krb5.conf and environment variables for KRB5CC settings which could be interfering with the kerberos setup that ansible expects. Hope this helps, Jon On Saturday, May 25, 2019 at 5:49:24 PM UTC+1, Oliver wrote: > > Use ansible_port=5985 in the configuration instead of 5986 -- 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 ansible-project+unsubscr...@googlegroups.com. To post to this group, send email to ansible-project@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/a579ab0f-6e49-4120-b6c0-d057fa61d6fc%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
