Mapping a site collection through an extended web application

I have a SharePoint 2010 implementation with two web applications.  One is the "root" web application http://<URL>:80/ and the second is the Central administration web app.  The root web application has two site collections in it under ../sites/<site collection>

I have extended the "root" web to a new site for the extranet zone.  I can get to the root site through the newly created URL but not to the site collections underneath "../sites/".   Any thoughts on what I have missed?

I can provide more detail as I realize that this is somewhat lacking on the finer points.

Thanks
jima92119Asked:
Who is Participating?
 
Minesh ShahSharePoint & all about itCommented:
i m not very sure, but guess you need to enter site colloections into the Alternate Access Mapping
0
 
Justin SmithSr. System EngineerCommented:
Did you manually add the new host header to IIS?
0
 
jima92119Author Commented:
Ach1lles,

I did not supply a new host header as I extended the web application into a new web site.  The process of exteding the web application created an alternate access mapping but I did not supply a host header.  Some additional detail is that I setup the extension for the extranet zone and configured it for SSL on port 443.

I am going to inculude a screen shot of the settings for when I did the extension in the off chance it may spark a thought.  Please let me know what other information I can provide that might help.  I will try creating new aam entries as MineSharePoint has suggested.  If that resolves the issue then I will let you know.

   A screenshot of settings from the web app extension.
0
Cloud Class® Course: Ruby Fundamentals

This course will introduce you to Ruby, as well as teach you about classes, methods, variables, data structures, loops, enumerable methods, and finishing touches.

 
Justin SmithSr. System EngineerCommented:
THis is the only site in IIS on port 443, correct?
0
 
jima92119Author Commented:
Correct.  There are no other sites on 443.
0
 
jima92119Author Commented:
The answer turned out to be a combination of alternate access mapping entries AND how the request was being made via the fully qualfied domain name within our intranet.
Some requests to the URL were being passed on with the fqdn and there was no AAM entry for the FQDN as an internal URL and the public URL that was being accessed.
By adding the AAM between the two the problem was resolved.
0
 
jima92119Author Commented:
My final comments added additional information and the final resolution to the problem.  While it is generally not necessary to add aam entires for the web application beyond what SharePoint creates when the application is extended, in this case there were two ways the web application was being addressed and the AAM entries had to account for both.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.