I'd add 'use hostnames, not ip addresses' as well, HTTPS (and kerberos/Active Directory) really need hostnames, not ip addresses to work (you may be, I can't tell from your example though). Hope this helps, Jon
On Monday, April 23, 2018 at 3:34:20 AM UTC+1, Jordan Borean wrote: > > It really does sound like DNS is the issue, the problem is due to an > underlying library not being able to establish the connection. You can try > and just setup a raw connection with openssl to verify the host is > resolvable and the HTTPS stack is working on the Windows side. To do this > run, > > openssl s_client -host hostname -port 5986 > > Thanks > > Jordan > -- 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/c5d67b6b-827b-4e5d-a80d-7836fad9c56c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
