Authentication issues with Host Header site collection in SharePoint 2010
I am running into a wired authentication issue when creating host header SharePoint site. I have created a host header SharePoint site and try to browse to the site. I got prompt with the login dialog even though I have already logged in as Site owner. I tried to click the OK button for 3 times then I got access denied error. To solve this issue, you can do the following:
Update: If you try to use NLB to load balance your SharePoint site and create the host header for the virtual host, you will run into the same problem and the fix is the same below.
Update #2: For detailed explanation for the problem actually happened , check this blog here.
Solution: Specify host names (Preferred method if NTLM authentication is desired)
To specify the host names that are mapped to the loopback address and can connect to Web sites on your computer, follow these steps:
Set the DisableStrictNameChecking registry entry to 1. For more information about how to do this, click the following article number to view the article in the Microsoft Knowledge Base:
281308 Connecting to SMB share on a Windows 2000-based computer or a Windows Server 2003-based computer may not work with an alias name
- Click Start, click Run, type regedit, and then click OK.
In Registry Editor, locate and then click the following registry key:
- Right-click MSV1_0, point to New, and then click Multi-String Value.
- Type BackConnectionHostNames, and then press ENTER.
- Right-click BackConnectionHostNames, and then click Modify.
- In the Value data box, type the host name or the host names for the sites that are on the local computer, and then click OK.
- Quit Registry Editor, and then restart the IISAdmin service.
Pop open a PowerShell console and enter the following:
New-ItemProperty HKLM:\System\CurrentControlSet\Control\Lsa -Name "DisableLoopbackCheck" -Value "1" -PropertyType dword
Make sure to reboot your server afterwards. Then, try your SharePoint site again and you should be good to go!
You can find the detailed MSDN article here.