![]() |
|
Porsche, and the Porsche crest are registered trademarks of Dr. Ing. h.c. F. Porsche AG.
This site is not affiliated with Porsche in any way. Its only purpose is to provide an online forum for car enthusiasts. All other trademarks are property of their respective owners. |
|
![]() |
richardL |
![]()
Post
#1
|
Senior Member ![]() ![]() ![]() Group: Members Posts: 713 Joined: 27-January 03 From: San Diego, CA Member No.: 201 Region Association: None ![]() |
I'm hoping someone here has an answer to this, its driving me crazy.
I have a client using an ODBC connection (on XP Pro), to connect to a SQL Server database. Its set to use NT authentication. You can create the ODBC Datasource, select the appropriate database on the appropriate server and test the connection - all is fine. However, when you check it is actually connected to the another database on that Server, apparently the one defined as the defualt for that server. For instance I created a connection pointing at the standard Northwind database, then I opened Access, linked to an ODBC datasource, selected my new datasource and instead of being offered a list of the tables in Northwind, I was offered a list of the tables in the other default database (not master). I eventually got it to work as I expected, by logging off of the domain account and doing a login as the adminstrator for the local machine. In that account, the DSN worked as expected. I have never seen a DSN with NT authentication simply provide access to another database - it should tell me I don't have access rights to the database selected or whatever. In this case the default database is the clients main live production system, so it appears to be a glaring security risk. Anybody know why this might happen, or even how to make it happen/stop? Thanks. |
![]() ![]() |
richardL |
![]()
Post
#2
|
Senior Member ![]() ![]() ![]() Group: Members Posts: 713 Joined: 27-January 03 From: San Diego, CA Member No.: 201 Region Association: None ![]() |
Its not a public site - its behind a firewall.
I understand all about setting up users to have access to specific databases etc. The reason I am confused is that the connection is setup (as a system DSN, there are no User DSNs) to go to a specific database and its telling me that I am connected to that database, however I am actually accessing a different database, to which I have no access rights. Yet I can query and get data from it (I didn't try an insert since it was their Live system (IMG:http://www.914world.com/bbs2/html/emoticons/biggrin.gif) ) I am sure that there is an issue with user rights, or the way SQL Server is setup - I just can't find anything that would even allow me to specify such behavior. What I am looking for is a way to 'turn it off' from doing this And, yes, logging on as a local admin (not a network admin) on that machine cured the problem - so I had admin privilege on the client, but not on SQL Server and it made a difference. Richard (IMG:http://www.914world.com/bbs2/html/emoticons/idea.gif) |
![]() ![]() |
![]() |
Lo-Fi Version | Time is now: 15th June 2024 - 07:58 PM |
All rights reserved 914World.com © since 2002 |
914World.com is the fastest growing online 914 community! We have it all, classifieds, events, forums, vendors, parts, autocross, racing, technical articles, events calendar, newsletter, restoration, gallery, archives, history and more for your Porsche 914 ... |