> Second that. Even the content filtering of URLScan is evil. The > only thing I use on the webservers themselves is IPSec policies.
Though I think IPSec policies are fine, I find that URLScan is an invaluable utility on Windows Server 2000 boxes. At this point, I wouldn't run a Windows Server 2000 web server without it installed. That said, URLScan can be a pain to troubleshoot. I've gotten into the habit of checking the URLScan log files whenever I encounter bizarre behavior or non-descript errors. Ben Rogers http://www.c4.net v.508.240.0051 f.508.240.0057 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:193971 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
