Trouble using connection string to authenticate on SQL Server
The following connection string works fine when I'm already logged in to a computer on our intranet:
"Server=sname;User ID=my.name;Database=Databa
But from home, using a VPN connection into the intranet, the connection string fails because I'm obviously not "logged in".
I tried the obvious approach of adding my password:
"Server=sname;User ID=my.name;Database=Databa
But this doesn't work. For future reference, I normally log on to a computer named
"Corp123" with a domain of "corpdomain".
I'm using SQL Server 2008, and Visual Studio 2010 to perform the connection using C#.
If source is my connection string, then the following is the code I use to log in from C#:
SqlConnection conn = new SqlConnection(source);
conn.Open();
SqlCommand cmd = new SqlCommand(@"StoredProcedu
....
I appreciate any help anyone can give. I believe, most likely, that I have the permission to access the database as long as my connection string contains authentication information. But if it's likely I need special rights, please tell me what specific rights I need to ask for from my database adminsitrator. (My DBA's head pops off in response to vague security requests).
"Server=sname;User ID=my.name;Database=Databa
But from home, using a VPN connection into the intranet, the connection string fails because I'm obviously not "logged in".
I tried the obvious approach of adding my password:
"Server=sname;User ID=my.name;Database=Databa
But this doesn't work. For future reference, I normally log on to a computer named
"Corp123" with a domain of "corpdomain".
I'm using SQL Server 2008, and Visual Studio 2010 to perform the connection using C#.
If source is my connection string, then the following is the code I use to log in from C#:
SqlConnection conn = new SqlConnection(source);
conn.Open();
SqlCommand cmd = new SqlCommand(@"StoredProcedu
....
I appreciate any help anyone can give. I believe, most likely, that I have the permission to access the database as long as my connection string contains authentication information. But if it's likely I need special rights, please tell me what specific rights I need to ask for from my database adminsitrator. (My DBA's head pops off in response to vague security requests).
Who is Participating?
it means that indeed, the SQL Server cannot tell your current windows login information.
and using windows authenticaation will only work if the sql server can "tell" your windows login.
otherwise, you will need to use sql logins.
and using windows authenticaation will only work if the sql server can "tell" your windows login.
otherwise, you will need to use sql logins.
Reading your message, I have no idea (a) whether or not I may be able to log in using a connection string, and (b) what request to my database admin would result in success.
Remember, I do have access to my own username and password, and can supply them in the connection string if this is helpful.
in summary, does your answer mean (a) or (b) below:
(a) I need to supply authentication information _within_ the connection string, in which case the question becomes what changes are needed to the string in order to authenticate?
or
(b) a username must be added to SQL Server 2008 before any such connection string would work
Remember, I do have access to my own username and password, and can supply them in the connection string if this is helpful.
in summary, does your answer mean (a) or (b) below:
(a) I need to supply authentication information _within_ the connection string, in which case the question becomes what changes are needed to the string in order to authenticate?
or
(b) a username must be added to SQL Server 2008 before any such connection string would work
A tertiary possibility is that VPN's permit logging on to the network, in which case the question would become, how does one log in remotely to a vpn network to satisfy a SQL Server database. on that vpn.
Question has a verified solution.
Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.
Have a better answer? Share it in a comment.
All Courses
From novice to tech pro — start learning today.
-
Course of the Month8 days, 6 hours left to enrollMonitoring and Operating a Private Cloud with System Center 2012 R2 273 lessons
so, either your local windows machine login information must be added (as windows login) to the sql logins (however, I am not sure if the SQL Server can resolve - and hence trust - the remote login source... )
otherwise, you need indeed a classic sql login created in the sql logins, and THAT login/password shall be passed in the connection string, but you then need to remove the part "trusted_connection ..."