Take the 2-minute tour ×
SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. It's 100% free, no registration required.

In our farm setup we have multiple WFE servers, these are server 21 and server 31.

When i create a new web application to run on port 84, and then i create a new site collection, i can access this site collection using both of these urls:

This is all working fine, however, when i create a new site collection at a different managed path using wildcard inclusion, f.e. the standard sites path, things start to go wrong. To be clear, i create a new site collection named Site1 at the sites managed path at the web appliaction on port 84. I can access this site using

but when i try to access the site from http://31:84/sites/Site1 i get an error 404, I am totally stumped on what could possibly cause this weird behaviour. Also i cannot seem to find anyone on the internet that is facing the same issue, so any help is appreciated.

edit The server that will have the working site collection access, depends on which one i set to be the default server when creating the web application, but after that it is normal for SharePoint to make it possible to access this site from the other WFE's right, or am I seeing it all wrong?

share|improve this question
1  
Why are you using unique URLs relative to the server and not a shared, common DNS entry? Also, why the non-standard port? Are these seen as unique web applications, or is the web application setup in central administration to support both within the Alternate Access Mappings? –  Mike Oryszak Nov 1 '11 at 18:25

1 Answer 1

up vote 1 down vote accepted

For future reference, the error i described in my post is actually normal behaviour. I thought that when i created a web application with a site collection, it would automatically be served via all the WFE servers. This is true, but only on the root site collection, to access the other site collections on all WFE servers, I had to add an Alternate Acces Mapping.

My confusion about this originated from our Development envirionment where this behaviour was normal, i later found out however that the extra AAM had been added in that envirionment.

Thanks for the comment Mika Oryszak

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.