I used a fresh box & finally did below & wored
yum install -y python3-devel
pip install pykerberos
Thanks @Jordan
On Thursday, May 21, 2020 at 5:37:40 PM UTC-7, Jordan Borean wrote:
>
> The issue here is the kerberos library you have installed is either too
> old or incompatible with what
Anyways i did below
1017 21/05/20 17:47:19 yum remove python-kerberos-1.1-15.el7.x86_64
1018 21/05/20 17:49:29 rpm -qa|grep -i kerb
1019 21/05/20 17:49:43 pip install pykerberos
1020 21/05/20 17:49:55 pip install requests-kerberos
1021 21/05/20 17:50:05 ansible windows -m win_ping
Shall i do below
yum remove python-kerberos-1.1-15.el7.x86_64
=
Package
Thanks for the reply
You mean :
yum remove -y krb5-devel krb5-libs krb5-workstation
And
re-run
*pip install pykerberos*
On Thursday, May 21, 2020 at 5:37:40 PM UTC-7, Jordan Borean wrote:
>
> The issue here is the kerberos library you have installed is either too
> old or
The issue here is the kerberos library you have installed is either too old
or incompatible with what requests-kerberos requires. Uninstall both
kerberos and pykerberos and install just pykerberos. You may want to update
requests-kerberos as well as 0.7.0 is quite old.
--
You received this
Thank you Jordan!
I managed connect using Kerberos instead of using ssl. For ssl connection I
think i need to create self signed cert as mention here
http://www.hurryupandwait.io/blog/understanding-and-troubleshooting-winrm-connection-and-authentication-a-thrill-seekers-guide-to-adventure.
There are numerous scenarios that can cause an authentication problem, such
as;
- The credentials you are using are actually incorrect, or you haven't
specified the password in Ansible correctly
- The account is disabled or locked on the Windows host
- If using Basic auth (you are),
I will try this Ankit.
Thank you.
On Thursday, 20 September 2018 09:45:01 UTC-4, Ankit Vashistha wrote:
>
> Try adding the following and recheck with ntlm
> ansible_winrm_message_encryption: auto
>
> On Thu, Sep 20, 2018, 7:09 PM 'J Hawkesworth' via Ansible Project <
> ansible...@googlegroups.com
Thank you @Hawkesworth.
Yeah this might be the dependensy issue with winrm on latest ansible
version.
i worked absolutely fine when i used ansible 2.4.2.1 version with
pywinrm[0.2.0] with basic authentication.
But kerberos authentication is not supported in that version.
On Thursday, 20
Try adding the following and recheck with ntlm
ansible_winrm_message_encryption: auto
On Thu, Sep 20, 2018, 7:09 PM 'J Hawkesworth' via Ansible Project <
ansible-project@googlegroups.com> wrote:
> Can you run
>
> ansible windows -m win_ping -v
>
> This should return the stack trace.
>
> My
Can you run
ansible windows -m win_ping -v
This should return the stack trace.
My guess is one of your keberos-related dependencies is out of date.
Sometimes the kerberous libraries are installed with the operating system,
so you may need to double check the dependencies you have
+1
getting the same error, didn't get the solution yet.
please post here if anyone resolved the following error.
pip list :
Package Version
-
ansible 2.6.4
asn1crypto 0.24.0
Babel
Ok a couple of other ideas...
See if the s2012r2 target firewall is blocking traffic to/from port 5985
If I recall the configure for remoting script adds a rule for this but
worth checking all the profiles.
Also worth checking for any firewalling on your ansible host as well while
you are at
Same error is raised regardless of hostname, even if I put an erroneous
one. Event log shows an alert to an ntlm authentication but I can't find
anything as far as a successful login I'm targeting Server 2012R2. Ran a
clean install and still run into the issue
On Tuesday, August 7, 2018 at
Can you give us the output of *pip list*, seems like pywinrm is receiving a
None value where it is expecting a string.
Thanks
Jordan
--
You received this message because you are subscribed to the Google Groups
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails
That's a new one on me, but I have a few suggestions of things you can try.
Try using a hostname instead of an ip address.
Try not running ansible from a venv (should be fine, but just peeling back
a layer).
Check the event log on the target windows box (eventvwr.msc) and see if
there is any
16 matches
Mail list logo
