After seeing your suggestion, tried with Kerberos and NTLM
This is what i see
10.67.104.45 | UNREACHABLE! => {
"changed": false,
"msg": "Failed to connect to the host via ssh: OpenSSH_7.4p1, OpenSSL
1.0.2k-fips 26 Jan 2017\r\ndebug1: Reading configuration data
/etc/ssh/ssh_config\r\ndebug1: /etc/ssh/ssh_config line 51: Applying
options for *\r\ndebug1: auto-mux: Trying existing master\r\ndebug1:
Control socket \"/root/.ansible/cp/966bc611a0\" does not exist\r\ndebug2:
resolving \"10.67.104.45\" port 22\r\ndebug2: ssh_connect_direct: needpriv
0\r\ndebug1: Connecting to 10.67.104.45 [10.67.104.45] port 22.\r\ndebug2:
fd 3 setting O_NONBLOCK\r\ndebug1: connect to address 10.67.104.45 port 22:
Connection timed out\r\nssh: connect to host 10.67.104.45 port 22:
Connection timed out\r\n",
"unreachable": true
}
I must be missing something, please guide me where exactly going wrong.
On Saturday, January 19, 2019 at 4:13:59 AM UTC+5:30, Jordan Borean wrote:
>
> I forgot to mention that running over http (like you are) for basic auth
> will only work if you have disabled message encryption on the Windows host.
> Do not do this, do something sane like running over https or use an
> authentication option that supports message encryption like Kerberos or
> NTLM.
>
--
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/ba47b394-2d35-43ac-a9c0-66f89976e6eb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
