Blocked requests (e.g. for disallowed webservice extensions) are logged into
the main IIS logfile.

Cheers
Ken

--
Blog: www.adopenstatic.com/cs/blogs/ken/
Web: www.adopenstatic.com

[quoted text, click to view]
: We know that the std IIS logs contain the return codes of 401, 402, etc.,
: but we are interested in the URLScan logs that were present in IIS 5 and
: prior with the URLScan tool was setup.
:
: I am told not to run URLScan or IIS Lockdown on an IIS 6 box because that
: functionality is baked right into IIS 6. But where do I read the detail
: results of a blocked request like I used to get with URLScan?
:
: Many thanks,
:
: Keith
:
:

We know that the std IIS logs contain the return codes of 401, 402, etc.,
but we are interested in the URLScan logs that were present in IIS 5 and
prior with the URLScan tool was setup.

I am told not to run URLScan or IIS Lockdown on an IIS 6 box because that
functionality is baked right into IIS 6. But where do I read the detail
results of a blocked request like I used to get with URLScan?

Many thanks,

Keith

You still can deploy urlscan if it fits your requirement, refer
http://www.microsoft.com/technet/security/tools/urlscan.mspx#ECAA


--
Regards,
Bernard Cheah
http://www.tryiis.com/
http://support.microsoft.com/
http://www.msmvps.com/bernard/


[quoted text, click to view]