August 20, 2004 at 2:15 pm
HI There
Recently we rolled out new images with MDAC 2.7 and some with 2.8. As soon as users fired up a small application that was previously using admin shares to allow cross domain authentication to the SQL server we started getting the messege "login fails for user null, not associated with a trusted sql server connection" To get around this I had to hard code the "SA" user name and password into the application to start the session. While this is a working "work around" it is not acceptable to the clients as they feel it is a security issue. I have read a few posting where people have talked about these issues, but no one has come up with a solution. The articles were dated so was hoping some new light could be shed on this matter. We are using Windows 2000 as OS.
Viewed a similar issue with XP here under "Authentication Prob using XP"
Thanks in advance for any help or direction to more information
Thanks Andy
Had to edit post as the post reply button wasn't getting me anywhere, Hope you check back here. Just wanted to clarify on your comment.. are you saying that I need to update the libray on the host? And if sodoes that mean updating the MDAC and OBDC on the host as well?
*****code*****
SQLServer = "DSN=" & maDB_LOC(intIDX).lrdata_dsn & ";SERVER=SQLSERVER;Network=DBMSSOCN;Address=10.0.18.5,1433;UID=" & strLoginID & ";PWD=" & Me.txtPassword
*******End code******
This is the string I use to connect. The user ID and passowrd must be of sufficient authority on the server box or I get the error. Sufficient authority at the moment being SA or myself as administrator. If this still holds true to your previous advice I'll go about building an enviroment i can test the upgrades in.. Thanks
MArc
August 20, 2004 at 4:09 pm
Maybe a network library issue?
August 24, 2004 at 1:57 pm
If you are using Windows Authentication and ODBC, your connect string is in conflict with itself.
Yours:
SQLServer = "DSN=" & maDB_LOC(intIDX).lrdata_dsn & ";SERVER=SQLSERVER;Network=DBMSSOCN;Address=10.0.18.5,1433;UID=" & strLoginID & ";PWD=" & Me.txtPassword
Mine:
Provider=MSDASQL.1;Persist Security Info=False;Extended Properties="DSN=DSNname;DATABASE=DataBase Name;Network=DBMSSOCN;Trusted_Connection=Yes";
The UID and PWD parameters do nothing when using Windows Authentication.
Also, the parameter "Network" and "Address" are redundant. See KB # 229929
If you are using Windows Authentication and OLEDB your connect string isn't quite correct.
Try:
Provider=SQLOLEDB.1;Integrated Security=SSPI;Persist Security Info=False;Catalog=Server Name;Data Source=Database Name;
Michael L John
If you assassinate a DBA, would you pull a trigger?
To properly post on a forum:
http://www.sqlservercentral.com/articles/61537/
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply