I wonder if someone can help me understand what I am missing here.
I am trying to create a host header based site collection in Sharepoint Foundation 2010 using powershell. The creation process appears to complete ok but after the site collection has been created it is inaccessible. What I mean by this is that pointing a browser at the new site collection gets a prompt for login but when I try to login using the credentials for the site administrator those credentials are never recognised. This is my environment.
The server on which SPF is installed has a computer name of DELL-M4300. We have a Active Directory/dns server configured that correctly points to DELL-M4300 and dell-m4300.mydomain.com. If I ping either of these addresses, they resolve fine.
I have a web application configured using Sharepoint Central Administration that is on port 80. This application is configured to use windows authentication using NTLM.
I can create a root site collection through Central Administration and asisgn myself as a site administrator using my account mydomain\nick
Once created, this site collection is accessible at address http://DELL-M4300
. I can login to this site collection using my account mydomain\nick.
So, now I want to create a host header based site collection to be available at http://www.dell-m4300.mydomain.com
. I have created entries for this address in dns and confirmed that I can ping the entry (www.dell-m4300.mydomain.com
Using powershell, I am trying to create a site collection based on the team site template. To do this I am using the commands:
-OwnerAlias mydomain\nick -HostHeaderWebApplication http://DELL-M4300
This process runs ok in powershell and comes back indicating success. Also, if I now go to Central Administration, I can see the new site collection www.dell-m4300.mydomain.com
listed with my user account as an administrator.
However, if I then browse to http://www.dell-m4300.mydomain.com
, I immediately get a login prompt. I enter my user account details correctly but the login prompt immediately pops up again. In other words, it is impossible to login. I have tried this entire process using other user accounts, adding secondary administrators, etc but none of the user accounts can login.
One final note. If I create a new path based site collection in the same application using Central Administration with myself as site administrator, everything works just fine. Once created, I can login to the path based web site with no problem.
Any advice would be very appreciated.