Greetings all, Have 2 WSS 3.0 FWEs on DMZ and want to expose to the internet. Have the extended the web app for external access. My question is, since each WFE has a different internal IP address, where do I tell my firewall to send inbound packets, NAT basically? Ex. WFE 1: 192.168.10.10 WFE 2: 192.168.10.20 Firewall: Packets from Ext. ip address get natted to which internal WFE? I'm missing something here in how the NLB works on WSS. Don't know if it's Win Network Config or what. Please note, I'm not running ISA Server or anything of that nature. Just need to know how to make both internal servers look like 1 ip address for HW firewall to know where to send the packets. Appreciate any thoughts.

Oleg, Thanks for the quick reply. SW NLB is exactly correct. My stumbling point is that my NIC adapter does not show NLB as a service or protocol etc in the NIC properties. How does one install/configure this? BTW the OS is Win 2k8 R2. Thanks again.

All version of Windows 2003/2008 supports NLB. I guess you have to install NLB in your Network Connection. Oleg

Wow, there is some serious lag between when a post opens and when the posts arte getting posted.... I fee l like we are answering the same questions To install NLB 1. Navigate to Administrative Tools and click Server Manager. 2. Scroll down to the Features section or click the Features node in the left-hand tree view. 3. Click Add Features. 4. In the Add Features Wizard, select Network Load Balancing from the list of available optional components. 5. Click Next, and Install, as applicable to complete the wizard. 6. To configure NLB 7. Navigate to Administrative Tools and click Network Load Balancing Manager, or run nlbmgr from a command prompt. 8. Right-click Network Load Balancing Clusters and click New Cluster. 9. Connect to the host that will be part of the cluster, in this case the Web server. In the Host text box, type the name of the host, and then click Connect. 10. Select the interface you want to use with the cluster, and then click Next. 11. On the Host Parameters page, select a value from the Priority (unique host identifier) drop-down list. 12. In the Dedicated IP Addresses area, click Add to type the IP address that is shared by every host in the cluster. NLB will add this IP address to the TCP/IP stack on the selected interface of all hosts chosen to be part of the cluster. Click Next to continue. 13. On the Cluster IP Addresses page, click Add. 14. In the Add IP Address dialog box, type the IP address and subnet mask, and then click OK. 15. Click Next. 16. On the Cluster Parameters page, in the Cluster operation mode area, click Unicast to specify that a unicast media access control (MAC) address should be used for cluster operations. Click Next to continue. 17. On the Port Rules page, click Edit to modify the default port rules if you need advanced rules. Otherwise, use the default. 18. Click Finish to create the cluster. To add more hosts to the cluster, right-click the new cluster, and then click Add Host to Cluster. References · “Reasons for Using Network Load Balancing” http://technet2.microsoft.com/windowsserver/en/library/7698646d510e47f99b09b31dec12be3a1033.mspx · “VMware Virtual Networking Concepts“ http://www.vmware.com/resources/techresources/997 · “Windows Server 2003 Deployment Kit” http://go.microsoft.com/fwlink/?LinkId=18370 · “Checklist: Enabling and configuring Network Load Balancing” http://go.microsoft.com/fwlink/?LinkId=18371 · “Clustering Services in Windows 2003” http://www.microsoft.com/windowsserver2003/technologies/clustering/default.mspx · “Microsoft Communities Web Site” http://go.microsoft.com/fwlink/?LinkId=18374 · “Microsoft NLB Not Working Properly in Unicast Mode” http://kb.vmware.com/kb/1556 Hope this helps... -IvanIvan Sanders My LinkedIn Profile, My Blog, @iasanders.