This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Active Directory SSO Problems

We have our Web Filter Profiles setup to use Active Directory SSO authentication.  This has been working fine for a while.  Recently, users have sporadically not been able to access websites.  Examining the logs shows that the users are not being authenticated.  To troubleshoot I started by opening the Servers tab under Authentication Services and verifying the AD server connection.  Opening the server and clicking "Test" for Test Server Settings gives the following error message "Error: Server exists and accepts connections, but bind to ldap://x.x.x.x:389 failed with this Bind DN and Password."  If I enter the password again for the Bind DN and click "Test" the server test passes.  Now, when I click "Save" and then go back into the server and click on "Test" again I get the same error message as before.  The Bind DN we have been using for years is in the following format: CN=user,CN=Users,DC=domain,DC=com.  I have tried switching to: user@domain.com and get the same results.  Any ideas?



This thread was automatically locked due to age.
Parents
  • Hi,

    are u using NTLM or Kerberos?

    If NTLM, check if NTLM authentication is enabled (AD / PCs).

    Local Security Policy --> Security Settings --> Local Policies --> Security Options --> Network Security --> LAN Manager authentication level = Send LM & NTLM - use NTLM2 session security if negotiated

Reply
  • Hi,

    are u using NTLM or Kerberos?

    If NTLM, check if NTLM authentication is enabled (AD / PCs).

    Local Security Policy --> Security Settings --> Local Policies --> Security Options --> Network Security --> LAN Manager authentication level = Send LM & NTLM - use NTLM2 session security if negotiated

Children
No Data