Your browser does not allow storing cookies. We recommend enabling them.


Authentication Fails for Domain Account on Tectia Server on Windows

Symptom: User authentication fails for domain accounts on Tectia Server.

This problem could be caused by a number of reasons:

Start the troubleshooting by checking that you are able to log in to the Windows host where the Tectia Server is installed. Attempt the login at the console using domain accounts. Additionally, check that the Windows host where the Tectia Server is installed can reach the Domain Controller. While Windows allows you to log in (by using cached passwords) at the console even when the Domain Controller is down, Tectia Server requires active communication with the Domain Controller in order to authenticate domain users.

Another possible cause for this is having additional groups in the "Pre-Windows 2000 Compatible Group" on the Domain Controller. Some Windows updates, such as the multilanguage pack, can result in adding entries to this group, which breaks the mapping for the groups' SIDs, and the Tectia Server is no longer able to create access tokens for the domain users. In order to prevent this, check on the Domain Controller that the "Pre-Windows 2000 Compatible Group" contains only the "Authenticated Users" group.




What to read next:

  • Reduce Secure Shell risk. Get to know the NIST 7966.

    The NISTIR 7966 guideline from the Computer Security Division of NIST is a direct call to action for organizations regardless of industry and is a mandate for the US Federal government.
    Download now
  • ISACA Practitioner Guide for SSH

    With contributions from practitioners, specialists and SSH.COM experts, the ISACA “SSH: Practitioner Considerations” guide is vital best practice from the compliance and audit community.
    Download now