So to verify the host is actually listening run 'winrm e winrm/config/listener' you should see if there is an actual listener for HTTPS/5986. You can also use your favourite command to check if the port is reachable, e.g. 'nc -zvw10 192.168.1.2 5986'. Once you've verified that you can actually connect to the host on that port and that the remote host is listening to it and there's no firewall in the way that blocks it you can move onto getting SSL/TLS working. This is done through 'openssl s_client -connect 192.168.1.2:5986'.
Thanks Jordan On Saturday, October 8, 2022 at 6:17:35 AM UTC+10 [email protected] wrote: > On Fri, 7 Oct 2022 at 21:29, AdminLP <[email protected]> wrote: > > > > Hi Jordan, > > Thanks for your response.. > > > > We have checked with Network team they are saying that they can see > traffic while scanning from Sources server (ansible) to Destination (WinRM > )servers over 5986 port. > > I don't know your Network team, and I have no way of telling whether > what they claim is true or not, or even know if their statements are > relevant at all. Please read on. > > > Pls let us know if any other info. > > The previous reply asked you to use an openssl command to obtain > relevant debugging information about the connection from the ansible > host to the target system. > You did not provide the results of that - so please do that. > -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/d3885ec2-6034-4a7f-a1ba-4df80a9bed53n%40googlegroups.com.
