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 trust DNS, so worth verifying those things.
Otherwise I'd maybe try the following: Use the event viewer on the destination windows machine to see if there is anything there which might explain the 'Connection refused' message Ensure you are using ansible 2.0 or later, and pywinrm 0.11 (or later) - its much faster when targetting windows hosts than 1.9.x was so less likely to hit timeouts. Ensure your ansible controller and windows machine are 'near' to each other in terms of networking. Its best to avoid lots of network hops between the ansible controller and the machines you are controlling (general advice for Ansible, not specific to windows). Look for a firewall that could be chopping your connection. I hope something from the above might help Jon On Wednesday, April 27, 2016 at 6:06:28 AM UTC+1, Deepa Yr wrote: > > 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 [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/46e86e6b-9d82-4314-9809-a5dbb4bf9ee7%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
