CODEWITHSUNDEEP
sql-server-2005windows-authentication
Knox
Knox

Reputation: 2919

User is not associated with a trusted sql server connection - non-domain computer

I'm trying to connect using several different clients to SQL Server 2005 standard, which has been configured to use Windows Authentication. Although the user account exists on the domain, the computer is not joined to the domain. I get the message, "user is not associated with a trusted sql server connection". The question The user is not associated with a trusted SQL Server connection helpfully suggests that I set the SQL server to allow both Windows Authentication and SQL Authentication. I'd rather just stick to Windows Authentication. Is there a workaround?

Upvotes: 0

Views: 3517

Answers (2)

Chad
Chad

Reputation: 574

If the user exists on both domains/computers with the same username/password, it will work. So in your example you would create a new account on the computer running SQL Server with the same username and password as the domain account you are connecting from.

Not ideal if you have a password policy and need to change the password every so often because you always need to keep them in sync, but it works for a temporary fix or non-production usage.

Upvotes: 1

Justin Niessner
Justin Niessner

Reputation: 245429

No. To use Windows Authentication, the machines must be on the same domain. If the machines are not on the same domain (or there is no trust relationship between the domain the server is on and the machine is on), neither will know which domain to use to authenticate the user against (even if the account exists).

Upvotes: 1

Related Questions