You could parse the logs for the name of the rule that denies the destination set and then parse that for 407 and 12209 (proxy authentication required codes). Setup a job to do it if you wish to automate it. That of course assumes that you're logging those fields. Go get the GNU Posix tools for NT, grep is a wonderful thing. -Shawn ----- Shawn R. Quillman Robert Bosch Corporation RBNA/CIT1.1 38000 Hills Tech Drive Farmington Hills, MI 48331 (248) 553-1164 (P) (248) 848-2855 (F) shawn.quillman@xxxxxxxxxxxx -----Original Message----- From: Greg Mulholland [mailto:greg_mul@xxxxxxxxxxxxxxx] Sent: Tuesday, March 11, 2003 5:53 AM To: [ISAserver.org Discussion List] 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 <mailto: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: shawn.quillman@xxxxxxxxxxxx To unsubscribe send a blank email to $subst('Email.Unsub')