Re: That $%#@ "Trusted Connection" Thing Again...

From: Sue Hoegemeier (Sue_H@nomail.please)
Date: 05/14/02


From: Sue Hoegemeier <Sue_H@nomail.please>
Date: Tue, 14 May 2002 11:34:07 -0600


There are some situations where the authentication is
ignored (FIX: SQL Server ODBC Driver Ignores Authentication
Setting - Q279526) but that doesn't appear to be your issue.
You can check anyway though.
You probably need to provide more details and try some other
things for anyone to help you out with this:
Connecting with what - ODBC, OLE DB?
What is the connection string you are using?
What version of MDAC? Have you run Component checker to
verify the MDAC installation?
Have you monitored with profiler?
Can other clients connect to this server using this a SQL
Login?
What specifically have you checked? Otherwise we'll just
keep suggesting things you have already checked which won't
be very productive.

-Sue

On Tue, 14 May 2002 11:06:32 -0600, "Jeff M."
<Jeff.Menten@McKesson.com> wrote:

>Sigh... yeah, I checked that also (from a 'way earlier post). The connection
>string worked fine when connecting to a different SQL server, just not this
>one. I have been all over the configurations of the two machines, trying to
>match them as closely as possible. I have found no discrepancies yet, which
>is frustrating.
>
> - Jeff.
>
>"Sue Hoegemeier" <Sue_H@nomail.please> wrote in message
>news:d0d2euct671rj6701k9q0isd53ctrp349r@4ax.com...
>> Make sure the connection string is correct. You can find
>> examples at:
>> http://www.able-consulting.com/ADO_Conn.htm
>>
>> -Sue
>>
>> On Tue, 14 May 2002 09:49:30 -0600, "Jeff M."
>> <Jeff.Menten@McKesson.com> wrote:
>>
>> >I thought of that also, and checked authentication early on. In fact,
>other
>> >servers can connect to the database using SQL authentication if I create
>a
>> >System DSN on those machines. The issue just seems to be in the ADO
>DSN-less
>> >connection...
>> >
>> > - Jeff.
>> >
>> >"Sue Hoegemeier" <Sue_H@nomail.please> wrote in message
>> >news:aqb2eu0dj20dqm4u5pegvro4rjcn2lmrq6@4ax.com...
>> >> Make sure the server is configured for Windows and SQL
>> >> Server authentication. If you can connect with Windows
>> >> Integrated security but get the error "not associated with a
>> >> trusted connection" when using SQL logins, it's usually due
>> >> to the server being configured for Windows authentication
>> >> only.
>> >>
>> >> -Sue
>> >>
>> >> On Mon, 13 May 2002 15:35:12 -0600, "Jeff M."
>> >> <Jeff.Menten@McKesson.com> wrote:
>> >>
>> >> >I know there have been many posts exploring this issue, but it's still
>> >not
>> >> >fixed.
>> >> >
>> >> >When I try to connect to a SQL7 database using a DSN-less connection,
>or
>> >> >from within Access by defining a connection, I get the error
>> >> >
>> >> >"Test connection failed because of an error in initializing provider.
>> >Login
>> >> >failed for user 'sa'. Reason: Not associated with a trusted SQL Server
>> >> >connection."
>> >> >
>> >> >I can connect successfully to a different SQL server (which I am
>trying
>> >to
>> >> >clone), and I can connect successfully using Windows Integrated
>security
>> >to
>> >> >this server. I have reviewed the Server Network configuration, and
>Named
>> >> >Pipes is at the top of the list. The DSN-less connections are using
>the
>> >> >correct strings (verified from a posting quite a while back).
>> >> >
>> >> >Is this a problem with configuration on the server, or with
>configuration
>> >on
>> >> >the user's workstation?
>> >> >
>> >> >Does anyone have any more suggestions?
>> >> >
>> >> >
>> >>
>> >
>>
>



Relevant Pages

  • Re: Remote connection failed
    ... If you are going over a remote connection or are not logging ... into the domain where SQL Server is then no, Windows ... authentication won't work. ...
    (microsoft.public.sqlserver.connect)
  • Re: C# connection string using Windows NT Authentication
    ... you indicate that you are using Windows ... If you are connecting to a local instance of SQL Server on your ... it sounds much less like a connection string ... you'll need to resort to SQL Authentication. ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Problems Using Laptop As SQL Server - Log On Failed
    ... > connected to the network and no password for windows. ... > the name of the laptop as name of the SQL Server. ... > trusted SQL Server connection ... you have to change the authentication mode... ...
    (microsoft.public.sqlserver.msde)
  • Re: No Windows, Only SQL Server Authentication
    ... To establish a Windows authenticated connection from OSQL, ... SQL Server programatically. ... Your connection string needs to specify the type of authentication desired. ...
    (microsoft.public.sqlserver.security)
  • understanding chkrootkit: sshd section
    ... Rhosts Authentication disabled, originating port will not be trusted. ... Secure connection to %.100s on port %hu refused%.100s. ... Warning: Remote host refused compression. ... Received RSA challenge from server. ...
    (comp.os.linux.security)

Quantcast