If a coworker gets a new computer, they can't access our database from any other user account on the computer other than one called 'ctap' and I can't figure out why.
We work with two servers, the one running SQL Server (tulip) and the one running our Access front-end (panda). Our data is stored as SQL Server tables on tulip, but all data manipulation and data entry occurs from the Access program on panda, so we're working with linked tables over an ODBC connection. In the past when I've tried to add new users I get an error message saying "Login failed for user (null). Not a trusted connection." But there's a workaround that I just figured out. If a create a user account on each client called 'ctap' with the same password, I can make the connection to the database just fine. On both servers, users are placed in a group called CTAP_Professionals, presumably because one of the users on SQL Server is labeled tulip\CTAP_professionals (the user 'ctap' is also part of this group). I can't figure out why this one user has access, but no other users can get access, even though their profiles are the same!