Raj, that is good to know. Thanks. It was not much of a deliberate decision to combine them. I have ISA Enterprise edition and I'm used to managing ISA boxes in a cluster rather than individually. I think there are also some cache and performance advantages using an ISA Array. Food for thought. Beginning to think I should give different name for Array and different for Cluster and create DNS host records for both. That way there is an option to choose between Array and Cluster for the Proxy clients. SNAT clients would always point to cluster address. Regards, John -----Original Message----- From: Periyasamy, Raj [mailto:Raj.Periyasamy@xxxxxxxxxxxx] Sent: Wednesday, December 11, 2002 11:18 AM To: [ISAserver.org Discussion List] Subject: [isalist] RE: NLB on Internal Interface http://www.ISAserver.org We are using NLB with 2 ISA servers. But no Array. The NLB cluster DNS name is the proxy server name used by clients. We use WPAD with DHCP for proxy auto detection. It works very good. Why do you want to combine array and NLB ? Regards, Raj -----Original Message----- From: John C. Shepard [mailto:jshepard@xxxxxxxxxxx] Sent: Wednesday, December 11, 2002 1:24 PM To: [ISAserver.org Discussion List] Subject: [isalist] NLB on Internal Interface http://www.ISAserver.org Does anybody know how to overlap the ISA Cluster on top of NLB on the Internal Interface? Can the NLB Cluster DNS Name be the same as the ISA Cluster name? I'm thinking this could make things easier but I don't know how it dovetails with WPAD, CARP and client config. SNAT seems simple and straightforward. I'll just use the NLB cluster address as gateway on the clients. Having a hard time deciding if I should use different names for the ISA Cluster and the NLB DNS name. The desired result is to load balance the Internal Interface.