I'm using SharePoint 2010 and have two WFE servers hosting our SP sites. There is an IntraNet portal site with a separate MySite and Search Center. Then there is the Internet portal site. These all have FQDN DNS entries with separate AAMs which all point to the virtual IP address of the NLB site. The first, port 80 (IntraNet site) loads fine but all the other sites come up as "Unable to load page"! Do I need a separate vIP and NLB site for each application? (That doesn't sound right?!?) Any help would be appreciated. Thanks, Matt.Matthew Barrett Concept Interactive Inc.

When you created the original Web Applicaitons did you use Hostnames? If not then you can't share the same IP address and port for all the sites because IIS won't know which page to load.Paul Stork SharePoint Server MVP

Hi Matthew, In SharePoint 2007, we have load balanced URL, however, in SharePoint 2010, the "Public URL" in the web application creation wizard is the load balanced URL. How did you configure the Public URL when you create the web application? When a web application is created in SharePoint 2010, you can specify the Public URL for the web app. To do network load balancing(NLB), you usually create the web app with a host header that is mapped to the NLB virtual IP that all the servers in the NLB cluster share. Make sure that there is a corresponding record for it in DNS. When the web application is created, the Public URL is what appears as the default zone of the web app. Seriously. The other zones can be used for several other good reasons, but the default zone is actually propagated from the load balanced URL field. By default, a web application will use the server's machine name and port number as the address for a web application. That isn't load balancing, because the address maps to only one machine. If you are going to do NLB, use a host header for NLB as the Public URL for the web app. When it is created, the web app will propagate to the other SharePoint servers in the farm (be sure to IISRESET /noforce on the servers). For more information about Setting up NLB for your WFE’s in SharePoint, please refer to the following articles: http://fabiangwilliams.wordpress.com/2009/04/28/setting-up-nlb-for-your-wfes-in-sharepoint/ http://social.technet.microsoft.com/Forums/en-NZ/sharepointadmin/thread/e4bcd844-6d0c-4ae1-b683-87694468583a http://blogs.msdn.com/b/joelo/archive/2007/01/05/nlb-network-load-balancing-and-sharepoint-troubleshooting-and-configuration-tips.aspx Thanks, Rock Wang TechNet Subscriber Support in forum If you have any feedback on our support, please contact tngfb@microsoft.comRegards, Rock Wang Microsoft Online Community Support

Yes. When I create a web app I use the default server and port (i.e. http://spapp01:80) and then assign an Alternate Address Map to it (i.e. portal.domain.com). The AAM is given the zone, in this case, Intranet and the original app server is the default zone. The spapp01 server has a different IP address then the WFE servers and the vIP but, the AAM is given the vIP address in DNS. Matthew Barrett Concept Interactive Inc.

Yes, you're right; the web app is given the server name with port number when it is created. To give it a "Public" URL I use Alternate Address Mapping (AAM) to give it a FQDN that is then entered into DNS with the NLB address. There is a separate FQDN for each app (Portal, Mysite, Search) since these are separate apps and sites. Again, the first app works (Portal) but when the other sites are called from this app I get Page cannot be loaded. I am using a standard SP2010 farm: 2x WFE with NLB, 1 App, 1 Index, 1 SQL. Matthew Barrett Concept Interactive Inc.