Ha! You musta be some sorrta mind reader or somethin! Sorry I missed Montreal. You can blame my wicked taskmasters at MSS. Tom www.isaserver.org/shinder Tom and Deb Shinder's Configuring ISA Server 2004 http://tinyurl.com/3xqb7 MVP -- ISA Firewalls -----Original Message----- From: Jim Harrison [mailto:Jim@xxxxxxxxxxxx] Sent: Wednesday, June 08, 2005 10:27 AM To: [ISAserver.org Discussion List] Subject: [isalist] RE: Using a Unihomed ISA Firewall at Branch Offices to Reduce WAN Bandwidth Usage http://www.ISAserver.org I know who it was... Neener-neener-boo-boo.. :-) BTW, Montreal was a interesting; you shoulda gone... ------------------------------------------------------- Jim Harrison MCP(NT4, W2K), A+, Network+, PCG http://isaserver.org/Jim_Harrison/ http://isatools.org Read the help / books / articles! ------------------------------------------------------- -----Original Message----- From: Thomas W Shinder [mailto:tshinder@xxxxxxxxxxx] Sent: Tuesday, June 07, 2005 11:45 To: [ISAserver.org Discussion List] Subject: [isalist] Using a Unihomed ISA Firewall at Branch Offices to Reduce WAN Bandwidth Usage http://www.ISAserver.org Hey folks, This is the beginning of an article I'm doing that shows a deployment I did recently with a large organization with many branch offices: Using a Unihomed ISA Firewall at Branch Offices to Reduce WAN Bandwidth Usage: http://www.msfirewall.org/isa2004/2004unihomedbo/2004unihomedbo-1.htm This article has the potential to get very very long if I go through not only the principles behind the decisions, but also the step by step configurations. What I'd like to know from anyone who cares is if it would be worthwhile to go through the step by steps, or would someone who ready know how to do the configuration steps be the only one who'd be interested in this kind of deployment, and so step by steps would be redundant? The bulleted list shows the steps. I plan on doing a discussion on the rational and principles for each of the bulletted list sections, but what I'd like to get some opinions on is whether it would be a value to anyone to show the detailed config steps. Thanks! Tom ------------------------------------------------------ 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 ------------------------------------------------------ Other Internet Software Marketing Sites: World of Windows Networking: http://www.windowsnetworking.com Leading Network Software Directory: http://www.serverfiles.com No.1 Exchange Server Resource Site: http://www.msexchange.org Windows Security Resource Site: http://www.windowsecurity.com/ Network Security Library: http://www.secinf.net/ Windows 2000/NT Fax Solutions: http://www.ntfaxfaq.com ------------------------------------------------------ You are currently subscribed to this ISAserver.org Discussion List as: jim@xxxxxxxxxxxx To unsubscribe visit http://www.webelists.com/cgi/lyris.pl?enter=isalist Report abuse to listadmin@xxxxxxxxxxxxx All mail to and from this domain is GFI-scanned. ------------------------------------------------------ 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 ------------------------------------------------------ Other Internet Software Marketing Sites: World of Windows Networking: http://www.windowsnetworking.com Leading Network Software Directory: http://www.serverfiles.com No.1 Exchange Server Resource Site: http://www.msexchange.org Windows Security Resource Site: http://www.windowsecurity.com/ Network Security Library: http://www.secinf.net/ Windows 2000/NT Fax Solutions: http://www.ntfaxfaq.com ------------------------------------------------------ You are currently subscribed to this ISAserver.org Discussion List as: tshinder@xxxxxxxxxxxxxxxxxx To unsubscribe visit http://www.webelists.com/cgi/lyris.pl?enter=isalist Report abuse to listadmin@xxxxxxxxxxxxx