docs: mention security tools that break mTLS with LDAP (#40503)

We have seen several cases of tools that terminate the mTLS connection
from Teleport and drop the client certificates, preventing Teleport
from making an authenticated LDAP connection.

docs/cspell.json

@@ -196,6 +196,7 @@
     "SVID",
     "SVIDs",
     "Shockbyte",
+    "Silverfort's",
     "Slackbot",
     "Sllavd",
     "Smartcard",

docs/pages/desktop-access/troubleshooting.mdx

@@ -81,7 +81,7 @@ If your group policy prevents the desktop from seeing this PIN, the user will
 remain at the login screen even though the smart card was detected.
 
 **Solution:** Ensure that group policy allows specifying credentials during
- RDP connection establishment.
+RDP connection establishment.
 
 Expand Computer Configuration, Administrative Templates, Windows Components,
 Remote Desktop Services, and Remote Desktop Session Host.
@@ -177,7 +177,7 @@ or
 connecting to LDAP server: unable to read LDAP response packet: read tcp 172.18.0.5:35970->;172.18.0.4:636: read: connection reset by peer
 ```
 
-**Solution:**  Enable LDAPS
+**Solution:** Enable LDAPS
 
 This means you do not have an LDAP certificate installed on your LDAP servers,
 or you are trying to make an insecure connection on port `389`. Teleport requires
@@ -239,6 +239,12 @@ in LDAP, you can force the desktop to sync with the following command:
 $ certutil -pulse
 ```
 
+If you have verified that the Teleport CA certificate is properly installed and
+are still seeing this error, check for any security tools or addons that may be
+interfering with the mTLS connection. Tools such as CrowdStrike's LDAP inspection
+or Silverfort's AD adapter are known to terminate TLS and drop the client certificate,
+which prevents Teleport from authenticating.
+
 ## Connection attempts fail
 
 ### RDP server only uses Standard RDP Security