Can your ansible controller machine resolve the name windowsserver.cloudapp.net to an ip address? If so, check that firewalling alllows connections to port 5986.
On Monday, March 2, 2015 at 12:34:17 AM UTC, satheesh kumar wrote: > > I tried to ping windows server from ansible, and getting the below error: > > $ ansible windows -m win_ping -vvvv > <windowsserver.cloudapp.net> ESTABLISH WINRM CONNECTION FOR USER: > windowsuser on PORT 5986 TO windowsserver.cloudapp.net > <windowsserver.cloudapp.net> WINRM CONNECT: transport=plaintext endpoint= > https://windowsserver.cloudapp.net:5986/wsman > <windowsserver.cloudapp.net> WINRM CONNECTION ERROR: 500 WinRMTransport. > [Errno -2] Name or service not known > <windowsserver.cloudapp.net> WINRM CONNECT: transport=plaintext endpoint= > http://windowsserver.cloudapp.net:5986/wsman > <windowsserver.cloudapp.net> WINRM CONNECTION ERROR: 500 WinRMTransport. > [Errno -2] Name or service not known > windowsserver.cloudapp.net | FAILED => 500 WinRMTransport. [Errno -2] > Name or service not known > > > I have correct host under inventories/hosts file, and windows user/pass > under group_vars/windows.yml > > It worked fine earlier some time back, but has name or service not known > error. where might be the issue? > -- 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/60cc9386-80f5-484e-a223-1f95dd3ebd6c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
