You can also try to run the below PS script on the hosts to ensure all the WinRm options have been taken care of to allow Ansible to connect to it.
https://github.com/ansible/ansible/blob/devel/examples/scripts/ConfigureRemotingForAnsible.ps1 On Wednesday, June 1, 2016 at 6:43:50 PM UTC-4, skinnedknuckles wrote: > > Actually I had to type > > winrm set winrm/config/service '@{AllowUnencrypted="true"}' > > before it would work for me. > > > On Friday, May 27, 2016 at 9:26:32 AM UTC-5, Mike Fennemore wrote: >> >> I have a selected few workgroup Windows server 2012 R2 servers that give >> the following error: >> >> <10.128.44.37> ESTABLISH WINRM CONNECTION FOR USER: ansible_user on PORT >> 5986 TO 10.128.44.37 >> server_101 | UNREACHABLE! => { >> "changed": false, >> "msg": "ntlm: ('Connection aborted.', error(104, 'Connection reset by >> peer'))", >> "unreachable": true >> } >> >> I am using ntlm with Ansible 2.1.0.0 and pywinrm [kerberos] 2RC4. I have >> tested the port is open, recreated the listeners, run a curl to the server >> which delivers a successful 411 response. >> Any ideas on further troubleshooting? >> >> >> -- 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/2993fa75-3d0e-4d51-bffe-575c0f06d203%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
