Do you need CredSSP? I would try NTLM if not. Maybe run NETSTAT see if it
shows 5986 open and listening if you haven't already. You can also run
winrm enumerate winrm/config/listener on the host to see if a hostname is
assigned. When did you install pywinrm. If it's been a while might want
sorry my mistake, *ansible_port:=5985* just typing mistake.
and i changed port 5985 to 5986, that is why it is 5986
On Friday, August 4, 2017 at 10:43:30 AM UTC+5:30, benno joy wrote:
>
> Seems like it is using https 5986 and you have specified 5985 , maybe
> because there is a ':' in your
This seems like it could be an SSL wedging issue I've seen from time to
time. It is a weird issue where the combination of the OpenSSL version
(usually older ones) that Python is compiled to use and the cipher suite
selection on the remote server causes the SSL connection to lock up.
Depending
Seems like it is using https 5986 and you have specified 5985 , maybe
because there is a ':' in your variable ansible_port:=5985, is this a
typo ? and make sure the variables are applied to the task/play
On Fri, Aug 4, 2017 at 1:02 PM, Soniya panwar wrote:
> Thanks
Thanks for the reply,
i applied all these thing but not able to solve my problem.
please look into the logs also and provide the possible solution:
2017-08-04 10:19:54,570 urllib3.connectionpool Starting new HTTPS
connection (1): X.X.X.X
2017-08-04 10:19:54,598 urllib3.connectionpool
Also enable credSSP authorization in winrm on the host:
winrm get winrm/config (to see the settings)
winrm set winrm/config/client/auth @{CredSSP="True"}
or Set-Item -Path WSMan:\localhost\Service\Auth\CredSSP -Value $true
I would also check to make sure nothing else is using the default SSH
I think you should run powershell script on your windows machine with
-EnableCredSSP option like below.
powershell.exe -File ConfigureRemotingForAnsible.ps1 -EnableCredSSP
If you have already do this, it is helpful to run ansible module with
-v option.
ansible windows -m win_ping -v