StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>The URL provided by Velvet is down. I found a cached version on archive.org:</p> <p>" 401.1 Error When Accessing SharePoint From Server</p> <p>I ran into this issue several times in the past in setting up SharePoint environments (for both internal development use and customers) so I figured it was time to write a blog post about it. If you are running SharePoint Server 2007 or WSS 3.0 on Windows Server 2003 SP1 or later you will run into authentication issues if you are trying to access a SharePoint site using host headers from the server itself (i.e. host file has portal.mydomain.com pointed to 127.0.0.1). This issue manifests itself as the result of a loop back security check that Microsoft built in to Windows Server 2003 SP1 and later. The purpose of the loopback check is to eliminate denial of service attacks however it causes issues with access SharePoint sites locally from the server. In a typical production environment this is typically not a problem since you rarely access SharePoint sites (besides central admin) from a front end web server itself. However I do have physical and virtual development environments where all activities take place from the server, so this can cause some heartburn unless you have worked through the issue before. You can read the detailed KB article at <a href="http://support.microsoft.com/kb/926642" rel="nofollow">KB926642</a> & <a href="http://support.microsoft.com/kb/896861" rel="nofollow">KB896861</a>. Here is a rundown of how to fix the problem. I typically disable the loopback check however this is not recommended for production server environments.</p> <p>Method 1: Disable the authentication loopback check Re-enable the behavior that exists in Windows Server 2003 by setting the DisableLoopbackCheck registry entry in the <code>HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa</code> registry subkey to 1. To set the <code>DisableLoopbackCheck</code> registry entry to 1, follow these steps on the client computer:</p> <ol> <li>Click Start, click Run, type regedit, and then click OK. </li> <li>Locate and then click the following registry subkey: <code>HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa</code></li> <li>Right-click Lsa, point to New, and then click DWORD Value. </li> <li>Type <code>DisableLoopbackCheck</code>, and then press ENTER. </li> <li>Right-click <code>DisableLoopbackCheck</code>, and then click Modify.</li> <li>In the Value data box, type 1, and then click OK. </li> <li>Exit Registry Editor.</li> <li>Restart the computer. Note You must restart the server for this change to take effect. By default, loopback check functionality is turned on in Windows Server 2003 SP1, and the DisableLoopbackCheck registry entry is set to 0 (zero). The security is reduced when you disable the authentication loopback check, and you open the Windows Server 2003 server for man-in-the-middle (MITM) attacks on NTLM.</li> </ol> <p>Method 2: Create the Local Security Authority host names that can be referenced in an NTLM authentication request To do this, follow these steps for all the nodes on the client computer:</p> <ol> <li>Click Start, click Run, type regedit, and then click OK. </li> <li>Locate and then click the following registry subkey: <code>HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\MSV1_0</code></li> <li>Right-click MSV1_0, point to New, and then click Multi-String Value. </li> <li>In the Name column, type <code>BackConnectionHostNames</code>, and then press ENTER. </li> <li>Right-click <code>BackConnectionHostNames</code>, and then click Modify. </li> <li>In the Value data box, type the CNAME or the DNS alias, that is used for the local shares on the computer, and then click OK.</li> </ol> <p>Note Type each host name on a separate line.</p> <p>Note If the <code>BackConnectionHostNames</code> registry entry exists as a REG_DWORD type, you have to delete the <code>BackConnectionHostNames</code> registry entry. 7. Exit Registry Editor, and then restart the computer.<br> "</p> <p>From: <a href="http://blogs.bluethreadinc.com/thellebuyck/archive/2008/10/30/401.1-error-when-accessing-sharepoint-from-server.aspx" rel="nofollow">http://blogs.bluethreadinc.com/thellebuyck/archive/2008/10/30/401.1-error-when-accessing-sharepoint-from-server.aspx</a> on June 05 2009</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

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