Trusted connection for users in another domain

I have users from domain A and B using Access application to access SQL server tables in domain B. What should I do to anable  user from domain A to connect to SQL Server in domain A over the trusted connction
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

pvs001dAuthor Commented:
Adjusted points to 150
You need to install trust relationship between domains.
pvs001dAuthor Commented:
I have trust relationship enabled and still i can't see users from another domain in SQL security manager. (By trusted connection I mean option in ODBC datasource setup)
Your Guide to Achieving IT Business Success

The IT Service Excellence Tool Kit has best practices to keep your clients happy and business booming. Inside, you’ll find everything you need to increase client satisfaction and retention, become more competitive, and increase your overall success.

For appending to SQL security you need to put users in local group for your domain.
users must have Administrator privilege on the target domain.

Trusting as i means, don't have any relations to ODBC. This trust relationship must be configured for NT domains in User Manager. You need at least one-way trusting where domaid with SQL server is trusting domain in A domain and A domain must be trusted in B. After this you must add users form domain A to local groups in domain B and finally add this groups in SQL security manager
pvs001dAuthor Commented:
Wk, as far as I understand, there is no way to see users from other domain in SQL security manager? The choice is to add them to SQL server domain in order to see in SQL Security Manager?
pvs001dAuthor Commented:
Comment to perezjos: It is too bad to be true.
yes. You need to have users in groups of local domain.
pvs001dAuthor Commented:
What if I manualy add SQL logins through SQL Enterprise Manager? Should I do something else
E.g. Domain1 has SQL server
Domain2 has user user1
Domains trust each other
When I add login name Domain2_user1 through SQL EM and try to connect from that domain, I receive the following message:
Lgin failed:....
Not defined as a valid user of a trusted SQL Server connection.


The statement about the trust relationship needs to be addressed in the NT domain is correct.  The SQL server resides INSIDE an NT server.  Therefore the NT server needs to be told who can be trusted and who can talk to it before it even trys to let someone into SQL.
This is just a suggestions but... don't use trusted connections... use standard security... life is much simpler.

(Hope this helped.)

Install SQL client on your clients m/c and register the SQL server  if necessary, provided your having the permission on server.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
pvs001dAuthor Commented:
What do you mena by 'register SQL server'
Listen, pvs001d....

1) Define a trust relationship whereby the domain containing the SQL Server "trusts" the domain which contains the users (and vica-versa "is trusted by"...) This will allow you to "see" the accounts in Domain A in your User Manager.

2) Create a local group on the SQL Server in question. This will be the receptacle of the trusted domain accounts you need to provide access for.

3) Using SQL Server Security Manager, give the newly-created local group rights to the database(s) you wish them to access. Be sure to automatically create SQl Logins for them using the check box!!!

4) In SQL Enterprise Manager, set the permissions on the object(s) so that the user(s) in question can Select, Update, etc... as necessary.

5) These users will now be able to use SQL Server tables through any means (ODBC, DB-LIB, etc...)

All of the answers above were right in part, just not complete enough.

P.S. If you are using Access to connect, be sure to refresh your ODBC connections on the Access tables using the Connection Manager Add-In

pvs001dAuthor Commented:
Thanks perezjos,that's the answer I'v been looking for.
pvs001dAuthor Commented:
Sorry perezjos, I should have rejceted Ezhill answer. I'll post the points with  a 'question having 'for perezjos' subject. Answer it to get the points you deserved.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server

From novice to tech pro — start learning today.