win_ping Name or service not known

719 views
Skip to first unread message

skinnedknuckles

unread,
Apr 25, 2016, 2:06:21 PM4/25/16
to Ansible Project
Centos 7
Ansible 2.1
Windows 7 on remote node

My inventory file (/etc/ansible/hosts) contains...
[windows]
123.123.123.123.mycompany.com

My /etc/ansible/group_vars/windows.yml file contains...

ansible_user: username
ansible_password: password
ansible_port: 5985
ansible_connection: winrm
ansible_winrm_server_cert_validation: ignore

 But when I try to run win_ping I get this:

$ansible windows -m win_ping -c winrm --vvv
No config file found; using defaults
<123.123.123.123.mycompany.com> ESTABLISH WINRM CONNECTION FOR USER: username on port 5985 TO 123.123.123.123.mycompany.com
123.123.123.123.mycompany.com | FAILED! => {
    "failed": true.
    "msg": "plaintext: 500 WinRMTransport. [Errno -2] Name or service not known"
}

What config file am I missing?
Where should it be located?
What should it contain?

Any suggestions are appreciated.

Jonathan

J Hawkesworth

unread,
Apr 26, 2016, 5:49:48 AM4/26/16
to Ansible Project
Hi,

Could be a few things going on here but 'Name or service not known' can mean that it can't find the host.

Can you ping 123.123.123.123.mycompany.com from your ansible controller? Also if you do an nslookup on its ip address, do you get the correct hostname back?


Also, if I recall, Windows 7 came with Powershell 2.0.  You'll need to upgrade it to at least Powershell / Windows Management Framework 3.0 (although I would go straight to 4.0 if possible).

Hope this helps,

Jon

Reply all
Reply to author
Forward
0 new messages