SSH

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 on to the Windows host where Tectia Server is installed. Attempt the logon at the console using domain accounts. Additionally, check that the Windows host where Tectia Server is installed can reach the Domain Controller. While Windows allows you to log on (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 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.