From bc3686c7843050c27168441facc00cb5e82e73b4 Mon Sep 17 00:00:00 2001 From: jlownie Date: Fri, 15 Jul 2022 03:11:18 +1000 Subject: [PATCH] Adding some troubleshooting detail for Kerberos connections (#78197) --- docs/docsite/rst/win_guide/windows_winrm.rst | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/docsite/rst/win_guide/windows_winrm.rst b/docs/docsite/rst/win_guide/windows_winrm.rst index 6a1ffec4302..fef54ce8446 100644 --- a/docs/docsite/rst/win_guide/windows_winrm.rst +++ b/docs/docsite/rst/win_guide/windows_winrm.rst @@ -483,6 +483,8 @@ Kerberos is reliant on a properly-configured environment to work. To troubleshoot Kerberos issues, ensure that: * The hostname set for the Windows host is the FQDN and not an IP address. + * If you connect using an IP address you will get the error message `Server not found in Kerberos database`. + * To determine if you are connecting using an IP address or an FQDN run your playbook (or call the ``win_ping`` module) using the `-vvv` flag. * The forward and reverse DNS lookups are working properly in the domain. To test this, ping the windows host by name and then use the ip address returned