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,
open
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 doe
