Discussion Locked

System DSN ODBC to SQLServer

0 helpful
4 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
When I set up a System DSN on users NT 4.0 workstations to Microsoft SQLServer 7, and set the authentication to a SQLServer account, the users are prompted for the password of the SQLServer account. Why isn't the password saved in the DSN? What amI doing wrong and where can I find info on how DSNs work in NT?

4 replies

by curlergirl

Are you putting the username and password in the Advanced options screen when you set up the System DSN (i.e., click the Advanced button on the DSN properties and then fill in the user name and password in the Default Authorization fields)? This is what needs to be done to save the info so that the user can access the database with the rights of that account. Hope this helps!

by jim.schromm

Microsoft requires that SQLServer based authentication prompts for a password each time. Basically, you need to use NT based authentication which is best done by setting up a Global Group on your domain with the users assigned to the global group.On the SQLServer machine set up a Local NT group which has the domain's Global Group as a member. Then assign the Local Group to the database using SQLServer. This is done manually without having a drop down list of NT Groups or users.

This discussion is closed to new replies.