"YUNG LIE" <yung@allways.net> wrote in message
news:303401c428b4$25d8dc50$a101280a@phx.gbl...
> My connection from a web page to my SQL Server was
> working when my connection string is:
> ...Trusted Connection=no; uid=sa; pwd=sapassword;"
>
> It stopped working when I change it to:
> ...Trusted Connection=yes;"
>
> I get this error message:
> Microsoft OLE DB Provider for SQL Server error '80040e4d'
> Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.
> /xxxx.asp, line 32
>
> My SQL server security Authentication is set to SQL
> Server and Windows.
>
> I ran the microsoft identity check scrip on that page to
> see what identity i'm assuming on that page and this is
> the result:
>
> HttpContext.Current.User.Identity
> Name: domain\myusername
> IsAuthenticated: Ture
> AuthenticationType: Negotiate
>
> WindowsIdentity.GetCurrent()
> Name: domain\IWAM_MACHINENAME
> IsAuthenticated: Ture
> AuthenticationType: NTLM
>
> THRED.cURRENTpRINCIPAL.IDENTITY
> Name: domain\myusername
> IsAuthenticated: Ture
> AuthenticationType: Negotiate
>
>
> Therefore I should, in no way, show up as "ANONYMOUS" as
> the error message suggests.
>
> Also domain\myusername is set up in my SQL Server with
> the proper permission to run the procedure the web page
> requests.
>
>
> please help...
>
>
>
>
>

> My connection from a web page to my SQL Server was
> working when my connection string is:
> ...Trusted Connection=no; uid=sa; pwd=sapassword;"
>
> It stopped working when I change it to:
> ...Trusted Connection=yes;"