Re: Authentication problem continued



Going by your input there could be 2 problems that I can think off

1) SQL Server is configured for Windows Authentication only and not mixed
authentication

2) The account used to set the security context for the application pool of
your web site has no access to the other box' SQL Server

Gabriel Lozano-Morán
http://www.pointerx.net

"SAL" <SAL_@xxxxxxxx> wrote in message
news:ur%23QOK6HHHA.1468@xxxxxxxxxxxxxxxxxxxxxxx
Hello,
I'm still having trouble getting my app to authenticate correctly.
I have read the tips at:
http://www.devhood.com/messages/message_view-2.aspx?thread_id=72204

and am still having trouble making this happen correctly. Here are my
settings.
SQL Server 2005 db access is required
Web page
Anonymous access is turned off in IIS.
<identity impersonate="true" />
<impersonate="true" />

Connection string is:
packet size=4096;Trusted_Connection=True;data source=NTserver;persist
security info=False;initial catalog=MyTest"

I pass in my user name and password as:

User Id=me;Password=mypassword

When I take out the User Id and Password stuff and put in:
Integrated Security=SSPI

I get logged in, but only on my developement machine and not another box.

When the user name and password is passed in the connection string I get
the login failed for User Id=me

I'm the dbo of this sql server database so I should be able to log in.
However, I need to be able to access this web page from machines other
than my development box also.

Can anyone help me with this? Thanks

S



.



Relevant Pages

  • Re: Windows Authentication in asp.net 2005 to SQL Server?
    ... If the domains do not trust each other, Windows authentication is not going ... Basic authentication sometimes makes the need for Kerberos delegation go ... generic account to do the backend data stuff on our SQL Server. ...
    (microsoft.public.dotnet.framework.aspnet.security)
  • Re: Cannot connect using sa
    ... that's because there isn't generally an advantage to SQL Server ... Windows authentication is significantly more secure. ... >>>from the connection string, couldn't connect, then when I put it back I ...
    (microsoft.public.sqlserver.setup)
  • Re: I dont want to re-invent the Login/Login Wheel - Help with utilities
    ... Yes, if you use .NET1.1, there isn't built-in login control, and more importanltly there isn't ready-to-use membership component to use. ... the membership provider uses SQL Server or SQL Server Express. ... We feel that having the capability to force password change would be a better benefit in securing our application and data access. ... Both Windows authentication and authorization wolud be be fine if we wanted the world to have access to our application data, but not very intuitive for maintaining integrity over our data. ...
    (microsoft.public.vstudio.general)
  • RE: IIS (ASP) -> SQLServer Authentication Issue
    ... I understand that you'd like to use IIS Intergration authentication in the ... and ASP "impersonates" authencitaed users to access SQL Server on ... only kerberos authentication allows double-hops from clients ...
    (microsoft.public.sqlserver.security)
  • Re: SBS Premium Edition .. what way is SQL licenced
    ... Another thing to note in using your SQL Server as a backend database is the ... concept of Forms-based authentication and Integrated Windows authentication. ... thereby requiring individual CALs to access SQL Server. ... Chad A. Gross - SBS MVP ...
    (microsoft.public.windows.server.sbs)

Loading