I have two servers, both with Windows Network Load Balancing installed and running on them.
I have an IP that all my domain points to, and that IP is then bound to both servers. NLB then does the clever stuff and figures out which server should handle the respective request.
Here's my problem:
Say I'm on server 1, browsing the site as usual, it's all working fine. I then take server 1 offline in the NLB window, so that server 2 is the only server running, and then click another link in the page. This is when server 2 seems to take about 2 minutes to respond.
I've checked my application trace and the page itself is taking less than a second to load. At first I thought it was taking time to initialize application pools in IIS etc, but we tested that by having someone constantly browse server 2 explicitly, and then I did the same test as before (Start on server 1, take that down and continue on server 2).
Also, i had a constant ping going on the I.P that manages the load balancing, and when I took one server down, I noticed pretty much no downtime in the return ping. So this makes me think it's something to do with the server loading, rather than NLB figuring out that the server is down.
Has anyone had this before? Am I missing anything blatently obvious?
Here's the setup:
- Windows Server 2008 R2.
- IIS 7.0 - each site is a .NET application running framework v.3.0.