Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>Quoting a <a href="http://technet.microsoft.com/en-us/library/cc261814.aspx" rel="nofollow noreferrer">Technet article</a>:</p> <blockquote> <p><strong>About alternate access mappings</strong> Alternate access mappings enable a Web application that receives a request for an internal URL, in one of the five authentication zones, to return pages that contain links to the public URL for the zone. You can associate a Web application with a collection of mappings between internal and public URLs. Internal refers to the URL of a Web request as it is received by Office SharePoint Server 2007. Public refers to the URL of an externally accessible Web site. The public URL is the base URL that Office SharePoint Server 2007 uses in the pages that it returns. If the internal URL has been modified by a reverse proxy device, it can differ from the public URL. </p> </blockquote> <p>There are a few good guides written for this:</p> <ul> <li>Bob Fox has a <a href="http://bobfox.securespsite.com/FoxBlog/Lists/Posts/Post.aspx?ID=16" rel="nofollow noreferrer">How To Screencast</a></li> <li>The SharePoint Team Blog has a <a href="http://blogs.msdn.com/sharepoint/archive/2007/03/06/what-every-sharepoint-administrator-needs-to-know-about-alternate-access-mappings-part-1.aspx" rel="nofollow noreferrer">good guide</a></li> <li>Technet has a relatively <a href="http://technet.microsoft.com/en-us/library/cc261814.aspx" rel="nofollow noreferrer">thorough article</a></li> </ul> <p>In terms of debugging a few things to check:</p> <ul> <li>All the ISA settings are correct</li> <li>The AAM zones are setup correctly in MOSS</li> <li>Try using <a href="http://www.fiddler2.com/" rel="nofollow noreferrer">fiddler</a> on a client machine to see what is happening, in the past i have noticed a mixutre of https &amp; http requests going through which was causing an issue with images etc..</li> </ul>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload