Re: Not associated with a trusted SQL Server connection - Windows
- From: "Norman Yuan" <NotReal@xxxxxxxxxxx>
- Date: Tue, 21 Jun 2005 07:15:29 -0700
Another thing I forgot to ask: where are you trying to connect to the SQL
Server from, I mean, which type of application? Windows desktop app or Web
app?
"Kris" <Kris@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:A93DA0A9-F7DA-4C9D-9E95-F74364E3F83F@xxxxxxxxxxxxxxxx
> Norman,
>
> Thanks for ur inputs. I checked the user accounts on the SQL server and I
> found the UserGroup account to which I belong does already exists on the
> server(Builtin/Administrators group). I am trying to connect to sql server
> using the logged in account(windows user account).
>
> Hence not sure what else I am missing here.
>
> Thanks in advance.
> --Kris
>
> "Norman Yuan" wrote:
>
> > Using Windows authentication in SQL server DOES NOT mean that as long as
you
> > logged on to your computer then you can go into SQL Server. It only
means
> > that you do not need supply username/password pair when trying to access
SQL
> > Server, and SQL Server accept who you are as your user account claims.
> >
> > Important thing for many newbie ( no offence here) to know is security
> > include authentication and authorization. Authentication only answers
who
> > you are. Authorization gives you proper access privilege base on who you
> > are.
> >
> > In your case, when you try to access SQLServer with windows user
account,
> > SqlServer knows who you are. But you ( the user account) may still not
have
> > access right to go to a database. First you need to create SQLServer
loggin
> > that matches your Windows user account or a Windows user group which
> > includes your user account. Then you need assign database access
permission
> > to this SQL Server loggin. After this, your Windows account then becomes
> > trusted in the SQLServer.
> >
> > "Kris" <Kris@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> > news:8DD77E7C-AD07-4994-9DE2-FB13C579E5AC@xxxxxxxxxxxxxxxx
> > > Val,
> > >
> > > Can u pl see this post. I have similar problem connecting to a SQL
Server
> > > which is configured as mixed mode authentication. So far I never came
> > across
> > > a situation like this but now I am happened to use mixed mode
> > authentication
> > > but to connect using windows authentication. The authentication is
working
> > > fine if I specify the username and password in the connection string
but I
> > > want to use windows authentication for connections to the server.
> > >
> > > Here is the connectionstring that I am using to connect to SQL server
> > using
> > > SQLClient provider.
> > >
> >
> --------------------------------------------------------------------------
> > ---------------
> > > "Data Source=(local);Database=Northwind;Integrated Security=True;"
> >
> --------------------------------------------------------------------------
> > ---------------
> > >
> > > Am I missing anything here?
> > >
> > > Thanks in advance.
> > > --Kris
> >
> >
> >
.
- References:
- Not associated with a trusted SQL Server connection - Windows Serv
- From: Thomas Woods
- Re: Not associated with a trusted SQL Server connection - Windows Serv
- From: Val Mazur \(MVP\)
- Re: Not associated with a trusted SQL Server connection - Windows
- From: Kris
- Re: Not associated with a trusted SQL Server connection - Windows
- From: Norman Yuan
- Re: Not associated with a trusted SQL Server connection - Windows
- From: Kris
- Not associated with a trusted SQL Server connection - Windows Serv
- Prev by Date: Re: Not associated with a trusted SQL Server connection - Windows
- Next by Date: Re: from mm/dd/yyyy to yyyy/mm/dd
- Previous by thread: Re: Not associated with a trusted SQL Server connection - Windows
- Next by thread: How to capture the SQL statement after parameter substitution?
- Index(es):
Relevant Pages
|