Windows Network Services Architecture series of courses (vi) using NLB clustering to achieve Web server reliability

Experimental background:

There is such a scenario in a large network environment, the company's internal FTP server failed or offline, and can not quickly recover, users can not timely access to the company's internal resources; the company's internal Web server access is too large, resulting in the speed of the site is more and more slow, not very good for customer service, there are Isa, VPN servers (these servers have a common feature: there is only a read-only relationship between the server and the client and cannot be written to) ...

So how to ensure the reliability of these servers, the Network Load Balancing cluster (NLB) gives a solution that enhances the reliability and scalability of services such as Web, FTP, ISA, VPN, and so on. It is done by running a service on two or more (up to 32) computers, the content of its services must be the same, consisting of a single Network Load Balancing cluster that provides services out of a virtual IP address that automatically reassign the load between computers that continue to run when a server in the cluster fails or goes offline. The client accessing the server does not feel that a server has failed.

Experimental purposes:

1. Understand the use of NLB clusters

2. Deploying NLB clusters on Windows Server 2003

3. Verify the reliability of your Web server's NLB cluster

Experiment Network topology: