I never got Kerberos to work. I ended up using SSL instead.
On Wednesday, June 1, 2016 at 5:40:48 PM UTC-5, skinnedknuckles wrote:
>
> Control Node:
>
>- CentOS 7
>- Ansible 2.1
>- pywinrm version from May 19th, 2016
>
> Remote Node:
>
>- Windows 7
>- Powershell 3
>
>
> I'm ha
Hi skinnedknuckles,
Does it work for you now? I am getting the same error message.
Server_Name | UNREACHABLE! => {
"changed": false,
"msg": "kerberos: (('Unspecified GSS failure. Minor code may provide
more information', 851968), ('Server not found in Kerberos database',
-1765328377)
>> *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:
[alf...@webdmz.no@tvm-alfkla
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.
On Thursday, October 20, 2016 at 10:00:45 AM UTC-7, Alf Normann Klausen
wrote:
>
> Hi,
>
> I think I have
Hi,
I think I have the exact same problem.
Running ansible 2.1.1.0-1.el7 on CentOS 7.2.1511
Here is an example of ansible command output:
[alf...@webdmz.no@tvm-alfkla ~]$ ansible -i hosts TVM-ALF2012R2 -m win_ping
-v
Using /etc/ansible/ansible.cfg as config file
Loaded callback minimal of
Probably not. First, make sure you specify ansible_user: ads-6999 including
the realm, so ansible_user: ads-6...@acme.com. Not sure if that has any
effect, but still. If that fails, I'd create a new user with a different
name from the node to see if that helps.
On Thursday, June 2, 2016 at 8:56
Yes, they are the same. Is that a problem? I could make a new account
local or domain.
On Wednesday, June 1, 2016 at 5:40:48 PM UTC-5, skinnedknuckles wrote:
>
> Control Node:
>
>- CentOS 7
>- Ansible 2.1
>- pywinrm version from May 19th, 2016
>
> Remote Node:
>
>- Windows 7
>
Is both your user and your computer named "ADS-6999"?
On Thursday, June 2, 2016 at 12:40:48 AM UTC+2, skinnedknuckles wrote:
>
> Control Node:
>
>- CentOS 7
>- Ansible 2.1
>- pywinrm version from May 19th, 2016
>
> Remote Node:
>
>- Windows 7
>- Powershell 3
>
>
> I'm having tr
