Welcome to Atlanta .NET Regular Guys Sign in | Join | Help

Be sure to use distinct names in your SharePoint Web Applications

If you are creating an externally accessible portal or extranet with SharePoint which uses Forms based authentication, business requirements such as Search and ECM Publishing might require you to create an intranet portal which uses NTLM or Kerberos authentication.  To do this, you'd first create a Web Application in SharePoint, then you'd go back and extend that web application to add the second zone.  However tempting it might be to give these portals the same description, don't.  The misnamed Description field is actually the name that shows up in the IIS Manager application.  If you give two Web Apps the same name, they won't get distinct entries in the IIS Admin web sites section.  This has the effect of IIS not being able to find your site and sending incoming requests for the duplicate named site to the default web site (which normally shows a "Under Construction" message)

SharePoint Web Application Description field    IISAdmin Sites list

Published 25-09-2007 10:43 by Matt Ranlett
Filed Under: , ,

Comment Notification

If you would like to receive an email when updates are made to this post, please register here

Subscribe to this post's comments using RSS



Ray Ranson said:

Good post. I encountered the same and although the FQDN ran for a while before we got 404's internally, people had already started to publish quite a bit of content. I resolved through editing with the IIS Metabase tool and less egg on my face.
October 17, 2007 8:36 PM

What do you think?


About Matt Ranlett

One of the two original Atlanta .NET Regular Guys, Matt fills his free time by helping to run several Atlanta area user groups, the Atlanta Code Camps, and works as one of the two INETA co-Vice Presidents of Technology
Powered by Community Server, by Telligent Systems