In regards to the ports you have stated
* 88 - I believe this is what the Kerberos TGS process uses, the traffic will
be between the Ansible controller and the domain controller not the Windows
host.
* 389 - This is the standard LDAP port, LDAP can use Kerberos auth like WinRM
but Ansible does
You will still need Kerberos to talk to the domain controller in whatever
fashion it uses but the traffic between the Ansible controller and the Windows
host will only need the WinRM port.
--
You received this message because you are subscribed to the Google Groups
"Ansible Project" group.
To
Are you saying none of the standard kerberos ports 88,389,445, 3268 etc are
required for ansible to use kerberos as ansible_winrm_transport, if we
configure either 5985/5986 as default.
Thanks in advance
On Fri, Nov 22, 2019 at 6:06 PM Jordan Borean wrote:
> No, port 5985 is the default port fo
No, port 5985 is the default port for http and 5986 is for https. The auth
selection does not change this, and your Windows host could be configured with
another port instead so you will have to check your configuration with ‘winrm e
winrm/config/listener’.
--
You received this message because
hey,
Does the ansible port requirement for Windows change from 5985/5986 to
corresponding ntml/kerberos depending on ansible_winrm_transport selection
of ntlm/kerberos/credssp etc.
Thanks in advance
--
You received this message because you are subscribed to the Google Groups
"Ansible Projec
