We have one site on IIS build in ASP.NET with DNN. Currently we try to configure network load balancing for two servers. The service hosting provider told us this would be enough, but we seem to have hit a brick wall:
- network load balancing only forwards requests from his public ip, it doesn't check the availability of the servers
- if a server goes down, 50% of the requests will see a "server not a available" until we manually remove the server from the load balancing configuration
- I don't see a way to configure this with two servers without this problem
With three-way load balancing, aka web farm, a single system checks which servers are available. If a server goes down, it will forward the request to the other server.
Is the above a correct assumption of the limitation of network load balancing, leading to classical web farm as only solution, or is there something the hosting provider can configure to prevent this behavior and have us stick with only two systems?