BigIP fronting IIS 6.0 w ASP.NET

Thanks Simon and Deb for your thoughts. I have seen the MS article which we are using to help justify the default configuration change, but as that relates to a direct Client-Server route it doesn't take into account the Big-IP middle-man how I read it. The limit by the AppDomain does alleviate some of the issue as you note, but since some of our applications are implemented as virtual directories of the root virtual application I believe they share the same appdomain [could be wrong].

 

 

I will raise the configuration question to our team about the best practices for a web server profile. Preserving the client IP will be helpful in a couple places as it not only does not squeeze the connection pool in ASP.NET due to the SNAP single IP, but it also doesn't require a customized ISAPI filter to understand the X-Forward-For which our Web team has been wary to integrate.

 

 

Deb is there a whitepaper on general web server load balancing that I could point our config team toward? To the point of a related IIS/ASP.NET Best practices guide, if the hypothesis is true and someone using SNAT for their IIS servers could be significantly impacting performance as the maxconnection won't scale with clients as it is designed since IIS only "sees" one client/virtual application. We are still working on proof of this hypothesis, but if I do prove it out I will post back and maybe an addendum to the generic web server configuration best practices.