Tracing IIS for CRL caching

[Yves]

Hi,
We developed a web site in ASP.NET using the Framework 2.0
The web site is hosted on a Windows Server 2003 SP2 (Enterprise edition) and
using IIS 6.0
The web site is configured to:
- Require SSL
- Require 128 bits encryption
- Require client certificates

The problem we have is with the CRL (Client Revocation List) and the
Distribution points.
Sometime, when the user accesses the site, he/she get’s an error (403.13)
because the CRL is expired. We suspect an intermittent problem with the
network

What I am trying to do and can’t seem to find is how to trace what IIS is
doing when it receives the request from the client to know:
- When it is using the CRL in the cache
- When it is using one of the url in the distribution point to fetch a new
CRL (current CRL is expired?)

Does IIS trace at that level of detail? What tool is best to view the trace
from IIS?

And my last question would be is it possible to remove the CRL from the
cache? If so, is it only by deleting the files in C:\Documents and
Settings\username\Application Data\Microsoft\CryptnetUrlCache?

Thanks in advance for your help!

--
Best regards
Yves

[David Wang]

Look up ETW Tracing which has been available since WS03SP1. If it
doesn't have it, then the info you want does not exist without Windows
Source Code access.

//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//

[Yves Gagnon]

I spent quite some time with “ETW tracing” and logman trying to get the
information I need but I was not successful. Here is what I did:

I created a provider file (IIS_config.txt) listing the following IIS
providers:

"IIS: WWW Global" 0 5
"IIS: IISAdmin Global" 0 5
"IIS: WWW Server" 0xFFFFFFFE 5
"IIS: WWW Isapi Extension" 0 5
"IIS: SSL Filter" 0 5
"IIS: Request Monitor" 0 5

Started logman:
logman start iis_log -pf IIS_config.txt –ets

Accessed the web site from a client pc

Stopped logman
logman stop iis_log –ets

Are there any other IIS providers out there? I would appreciate any
suggestions.

Thank you!

"David Wang" <w3....@gmail.com> wrote in message
news:5932bf4f-c891-400b...@v53g2000hsa.googlegroups.com...

[David Wang]

Unfortunately, if it is not in ETW Tracing, then you are out of luck.
Only by modifying IIS Source Code to add new traces will you get any
additional trace providers.

//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//

On Oct 1, 7:38 am, "Yves Gagnon" <gagy...@community.nospam> wrote:
> I spent quite some time with “ETW tracing” and logman trying to get the
> information I need but I was not successful. Here is what I did:
>
> I created a provider file (IIS_config.txt) listing the following IIS
> providers:
>
> "IIS: WWW Global" 0 5
> "IIS: IISAdmin Global" 0 5
> "IIS: WWW Server" 0xFFFFFFFE 5
> "IIS: WWW Isapi Extension" 0 5
> "IIS: SSL Filter" 0 5
> "IIS: Request Monitor" 0 5
>
> Started logman:
> logman start iis_log -pf IIS_config.txt –ets
>
> Accessed the web site from a client pc
>
> Stopped logman
> logman stop iis_log –ets
>
> Are there any other IIS providers out there? I would appreciate any
> suggestions.
>
> Thank you!
>

> "David Wang" <w3.4...@gmail.com> wrote in message

> //- Hide quoted text -
>
> - Show quoted text -