Re: Cached Logon

From: Ken Schaefer (kenREMOVE_at_THISadopenstatic.com)
Date: 12/19/04 

Date: Mon, 20 Dec 2004 10:42:41 +1100

Hi,

Your browser is caching the credentials, and resending them for each
subsequent page request to that server (until the browser is closed). IE
will continue sending those credentials as long as they work. As far as IE
is concerned, the credentials work, even for the first page, as the page can
be accessed (it's just the ASP page -> SQL Server that doesn't work, but IE
doesn't know anything about logging into databases)

In terms of the login failure - can we see the exact error message that you
are seeing please?

Also, are you using a common connection string across all three pages (eg is
the connection string stored in an include file, or in the registry?) Or
have you hard coded the connection string into all three pages? If the
latter, then I would suggest moving the connection string to a central
include file (or application variable), and using that on all three pages to
ensure that you aren't getting a dud connection string on one of the pages.

Cheers
Ken

"Roland Hall" <nobody@nowhere> wrote in message
news:uN$9owb5EHA.3784@TK2MSFTNGP10.phx.gbl...
> If IIS cached a logon just for one particular page, but not for other
> pages
> performing the same logon, is that normal? I know it sounds bizarre but I
> have an ASP page that makes an ADO connection to MS SQL Server.
> Authentication on SQL is set to SQL and Microsoft. Authentication in IIS
> is
> set to Basic and Integrated. Anonymous is disabled.
>
> I know this is not a coding NG but this is not necessarily a coding
> question.
>
> StraightASP.asp prompted me for credentials and I put in credentials for
> the
> domain administrator. It makes an ADO connection to SQL server using sa.
> (System Administrator). There is no sa account in Active Directory and
> the
> domain administrator does not have a SQL logon.
>
> I got access to the page, as I should but then the logon to SQL failed. I
> verified the password was correct and tried again. Same result. I then
> chose to try another file, which resides in the same folder:
> StraightXML1.asp It uses the exact same ADO code for logon to SQL, and it
> works. I have one last file, StraightXML2.asp, same code, works fine.
>
> The differences between the files is:
>
> 1. ASP only.
> 2. Recordset written to XML using CSS.
> 3. Recordset written to XML using XLS.
>
> I renamed the first file and it worked.
> I rename it back, it fails.
> I shutdown and restarted SQL. Same issue.
> I shutdown and restarted IIS. Same issue.
> I reboot the IIS/SQL server. Problem disappears. I now do not get
> prompted
> for any credentials and all files work. No changes to code.
>
> Other info:
>
> IIS/SQL server is W2K Adv. Server (completely patched).
> Remote: WinXP Pro (completely patched)
> domain1\administrator - domain2\administrator both have the same password.
>
> I was only prompted for credentials by the one file. I'm wondering where
> the caching issue resides and/or if the system had a problem with SQL
> being
> set for SQL and Windows authentication and IIS set for Basic and
> Integrated
> only.
>
> This question crosses several boundaries, ASP, SQL, IIS, W2K. I've
> included
> several NGs to see if anyone can provide an opinion on the cause of this
> phenomena. If you can only provide a partial answer which is relevant to
> the NG you read this in, that's fine.
>
> TIA...
>
>

Relevant Pages

  • Re: Cached Logon
    ... Your browser is caching the credentials, ... be accessed (it's just the ASP page -> SQL Server that doesn't work, ... are you using a common connection string across all three pages (eg is ...
    (microsoft.public.windows.server.general)
  • Re: Cached Logon
    ... Your browser is caching the credentials, ... be accessed (it's just the ASP page -> SQL Server that doesn't work, ... are you using a common connection string across all three pages (eg is ...
    (microsoft.public.sqlserver.connect)
  • Re: Cached Logon
    ... Your browser is caching the credentials, ... be accessed (it's just the ASP page -> SQL Server that doesn't work, ... are you using a common connection string across all three pages (eg is ...
    (microsoft.public.sqlserver.server)
  • Re: Cached Logon
    ... Your browser is caching the credentials, ... be accessed (it's just the ASP page -> SQL Server that doesn't work, ... are you using a common connection string across all three pages (eg is ...
    (microsoft.public.win2000.networking)
  • Re: Cached Logon
    ... Your browser is caching the credentials, ... be accessed (it's just the ASP page -> SQL Server that doesn't work, ... are you using a common connection string across all three pages (eg is ...
    (microsoft.public.sqlserver.security)