The WEBEXT..log contains the request as passed by the client. If you include "Rule#1" and "Rule#2" in the logging configuration, you'll get that information. Unfortunately, there's no easy mechanism to see exactly which destination in which destination set caused the rule to fire. Jim Harrison MCP(NT4, W2K), A+, Network+, PCG http://www.microsoft.com/isaserver http://isaserver.org/Jim_Harrison http://isatools.org Read the help, books and articles! ----- Original Message ----- From: "Greg Mulholland" <greg_mul@xxxxxxxxxxxxxxx> To: "[ISAserver.org Discussion List]" <isalist@xxxxxxxxxxxxx> Sent: Tuesday, March 11, 2003 02:52 Subject: [isalist] isa ad blocking http://www.ISAserver.org Steve may be best to answer this, but others feel free. Is there anyway of tracking what websites are being blocked by the destination sets created by the isa_ads file. Thanks Greg Mulholland Technical Services Manager Harvey Norman - Knox Melbourne, Australia greg_mul@xxxxxxxxxxxxxxx +613 9881-3730 ------------------------------------------------------ List Archives: http://www.webelists.com/cgi/lyris.pl?enter=isalist ISA Server Newsletter: http://www.isaserver.org/pages/newsletter.asp ISA Server FAQ: http://www.isaserver.org/pages/larticle.asp?type=FAQ ------------------------------------------------------ Exchange Server Resource Site: http://www.msexchange.org/ Windows Security Resource Site: http://www.windowsecurity.com/ Windows 2000/NT Fax Solutions: http://www.ntfaxfaq.com ------------------------------------------------------ You are currently subscribed to this ISAserver.org Discussion List as: jim@xxxxxxxxxxxx To unsubscribe send a blank email to $subst('Email.Unsub')