Hi Jim, You sure about the proxy chain loop error? I don't recall seeing those errors in my hundreds of painful hours trying to tame the Enterprise Edition beast. But now that I think about it, I don't think I configured the client side CARP routing to use a VIP name, since that would break CARP. Never mind :) 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: Friday, April 01, 2005 12:31 PM To: [ISAserver.org Discussion List] Subject: [isalist] RE: ISA 2004 EE http://www.ISAserver.org Much reading to be done, grasshopper: www.isaserver.org www.microsoft.com/isaserver NLB and CARP can conflict because of the potential for a connection loop: - user needs to make web request - CARP directs client to specific server name (resolves to VIP) - user requests content from VIP - ISA serving request doesn't have the content; makes CARP request to other array member (resolves to VIP) - ISA making request gets own request; throws "proxy chain loop" error - user gets pissed and throws PC out the window - user gets fired and arrested; problem solved ------------------------------------------------------- Jim Harrison MCP(NT4, W2K), A+, Network+, PCG http://isaserver.org/Jim_Harrison/ http://isatools.org Read the help / books / articles! ------------------------------------------------------- -----Original Message----- From: klocke [mailto:kevin.locke@xxxxxxxxxxxx] Sent: Friday, April 01, 2005 10:25 To: [ISAserver.org Discussion List] Subject: [isalist] ISA 2004 EE http://www.ISAserver.org Can somebody please a explain to what would be best to a very new ISA admin. I have been tasked with replacing our old Proxy with ISA 2004 EE. The requirment are that the it needs to be fault tolorate and it for Web proxy only. My thoughts were to create ISA in a array with CARP for web caching and also us NLB on internal NIC's for the fault tolorate. But I have seen a few article recommending not to use NLB with CARP? can you please explain. Thanks Kevin ------------------------------------------------------ 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