>> *Kerberos is highly dependent on DNS and name->realm mapping; you need 
to use the host's FQDN, not its IP, unless you've hacked up your krb5.conf 
and DNS infra significantly to support that.*

Wow, I replaced the ip address in variable ansible_host= with the FQDN:

[[email protected]@tvm-alfkla ~]$ grep ^TVM-ALF2012R2 hosts 
TVM-ALF2012R2
 ansible_host=TVM-ALF2012R2.WEBDMZ.NO [email protected] 
ansible_password=xXxXxXx ansible_port=5985 ansible_connection=winrm 
ansible_winrm_transport=kerberos ansible_winrm_kerberos_delegation=yes
[[email protected]@tvm-alfkla ~]$



And now it works! 
[[email protected]@tvm-alfkla ~]$ ansible -i hosts TVM-ALF2012R2 -m win_ping 
TVM-ALF2012R2 | SUCCESS => {
    "changed": false, 
    "ping": "pong"
}
[[email protected]@tvm-alfkla ~]$

Thanks a million Matt Davis!!! :o)

Kind regards,
Alf Norman Klausen


-- 
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 post to this group, send email to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/25602ee2-428c-490f-b74e-27bb026fcb3d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to