Windows Authentication connectionstring 'Login failed for user Gue

From: Ted W9999 (TedW9999_at_discussions.microsoft.com)
Date: 01/07/05 

Date: Fri, 7 Jan 2005 14:15:05 -0800

I have an VB6 client-server application that is currently using mixed mode
authentication to access SQL Server using the sa login. In order to avoid the
sa login, I want to convert the app to use Windows Authentication. So I
changed the connection string to this:

Provider=SQLOLEDB.1;Initial Catalog=mydatabase;Data
Source=mycomputer;Integrated Security=SSPI

This works fine on the local computer, but when I try to connect to another
computer on my network (which worked before) I get an error:

Login failed for user 'ABS3200\Guest'

ABS3200 is the other computer I am trying to connect to.

Okay, so I added a new user (EZA) and password (jackson) to the ABS3200
computer User Accounts. Then I went into SQL Server Enterprise Manager on
ABS3200 and added the EZA user to my database with ddladmin, datareader and
datawriter priviledges.

Then I changed the connection string to:

Provider=SQLOLEDB.1;User ID=EZA;Password=jackson;Integrated
Security=SSPI;Initial Catalog=mydatabase;Data Source=ABS3200

I still got the same error, so I went on the Internet and researched and
tried a score of variations for the connection string. Same problem.

Then I got smart (I thought). I created a "TEST.UDL" file on my desktop and
tried to have Windows configure the connection string for me. No dice. Same
problem.

I am sure I am missing something obvious here. My goal is this:

Allow up to 100 intranet connections to the server database without
requiring the configuration of individual login ids on the server for each
one.

Please help! And thanks in advance!

Relevant Pages

  • Re: Persisting user login credentials across pages
    ... In ASP.Net 1.1 most people add the connection string to the web.config file. ... "Siobhan" wrote in message ... >> Sample code requires you to have a login method on your Principal class ... >>> I am not sure how Forms authentication would work - the sample using ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Cant Connect
    ... Then it's likely the authentication settings on the IIS side ... Try adding the IUSR account as a login in SQL Server ... > Cn.open CnStr ...
    (microsoft.public.sqlserver.connect)
  • Re:changing sa password / login
    ... authentication and it worked. ... >I think you might have made changes to SQL Server ... >Authentication" can not recognize SA login which is SQL ... >configuration to use mixed authentication. ...
    (microsoft.public.sqlserver.security)
  • Re: Security question ..
    ... > If you use NT authentication, a user's permissions to a database are ... Your assertion that a user's permissions are independent of the application ... Even using Access and "exploring" will require an ODBC login to SQL Server. ...
    (microsoft.public.sqlserver.server)
  • Re:changing sa password / login
    ... I think you might have made changes to SQL Server ... to make was using Mixed Authentication which will ... Authentication" can not recognize SA login which is SQL ... configuration to use mixed authentication. ...
    (microsoft.public.sqlserver.security)
Loading