resolved the above error by uncommenting the line " 127.0.0.1 localhost " in C:\Windows\System32\drivers\etc\hosts file, then it works
On Thursday, May 4, 2017 at 9:06:29 AM UTC-4, Allen Fisher wrote: > > Thanks Jordan and J. > > I switched to the local administrator account. I also re-ran the > ConfigureRemotingForAnsible script. Now I get the dreaded "the specified > credentials were rejected by the server" error > > PS C:\Users\afisher\Documents> >> C:\Users\afisher\Documents\ConfigureRemotingForAnsible.ps1 -Verbose >> VERBOSE: Verifying WinRM service. >> VERBOSE: PS Remoting is already enabled. >> VERBOSE: SSL listener is already active. >> VERBOSE: Basic auth is already enabled. >> VERBOSE: Firewall rule already exists to allow WinRM HTTPS. >> VERBOSE: HTTP: Enabled | HTTPS: Enabled >> VERBOSE: PS Remoting has been successfully configured for Ansible. > > > I've tried both ports... > > > On Tuesday, May 2, 2017 at 4:18:33 PM UTC-5, J Hawkesworth wrote: >> >> Id suggest switching to port 5986 which is the https winrm listener port >> too. If you have run the configure for remoting script successfully that >> should work. >> >> Also, use ansible 2.3 as it has built in support for acquiring Kerberos >> (active directory) tickets. You still need to configure your krb5.conf and >> install the Kerberos libs as listed in the wndows setup documentation of >> course. >> >> Hole this helps, >> >> Jon >> >> -- 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 post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/c41a7cab-621f-444d-af09-b6cf33793f2f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
