[ansible-project] Re: Unable to do basic win_ping from CentOS7 to Windows 2012

2019-07-22 Thread uday kiran
It is working when I kept port: 5985 On Thursday, 31 August 2017 02:14:48 UTC+5:30, Jordan Borean wrote: > > If you have configured WinRM using the ConfigureRemotingForAnsible.ps1 > script I would highly advise you to use HTTPS over port 5986 instead of > HTTP. For one HTTP is sent over in clear

[ansible-project] Re: Unable to do basic win_ping from CentOS7 to Windows 2012

2017-08-31 Thread 'J Hawkesworth' via Ansible Project
What are you trying that produces the access denied message? On Thursday, August 31, 2017 at 11:20:25 AM UTC+1, Thijn Bukkems wrote: > > 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 > set

[ansible-project] Re: Unable to do basic win_ping from CentOS7 to Windows 2012

2017-08-31 Thread Thijn Bukkems
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:2

[ansible-project] Re: Unable to do basic win_ping from CentOS7 to Windows 2012

2017-08-31 Thread 'J Hawkesworth' via Ansible Project
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, sohail.p...@gmail.com wrote: > > > Use windows fqdn n

[ansible-project] Re: Unable to do basic win_ping from CentOS7 to Windows 2012

2017-08-31 Thread sohail . prodevans
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 o

[ansible-project] Re: Unable to do basic win_ping from CentOS7 to Windows 2012

2017-08-31 Thread Thijn Bukkems
command line: ansible web -m win_service -a "name=spooler state=stopped" Op donderdag 31 augustus 2017 02:27:02 UTC-7 schreef J Hawkesworth: > > Please share your playbook or command line > > On Wednesday, August 30, 2017 at 11:23:35 PM UTC+1, Thijn Bukkems wrote: >> >> Also tried to stop or start

[ansible-project] Re: Unable to do basic win_ping from CentOS7 to Windows 2012

2017-08-31 Thread Thijn Bukkems
The folder structure looks like this /etc/ansible: ansible.cfg inventory.yml /etc/ansible/group_vars/: web.yml I haven't configured the ansible.cfg in /etc/ansible regarding the cert validation. Op donderdag 31 augustus 2017 02:26:34 UTC-7 schreef J Hawkesworth: > > Its odd that you are getti

[ansible-project] Re: Unable to do basic win_ping from CentOS7 to Windows 2012

2017-08-31 Thread 'J Hawkesworth' via Ansible Project
Please share your playbook or command line On Wednesday, August 30, 2017 at 11:23:35 PM UTC+1, Thijn Bukkems wrote: > > Also tried to stop or start the print spooler just to test another > command.. This is what's in the log > > 2017-08-30 17:19:53,300 urllib3.connectionpool Starting new HTTPS >

[ansible-project] Re: Unable to do basic win_ping from CentOS7 to Windows 2012

2017-08-31 Thread 'J Hawkesworth' via Ansible Project
Its odd that you are getting the insecure request warnings - I am wondering if you are running ansible from a folder with a different ansible.cfg in it perhaps, as the ansible_winrm_server_cert_validation: ignore doesn't seem to be taking effect. On Wednesday, August 30, 2017 at 10:55:31 PM UTC

[ansible-project] Re: Unable to do basic win_ping from CentOS7 to Windows 2012

2017-08-30 Thread Thijn Bukkems
Also tried to stop or start the print spooler just to test another command.. This is what's in the log 2017-08-30 17:19:53,300 urllib3.connectionpool Starting new HTTPS connection (1): .domain 2017-08-30 17:19:53,314 urllib3.connectionpool Starting new HTTPS connection (1): .domain 2017

[ansible-project] Re: Unable to do basic win_ping from CentOS7 to Windows 2012

2017-08-30 Thread Thijn Bukkems
Not sure if you would know the answer to this and I should probably start a new thread but for some reason the -m setup command doesn't return any values. When run, it looks like I'm getting an empty array. P.s. I blanked out hostnames for security reasons [admin@localhost ansible]$ ansible -m

[ansible-project] Re: Unable to do basic win_ping from CentOS7 to Windows 2012

2017-08-30 Thread Jordan Borean
No worries, glad I could help. -- 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 ansible-project+unsubscr...@googlegroups.com. To post to this group, send email

[ansible-project] Re: Unable to do basic win_ping from CentOS7 to Windows 2012

2017-08-30 Thread Thijn Bukkems
Jordan's reply fixed the issue. I had ansible_winrm_cert_validation instead of ansible_winrm_server_cert_validation which was the issue. I also took his advice regarding https. Thanks Jordan. -- You received this message because you are subscribed to the Google Groups "Ansible Project" group.

[ansible-project] Re: Unable to do basic win_ping from CentOS7 to Windows 2012

2017-08-30 Thread Jordan Borean
If you have configured WinRM using the ConfigureRemotingForAnsible.ps1 script I would highly advise you to use HTTPS over port 5986 instead of HTTP. For one HTTP is sent over in cleartext and your credentials can be seen by anyone listening in. The other warning you are getting is because the c