Re: Unable to establish connection to sql database using trusted account
From: Greg Merideth (beta-gm_at_forwardtechnology.net)
Date: 07/27/04
- Next message: Mueller: "Re: Opening Documents"
- Previous message: Tom Chmielenski: "Re: I can't test Office 2003 Std with WSS as promised"
- In reply to: ssr: "Unable to establish connection to sql database using trusted account"
- Messages sorted by: [ date ] [ thread ]
Date: 27 Jul 2004 13:16:02 -0700
"ssr" <ssr@lubrizol.com> wrote in message news:<4f6a01c473e9$19861b90$a301280a@phx.gbl>...
> We were unable to establish a connection to a database on
> a sql server using a trusted account. The sql database is
> on a different server than SharePoint. When attempting
> the connection, the sql log shows the following error
> message:
>
> Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'
>
> How can you tell the identity of the account that is used
> to create the connection?
>
> If we use a standard account, passing it a user name and
> password, we are able to connect. This however, is not
> condoned by our security department.
Add the account NT AUTHORITY\ANONYMOUS LOGON into SQL server and give
it access to the databases/tables that you need to access from the
Sharepoint machine. Then in the connection string use
server=myserver;integrated security=sspi;database=sharepointdb;
then Sharepoint will talk to SQL without putting usernames/pw's in the
connection string.
- Next message: Mueller: "Re: Opening Documents"
- Previous message: Tom Chmielenski: "Re: I can't test Office 2003 Std with WSS as promised"
- In reply to: ssr: "Unable to establish connection to sql database using trusted account"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
