General discussion

Locked

Multi-User ODBC connectors onTerm Server

By bmiller95 ·
How can a create a ODBC connector that all users (even those not in the local Admin / Power users group) use to connect to a database on SQL 7.0 Server.???

Senario: Win2K Terminal Server w/ Citrix 2000 Metaframe. I have an Database Application that uses an ODBC connector to connect to an SQL 7.0 database / server.
When I create the ODBC connector as a User w/ admin privaledges (only those user in the local admin group or power users group can use the "system DSN - ODBC" connector. If any other user log's on they receive an error "Can connect to ODBC Data source".

Since the problem is NT rights -- how can I ?change the security to add/assign a specific NT user group (users who need to access this database)the appropriate rigts.
I've looked in the local Security policies and could not see anything that jumped out at me, that would work.

I do know that if I place the users in the local Power users group, that this works --- but then I don't want to give these users that much power on the local member server.

I would appreciate any suggestion or help.

Sincerely,

Bill Miller, MCSE
Network Engineer
Alpern, Rosenthal & Co.
wmiller@alpern.com

This conversation is currently closed to new comments.

4 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

Multi-User ODBC connectors onTerm Server

by rawright In reply to Multi-User ODBC connector ...

Bill, I just started studying SQLServer this week, so I'm far from being an expert. While exploring the System DSN in Control Panel, I noticed that the SQLServer source, by default, is set to grant access using SQLS7 internal security, rather than WinNT authentication. This implies that the Admin must create a user account in SQLS7 for each user or group requiring access. I would create a group - DBUsers - and add all those requiring access to it, then grant access in SQLS7 to the group. The details of the process are lengthy, but well documented in the Books Online installed with SQLServer.

Another option that might work would be to use the configuration button for each DSN to switch authentication methods so that permissions are determined by the WinNT logon, but as I said, I'm just getting started on this. It seems to me that this method would give you fewer headaches in the long run, but I haven't tried it. Good luck.

Collapse -

Multi-User ODBC connectors onTerm Server

by bmiller95 In reply to Multi-User ODBC connector ...

Poster rated this answer

Collapse -

Multi-User ODBC connectors onTerm Server

by bmiller95 In reply to Multi-User ODBC connector ...

This question was closed by the author

Collapse -

Multi-User ODBC connectors onTerm Server

by bmiller95 In reply to Multi-User ODBC connector ...

I actually have found the answer!!

1. Logon to member server as administrator.(you need admin privledges to change any permissions on the keys)
2. Run Regedt32 (this give you access to the permissions on the keys ** do not use regedit)
3. Go toHKLM (local Machine)
4. Software/ODBC (Remember to double-click on the key to open it)
5. File menu - security - permissions.
Add the specific NT Group whom you want to allow access or the group "Domain Users" or even "everyone"-- and give them full privledges (read & write) to "this key and all sub keys" which give them access to all odbc connectors you create and all odbc drivers that are avail on the local machine only.

This method is particular helpful on a mutli-user server such as terminal server.
.... on a single user pc it does not matter, because all the local account groups are already listed and given permissions by default.

My appreciation to Mark Tyrell of Microsoft for his assistance on this problem.

Back to Windows Forum
4 total posts (Page 1 of 1)  

Related Forums