check out this post for detailed items to check on your setup
https://groups.google.com/forum/#!topic/ansible-project/DJqUWVnH5Go
On Wed, Jul 12, 2017 at 9:42 PM, Bluesky <378408...@qq.com> wrote:
> hello，Skinnedknuckles
> I ask you how the final solution to the problem? I also encountered this
hello，Skinnedknuckles
I ask you how the final solution to the problem? I also encountered this
Error, hope you can get your help, thank you very much!
在 2014年9月24日星期三 UTC+8下午10:51:28，skinnedknuckles写道：
>
>
> I'm having trouble getting win_ping to work. Here is my info:
> Fedora 20
> Ansible 1.7.
There must be a problem with my encryption because when I run this line in
powershell it works.
winrm set winrm/config/service '@{AllowUnencrypted="true"}'
On Wednesday, September 24, 2014 9:51:28 AM UTC-5, skinnedknuckles wrote:
>
>
> I'm having trouble getting win_ping to work. Here is my in
It looks like it's still trying to use ssh instead of winrm, which
indicates your group vars still aren't being used. Based on your inventory
from the messages below, your host doesn't appear to be listed in a
"windows" group, so it won't use group_vars/windows.yml.
Try adding the following lines
My windows.yml file is in the group_vars directory and contains
---
ansible_ssh_user: ansmgr
ansible_ssh_pass: ansiblepw
ansible_ssh_port: 5986
ansible_connection: winrm
Here is my output
[ansmgr@LinuxControlMachine etc]$ *ansible ADS-6999 -m win_ping -*
<123.123.123.123> ESTABLISH CONNECTION
Sorry for the confusion, I was replying to the incorrect assertion above
and missed the scrollback.
Please make sure you file a ticket for this one as tracebacks in Ansible
are definitely bugs, though it sounds like you need to either use
--ask-pass or set ansible_ssh_pass -- though the variable n
ansible 1.7.1 (this and other details are in the original posting)
On Mon, Sep 29, 2014 at 7:03 AM, Michael DeHaan wrote:
> ansible_ssh_host does not imply the transport.
>
> Let's ask the starter question, "what's the output of ansible --version" ?
>
>
>
> On Mon, Sep 29, 2014 at 6:36 AM, J H
ansible_ssh_host does not imply the transport.
Let's ask the starter question, "what's the output of ansible --version" ?
On Mon, Sep 29, 2014 at 6:36 AM, J Hawkesworth <
j.r.hawkeswo...@googlemail.com> wrote:
> Try not setting the ansible_ssh_host in your inventory - I think this
> might be f
Try not setting the ansible_ssh_host in your inventory - I think this might
be forcing it to attempt ssh transport, which of course isn't going to work
for windows hosts.
In other words, change
[ads800s]
ADS-6999 ansible_ssh_host=123.123.123.123
to
ads800s]
ADS-6999
and ensure ADS-6999 can e
