Re: Reason: Not associated with a trusted SQL Server connection.

From: John Beschler (JohnBeschler_at_discussions.microsoft.com)
Date: 01/15/05 

Date: Sat, 15 Jan 2005 14:03:01 -0800

Thanks to both of you for helping me. Installing SP3a fixed the issue.

"Bob Barrows [MVP]" wrote:

> John Beschler wrote:
> > "Bob Barrows [MVP]" wrote:
> >
> >> John Beschler wrote:
> >>> Bob and Aaron,
> >>>
> >>> Are we really dealing with a connectivity issue here?
> >>
> >> Yes. obviously
> >>
> >>> Here's why I
> >>> ask: I can access the SQL server using several other tools and
> >>> applications on the XP computer.
> >>
> >> You're using your own user account when you do this. That's why it
> >> works. ASP does not run using your user account.
> >>
> >
> > OK, but does that mean ASP uses the IUSR account to access the SQL
> > database?
>
> Sort of. The initial "handshake" between the two computers is done under the
> IUSR account, which then uses the login and password to log into the sql
> server database.
>
> > If so, why the requirement for the User ID and Password in
> > the connection string? I'm still confused as to why windows is
> > trying to use a trusted connection when I am using SQL server
> > authentication. What am I missing in this equation?
> >
>
> There are two sets of authentications: Windows, and SQL Server. The user
> needs to be accepted by Windows/network before it has access to the box on
> which SQL Server is running. Without appropriate credentials on the network,
> it won't even see the box on which SS is runnig. Hence, the message "server
> does not exist". Once access to the box is gained, then authentication to
> gain access to SS begins. If using integrated security, the SS checks to see
> if the users Windows/network credentials exist in its list of logins,
> allowing the user in if it does. If not, then a user id and login must be
> supplied. (This is a high-level view of what takes place - don't hold me too
> strongly to this story. It's been a while since I studied it and it's hazy.
> But this should be close)
>
> >
> >> For example, Query Tools (George
> >>> Polouse) VB 6.0, VBScript, and MS Excel. The only application that
> >>> will not access the server is ASP and ASP runs fine if I try to
> >>> access a local Access DB (I do not have SQL running on the XP
> >>> computer.)
> >>
> >> You must have given the local IUSR account file-level access to the
> >> folder containing your database, right? It's all permissions.
> >
> > Actually, I have not granted IUSR any permissions anywhere. I'm
> > confused about this as well, because there is no security tab on the
> > properties page for any folder on my PC. (I'm used to WIN 2K and not
> > as familiar with XP yet as I'd like to be.)
>
> So you must only have one user at a time using it on your PC. Without
> granting file-level permissions to the folder containing the mdb, multi-user
> activity is not possible.
>
> If you change your XP security setting to not use Simple Security (i forget
> how to do it: you'll have to google for it - i know there's an article about
> it at microsoft.com), then you'll get your Security tab back.
>
> Bob Barrows
> --
> Microsoft MVP - ASP/ASP.NET
> Please reply to the newsgroup. This email account is my spam trap so I
> don't check it very often. If you must reply off-line, then remove the
> "NO SPAM"
>
>
>

Relevant Pages

  • Re: Cannot open database requested in login
    ... Assuming your goal is to use windows integrated ... security then leave out the username ... ASP.NET service) as a login to SQL Server and with access to the ... >> you should see security tab, change authentication to "SQL ...
    (microsoft.public.sqlserver.security)
  • ASP.NET "Custom" Security
    ... SQL Server, DB2, MySQL, Oracle, ... Windows server at the other end. ... to be authenticated by the stored procedure against the ... Is this a reasonable security model? ...
    (microsoft.public.dotnet.framework.aspnet.security)
  • Re: Is there any way to prevent hacker trying to guess sa password?
    ... the Space Shuttle has some very strong windows -- get my point. ... doubt THE single most significant security flaw -- this is the green light ... spoofing was known about when the protocol was introduced and Microsoft did ... > need to use some other mechanism to connect to SQL Server. ...
    (microsoft.public.sqlserver.security)
  • Re: MDF file level security from copying
    ... Sounds to me as if your first issue is the physical security of the machines ... hosting SQL Server. ... Neither Windows 98 nor Windows ME were meant as enterprise level operating ... >>BTW, if you are concerned about the database schema, as ...
    (microsoft.public.sqlserver.security)
  • Re: SQL or Access DB
    ... As far as encryption goes though... ... with Sql Server you can use SQL DMO and encrypt your stored procedures ... installation - Security was absolutely critical and in most instances, ... > then we create a nice gui around this database and sell it to automotive ...
    (microsoft.public.dotnet.languages.vb)