Thanks guys, I changed to fqdn shortly after that original post. Strangely 
enough now only getting access denied with 1 machine even though the winrm 
settings and user accounts on both are exactly the same. they even reside 
in the same subnet. very strange!

Op donderdag 31 augustus 2017 02:54:28 UTC-7 schreef J Hawkesworth:
>
> Well spotted!  Yeah, use hostnames. If you end up switching over to using 
> kerberos hostnames are essential (as is fully functioning DNS lookups (both 
> hostname -> ip and ip -> hostname).
>
> Jon
>
> On Thursday, August 31, 2017 at 10:51:01 AM UTC+1, [email protected] 
> wrote:
>>
>>
>> Use windows fqdn name in place of IPaddress then it will work
>>
>> On Wednesday, August 30, 2017 at 10:21:48 PM UTC+5:30, Thijn Bukkems 
>> wrote:
>>>
>>> Hi all,
>>>
>>> Just getting started with Ansible as proof of concept but already stuck 
>>> and not sure how to make it work. I have a CentOS7 box that is not on the 
>>> domain but on the same network and 2 Windows 2012 R2 servers.
>>>
>>> I ran the ConfigurePowerShellForAnsible.ps1 scripts on both servers as 
>>> admin, as suggested. I set up a local account named 'ansibleadmin' on both 
>>> servers.
>>>
>>> This is the output I get when trying to win_ping the servers:
>>>
>>>> [admin@localhost ansible]$ ansible web -m win_ping
>>>>
>>>>  [WARNING]: ansible_winrm_cert_validation unsupported by pywinrm (is an 
>>>>> up-to-date version of pywinrm installed?)
>>>>
>>>>
>>>>>  [WARNING]: ansible_winrm_cert_validation unsupported by pywinrm (is 
>>>>> an up-to-date version of pywinrm installed?)
>>>>
>>>>
>>>>> 10.128.2.108 | UNREACHABLE! => {
>>>>
>>>>     "changed": false,
>>>>
>>>>     "msg": "plaintext: the specified credentials were rejected by the 
>>>>> server",
>>>>
>>>>     "unreachable": true
>>>>
>>>> }
>>>>
>>>> 10.128.2.215 | UNREACHABLE! => {
>>>>
>>>>     "changed": false,
>>>>
>>>>     "msg": "plaintext: the specified credentials were rejected by the 
>>>>> server",
>>>>
>>>>     "unreachable": true
>>>>
>>>> }
>>>>
>>>>
>>> Some background information regarding my inventory files etc:
>>> inventory.yml:
>>>
>>>>
>>>> ---
>>>> [web]
>>>> 10.128.2.215
>>>> 10.128.2.108
>>>
>>>
>>>
>>> group_vars/web.yml:
>>>
>>>> ---
>>>> ansible_user: ansibleadmin
>>>> ansible_password: Passw0rd
>>>> ansible_port: 5985
>>>> ansible_connection: winrm
>>>> ansible_winrm_cert_validation: ignore
>>>
>>>
>>>
>>> ansible.cfg:
>>>
>>>> [defaults]
>>>> inventory      = /etc/ansible/inventory.yml
>>>
>>>
>>>
>>> Versions:
>>> Pywinrm 0.2.2
>>> Python 2.7.5
>>> Ansible 2.3.1.0
>>> CentOS 7.3.1611 (Core)
>>>
>>>
>>> I have no clue why I can't get it to work with a local account and am 
>>> hesitant to move on to kerberos AD authentication if I can't even get this 
>>> to work. Any advice? 
>>>
>>

-- 
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/4881312d-4699-4c26-8db2-172b876be9b3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to