This was exactly why I wnated to understand more about your environment. If you were to place ARR in front of your 2 content servers, you have a couple of options: - You would just use one IP on ARR and bind 7 domain names to the same IP. Based on the host header, you can route them to different server...

ARR deployment will always be in front of your content servers, regardless of whether you want to load balance across one or multiple sites. It is a proxy based solution. (I think you might be thinking of NLB - another Windows technology. NLB can be used to load balance sites as well and NLB does not...

Tony I would like to understand your environment a bit better before making my recommendation. - You've mentioned that you have 7 sites, each with their own IP. So today, in your load balancer, do you have 7 VIPs, each with their own domain name binding? - The 2 WS08 boxes that you have, are you...

We install Microsoft Application Request Routing on a server and we are using it as a reverse proxy server. All the url rewrite rules work, if we update the rule set with new rules everything still works but if we introduce or modify any rule that contains any IP condition and use REMOTE_ADDR as a variable...

Hi Joshua ARR and NLB can be complementary, but they are not the same technology. Not sure if you had a chance to walk through some of the documents, but for your use case, it seems like the following may be most useful: http://learn.iis.net/page.aspx/486/http-load-balancing-using-application-request...