Deployment of Windows 2008 load Balancing Servers

Project Environment:

Both Windows Server 2008 are dual network adapters

IP Address

192.168.19.100 (extranet 1) 99.99.99.99 (intranet 1 dedicated)

192.168.19.101 (extranet 2) 99.99.99.100 (intranet 2 dedicated)

Where 192.168.19.100 is primary DNS 101 is backup DNS

Virtual IP Address 192.168.19.125

Ideas:

First, load Balancing Services (NLB) are installed on the w2k08, and IIS services must be installed, and the deployment of IIS installations in this project is not displayed. Because of the limited concurrency of w2k08 load balancing, we deploy only as backup (we can switch to the server we deploy when the hardware load balancing (Citrix) in our production environment fails). Linux is better, of course, and we don't elaborate on Linux deployments.

Purpose of implementation:

To achieve the load of the network, play a backup role. DNS, IIS already deployed.

Deployment process:

1, first installs the deployment load balanced installs the service, the IIS Load equalization service if the backstage mount SQL may do cluster. (Deployment of two servers is the same so we list only one server deployment) as shown:

2, after the installation, respectively, set up IIS on two clusters, and then we test the binding. As shown in figure:

3, in the beginning of the operation of the input-nlbmgr pop-up, select "New cluster." Then enter the IP address of this computer in the dialog box that pops up. What we need to be aware of is that the IP address we select here is the IP address that the extranet can access. Then select the connection. Detailed diagram: