Windows 2000 Login for SQL Server 2000

I have an application that was developed using VB 6 and uses SQL Server 2000 as the database.  I am using SQL Server authentication in my code to access the data and the SQL Server user is setup and has the correct rights to the tables and stored procedures.  The Windows 2000 Server running SQL Server is part of a workgroup, not a domain.  I am running the application from computers on a seperate domain. I can connect to the SQL Server fine if the login on the computer running the application is the same login name and password, as on the Windows 2000 Server.  If the user's login doesn't exist or the password is different then I cannot connect to the SQL server in my application.  Is there a way to work around this security issue.  I'm confused because I assumed that if the SQL Server authentication user is setup on the SQL Server I should be able to get to the data reguardless of who the Windows login is.

Thanks,
Scott
sborchersAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

marc_nivensCommented:
It sounds like the application itself is sending the logged in credentials.  If that is the case you will need to code it to pass credentials the user supplies, not the credentials of the logged on user.
0
msiceCommented:
Are you sure that your SQL server is not in mixed authentication mode?
0
sborchersAuthor Commented:
msice,
Yes my server is in mixed authentication mode.  I am passing the SQL Server user name and password to access the database.  If the a user tries to access the data with a username and password that are the same as a username and passoword setup on the Windows Server running the SQL Server then I can connect to the SQL Server. If the username and password do not exist on the Windows Server running the SQL Server then I can't connect to the SQL Server.
0
How do you know if your security is working?

Protecting your business doesn’t have to mean sifting through endless alerts and notifications. With WatchGuard Total Security Suite, you can feel confident that your business is secure, meaning you can get back to the things that have been sitting on your to-do list.

sborchersAuthor Commented:
marc nivens,

I am passing the correct credentials to access SQL Server using SQL Server authentication.  The only way I know how to pass the correct credentials to the Windows server is by mapping a drive in code, but I'm not sure I want to do that becuase I have over 50 pc's with different mapped drives.
0
msiceCommented:
Have you thought about using SQL Server only authentication.
0
sborchersAuthor Commented:
The only two authentication modes are SQL Server and Windows or Windows only.
0
msiceCommented:
Are you using an ODBC connection?
0
sborchersAuthor Commented:
Yes, I am using an ODBC connection.
0
msiceCommented:
If you connect through ODBC, in the ODBC Administrator, choose SQL Server authentication when you configure the data source.
0
msiceCommented:
"I'm confused because I assumed that if the SQL Server authentication user is setup on the SQL Server I should be able to get to the data reguardless of who the Windows login is." - Yes you should. In the ADO connection string, where you include the parameters "UID" and "PWD" when you use ODBC, and "User ID" and "Password" when you use the SQLOLEDB provider set it to the sa user and pass for all and work backwards from there.
0
sborchersAuthor Commented:
I am doing that currently.  I am using SQL Server Authentication in my ODBC, but if I don't have the username and password setup on the Windows 2000 Server for the user of the computer that is trying to run the application then I receive an error.  I'm not sure if the problem is because I'm trying to run the application in a domain and the WIndows/SQL Server is in a seperate workgroup, but it is a problem.
0
sborchersAuthor Commented:
Good thought, I'll try that.  And yes I thought I should be able to connect regardless of the windows user.
Thanks
0
msiceCommented:
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
sborchersAuthor Commented:
Client OS we are working with currently is Windows 200 Pro, but when live we will be using Win95,98 and 200Pro.  The sa user still did not work.  I think I'm going to chase the named pipes IPC issue.
0
sborchersAuthor Commented:
The Guest account wan't enabled.  I enabled it and the connection worked.  Exactly what I was looking for.  I new there had to be something with the NT security.
Thanks,
Scott
0
msiceCommented:
Yes and take a look at the 98/95 issues as well they will require attention.
0
msiceCommented:
Cool glad to help and that you got it working.
Thank You for the points and the grade.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
OS Security

From novice to tech pro — start learning today.

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.