Hey Mike,
Unfortunately pywinrm currently has *zero* logging/diagnostic capabilities
(something I'd like to correct for troubleshooting stuff like this).
Meantime...
A couple of things to try:
- Does it work with Basic auth and a local user on that same box?
- Any chance you could run with Fiddler in the middle? Just run Fiddler on
some Windows box, configure it to capture/decrypt HTTPS and to allow
external connection, then on your Ansible controller, export
HTTPS_PROXY=http://(ip-of-fiddler-box):8888/ and go watch the fun.
I'm mostly just curious where the connection reset is occurring, as there
are numerous round-trips involved here (eg, is it NTLM auth failure,
resource issue, or something else?).
Thanks,
-Matt
On Friday, May 27, 2016 at 7:26:32 AM UTC-7, 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 [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/e9bf162a-a0bf-44fa-a5f4-50327cfa422b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
