October 22, 2003 at 9:32 am
I have a small home domain network with DSL and a static IP address. I have SQL2K running and I'd like to have a friend access the SQL2K server remotely. When he attempts to connect he gets "User not associated with a trusted SQL server connection"
I've added him to the active directory as a domain administrator, added him to the SQL2K security users login as an system administrator, and we've gone through the "Add New SQL registration Wizard". We've tried both Windows and SQL authentication. Both fail the same way.
Any idea's on what we're missing?
Many Thanks
John
October 22, 2003 at 10:35 am
What are you using for authentication?
SQL Server and Windows Authentication or Windows Authentication ONLY
If it's Windows Authentication, his SQL Server login AND password MUST be the same as his Windows login and password.
-SQLBill
October 22, 2003 at 12:48 pm
First, remove him as a domain admin. Second, take him out of the system admin role. He doesn't need those rights.
1) Create a user account on the SQL Server box (a local account). It can be in the users group. It doesn't need to be in Power Users and heaven forbid in Administrators.
2) Grant that local login rights to logon to the SQL Server (<SQLServerName>\<UserName>). Assign only the rights he needs and nothing more to that login.
3) He needs to create the same user account w/ password on his side.
4) He can either log on to his system using that username and password or he can use the runas command (hold down the shift key and right click the icon if you want to go through the start menu) and start the program with that username and password.
That should allow him to log on using Windows authentication.
K. Brian Kelley
http://www.truthsolutions.com/
Author: Start to Finish Guide to SQL Server Performance Monitoring
K. Brian Kelley
@kbriankelley
November 10, 2003 at 9:10 am
My appologies for not responding sooner to both suggestions. I do appreciate the time and suggestions you each have given.
Accordingly, I am using Windows authentication and I have (since and with your suggestions) been able to connect remotely after creating a new 'local' SQL user account and assigning permissions.
Again - many thanks for your input
John
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply