rl30
Mon Aug 18 13:38:22 CDT 2003
I found
http://support.microsoft.com/default.aspx?scid=kb;en-us;810572
"rl30" <rl30@hotmail.com> wrote in message
news:eyHQcjYZDHA.388@TK2MSFTNGP10.phx.gbl...
> Hey friends
> using a username and password its not the best way for securing database
> we use role for increase security in our intranet
> we want to use the the nt authentication
>
> domain\toto -> domain\grouptoto -> IIS -> SQL Server( role toto)
>
> all servers is in the domain
> toto is a account of the domain
>
>
> "William Ryan" <dotnetguru@comcast.net> wrote in message
> news:0a2001c3637b$c80a6ec0$a001280a@phx.gbl...
> I think you have to use Mixed Mode Authentication and
> explicitly use a username and password that has the
> permissions granted. Since the remote machine isn't on
> the domain the trust can't be made.
>
> Try switching your SQL Server to Mixed mode and supply a
> username and password in your connection string...make
> sure SSPI isn't being used.
>
> In my personal experience, I'd recommend using an account
> with limited access to server resources and ideally use
> Stored procs and let them handle the permissioning.
>
> Good Luck,
>
> Bill
>
> W.G. Ryan
> dotnetguru@comcast.nospam.net
> www.knowdotnet.com
> >-----Original Message-----
> >ASP.NET vs SQL Server¸
> >
> >I have an ASP.NET Application
> > In IIS I checked the Integrated Windows Authentication
> > option
> >
> >In Web.Config the connection string include Integrated
> > Security = SSPI
> >and Impersonate=true in Web.Config
> >
> > When I start then Web Application I have this messge
> > Login failed for user '(null)'. Reason: Not associated
> > with a trusted SQL Server connection.
> > Could you help me
> >
> > PS My account have the permission to connect to SQl
> Server
> >
> >the security model is base on role security
> >I have many users
> >
> >
> >
> >
> >.
> >
>
>