Hello Jordon & dnmv, Thank again for your help
Whatever you suggested its work, Opened the WInRM port on firewall for servers & Disabled SSL version in Registry, now Ansible successfully communicating to WinRM. However we still have few servers where getting below errors. (Telenet is working) Server3- Timeout error. ERROR DURING WINRM SEND INPUT - attempting to recover: WinRMTransportError Bad HTTP response returned from server. Code 413 Server4 - Times out after one hour. Error: WinRMTransportError Bad HTTP response returned from server. Code 413. Server5- Timed out: 192.0.x.x Pls help ...Thanks in Advance. Regards AdminLp On Wednesday, October 12, 2022 at 7:31:39 PM UTC+5:30 [email protected] wrote: > On Wed, 12 Oct 2022 at 15:03, AdminLP <[email protected]> wrote: > > > > Thanks for Response, > > > > We are unable to do Telnet 5986 from Ansible for below server 1 , might > be port is block in security Group.as Ansible servers are in AWS Cloud. > > server 1- > > kerberos: HTTPSConnectionPool(host='10.x.x.x'; port=5986): Max retries > exceeded with url: /wsman (Caused by > ConnectTimeoutError(<urllib3.connection.VerifiedHTTPSConnection object at > 0x7f3d45abe5d0>; 'Connection to 10.x.x.x. timed out. (connect timeout=30)')) > > There is your reason that things don't work. Get this working first. > But as you can see below, there might be more bumps on the road. > > > > > For server 2- Could you more elaborate on this ? wht need to be done to > solve this ? > > kerberos: HTTPSConnectionPool(host='192.x.x.x'; port=5986): Max retries > exceeded with url: /wsman (Caused by SSLError(SSLError("bad handshake: > SysCallError(104; 'ECONNRESET')";);)) > > As stated by Jordan this can be diagnosed by running an openssl command. > > So server1 has a networking problem, and possible an SSL problem > Server1 has no networking problem, but it has an SSL problem. > > Maybe it isn't clear, but you first need network connectivity, and > once that works you need a correct SSL setup. > Network problems will mask SSL problems, effectively. > > None of this is specific to ansible though. > > > > > > > > > > On Monday, October 10, 2022 at 12:57:10 AM UTC+5:30 [email protected] > wrote: > >> > >> 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/36831832-6905-4f33-94de-4673ecae2584n%40googlegroups.com > . > -- 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/60587c1a-dedd-4ab7-b470-dda9b7568545n%40googlegroups.com.
