Hello Jordan Thanks for your response.
The target server already has Powershell3.0, I went ahead and installed the hotfix and reinstalled the http and https listeners, but still isn't working. The thing with TLS1.2 is that I have 2 win 2008 servers and they both have exact same registry settings wrt the TLS ciphers and it works fine on one and does not work on the other. All Win RM commands yield same results in one of the servers and break on the other. Do you have any other ideas? Thanks Kartik On Thursday, September 13, 2018 at 3:58:06 PM UTC-5, Jordan Borean wrote: > > Hi > > The error you are seeing is that because the underlying HTTP stack on > Windows is beaking the connection and may or may not be related to WInRM > itself. If you are trying to connect to server 2008 then you will need > PowerShell v3.0 which has an issue with the memory settings. Make sure that > you have installed this hotfix > https://docs.ansible.com/ansible/latest/user_guide/windows_setup.html#winrm-memory-hotfix > . > > The other issue I know that could cause this is the recent TLSv1.2 patch > Microsoft has released which effectively breaks compatibility. I came > across a bug with it and found even Microsoft products are unable to use > TLS v1.2 with it enabled, you can find out more details about this here > https://social.msdn.microsoft.com/Forums/en-US/f4b0e1d5-4a7f-4e6a-a196-a54c50849ff8/server-2008-and-tlsv12-server-issues-kb4019276?forum=winservergen. > > If you have KB4019276 and have explicitly enabled the TLSv1.2 ciphers in > the registry then this would have to be undone before Ansible will work > with it. > > 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 ansible-project+unsubscr...@googlegroups.com. To post to this group, send email to ansible-project@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/edb857c5-46f1-4411-9fc2-455639e985a3%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
