Thanks for the inputs. With new script, I see connection failure reduced
significantly
--
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+unsu
It could be- I've heard reports that cloning the box *after* enabling wsman
can cause issues if you don't reconfigure stuff (see
https://github.com/ansible/ansible/pull/15275), though I've not experienced
this issue myself.
Regardless, it appears that the issue lies somewhere with the machine's
Thanks for the inputs.
I noticed Event viewer.The WinRM service is not listening for WS-Management
requests.
User Action
If you did not intentionally stop the service, use the following command
to see the WinRM configuration:
winrm enumerate winrm/config/listener
Let me explain the thin
I have a couple of suggestions...
If you are using kerberos, make sure your ansible controller's time is
synchronized with your domain controllers and also check that nslookup and
ping return the correct hostname and ip address - kerberos depends on both
the clock being right and being able to
Any help on this ?
Thanks
>
Deepa
--
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
