# Ansible 2.0.2 and Windows Server 2012 **URL:** \ **Category:** Ansible Project\ **Tags:** windows\ **Created:** [May 23, 2016, 4:17pm UTC](https://forum.ansible.com/t/ansible-2-0-2-and-windows-server-2012/21523 "2016-05-23T16:17:51Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![dyioulos](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/dyioulos/32/8363_2.png) [@dyioulos](https://forum.ansible.com/u/dyioulos)\ **Post date:** [May 23, 2016, 4:17pm UTC](https://forum.ansible.com/t/ansible-2-0-2-and-windows-server-2012/21523/1 "2016-05-23T16:17:51Z")
Hello, all. Until today, I’d hadn’t used our recently updated Ansible (19.4. → 2.0.2) against our few Windows Server 2012R2 servers but, when I did, I had failures, even when running the simplest modules (e.g. win\_ping). Here’s what I get: Loaded callback minimal of type stdout, v2.0 ESTABLISH WINRM CONNECTION FOR USER: winuser on PORT 5986 TO veeambackup11 veeambackup11 | FAILED! =\> { “failed”: true, “msg”: “ssl: 500 WinRMTransport. [Errno 110] Connection timed out” } I see the “Connection timed out” message, but am puzzled as to why I’m getting it with Ansible version 2.0.2 (the Ansible upgrade is the only thing that’s changed in the environment). Everything worked on both Win2K8 and Win2k12 boxes in version 1.9.4. In version 2.0.2, everything works on the Win2k8 boxes but, as I said, not on Win2k12. Has anyone experienced, and solved, this problem, or can otherwise shed some light? Many thanks. ---
**Author:** ![j.r.hawkesworth](https://avatars.discourse-cdn.com/v4/letter/j/a3d4f5/32.png) [@j.r.hawkesworth](https://forum.ansible.com/u/j.r.hawkesworth)\ **Post date:** [May 23, 2016, 5:24pm UTC](https://forum.ansible.com/t/ansible-2-0-2-and-windows-server-2012/21523/2 "2016-05-23T17:24:49Z")
I have hit a lot of s2012R2 machines today using ansible 2.0.0.2 and 2.0.2.0 so I don’t think it is something inherent in ansible. Connection timed out implies it isn’t able to connect to winrm on the machine. I suggest you try the pywinrm examples directly [https://github.com/diyan/pywinrm#run-process-with-low-level-api-with-domain-user-disabling-https-cert-validation](https://github.com/diyan/pywinrm#run-process-with-low-level-api-with-domain-user-disabling-https-cert-validation) Also I’d go looking for firewall changes to make sure the winrm port is still open. Hope this helps, Jon ---
**Author:** ![dyioulos](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/dyioulos/32/8363_2.png) [@dyioulos](https://forum.ansible.com/u/dyioulos)\ **Post date:** [May 23, 2016, 6:22pm UTC](https://forum.ansible.com/t/ansible-2-0-2-and-windows-server-2012/21523/3 "2016-05-23T18:22:55Z")
Thanks for the response, Jon. As mentioned in my original post, version 1.9.4 worked with Win2k12 hosts just fine. It’s only after I upgraded to version 2.0.2 that things went bad. So, that had me looking at Ansible first. Regarding pywinrm, I have version 0.1.1 installed and working. I believe that’s the correct version. There have been no firewall changes. Even when I turn the firewall off, I get the same error. ---
**Author:** ![Mike\_Fennemore](https://avatars.discourse-cdn.com/v4/letter/m/45deac/32.png) [@Mike\_Fennemore](https://forum.ansible.com/u/Mike_Fennemore)\ **Post date:** [May 23, 2016, 6:41pm UTC](https://forum.ansible.com/t/ansible-2-0-2-and-windows-server-2012/21523/4 "2016-05-23T18:41:40Z")
Hi there, 2 things you can try. Add a group or host var ansible\_winrm\_server\_cert\_validation: ignore. Alternatively try out newer pywinrm: [http://groups.google.com/group/ansible-project/t/bc497e9abbc592b6?utm\_source=digest&utm\_medium=email](http://groups.google.com/group/ansible-project/t/bc497e9abbc592b6?utm_source=digest&utm_medium=email) With that you can use ansible\_winrm\_transport:ntlm or kerberos