Skip to main content

SharePoint disable loopback check (DisableLoopbackCheck dword in registry)

SharePoint disable loopback check (DisableLoopbackCheck dword in registry)


I have found this very handy.. recently, I was working on a server and we were trying to access the local SharePoint site http://127.0.0.1 or http://nameoflocalserver/pages/default.aspx and I was constantly prompted for the username and password. In SharePoint 2010, it can really annoy you by not accepting your username password credentials in the popup window.


Its a ‘feature’ on the server that you need to disable as a workaround (if you are an Admin/Developer) on a DEVELOPMENT and PREPROD environment.
Caution: Microsoft Best practices is out of scope in this article. Do your own research on this topic.

There are two methods to do this:
1.  Specify the host names in the registry – BackConnectionHostNames (more secure and recommended for PRODUCTION servers). Refer http://support.microsoft.com/kb/896861

2. Disable the loopback check – DisableLoopbackCheck (less secure and recommended for DEVELOPMENT environments). Read on to use this method 2 and add via an easy powershell cmd.

You would need to create a DWORD registry key in the registry called DisableLoopbackCheck and set it to 1.
Follow these steps:

Option 1: Add this registry entry by PowerShell

New-ItemProperty HKLM:\System\CurrentControlSet\Control\Lsa -Name "DisableLoopbackCheck" -value "1" -PropertyType dword
Option 2: Add this registry entry manually

Click Start, click Run, type regedit, and then click OK
In Registry Editor, locate the following registry key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa
Right-click Lsa, point to New, and then click DWORD Value. (In Win 2008, its DWORD 32bit)
Type DisableLoopbackCheck, and then press ENTER.
Right-click DisableLoopbackCheck, and then click Modify.
In the Value data box, type 1 and then click OK.
Quit Registry Editor.
You may need to restart your server.


For more information about this, click the following article number to view the article in the Microsoft Knowledge Base: 281308 (http://support.microsoft.com/kb/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

Comments

Popular posts from this blog

while creating new site collection in SharePoint 2019, Its giving correlation id. System.NullReferenceException: Object reference not set to an instance of an object.

Correlation id log: System.NullReferenceException: Object reference not set to an instance of an object.   at Microsoft.SharePoint.Administration.SPContentDatabaseCollection.FindBestContentDatabaseForSiteCreation(IEnumerable`1 contentDatabases, Guid siteIdToAvoid, SPContentDatabase database, SPContentDatabase databaseTheSiteWillBeDeletedFrom)     at Microsoft.SharePoint.Administration.SPContentDatabaseCollection.FindBestContentDatabaseForSiteCreation(SPSiteCreationParameters siteCreationParameters, Guid siteIdToAvoid, SPContentDatabase database, SPContentDatabase databaseTheSiteWillBeDeletedFrom)     at Microsoft.SharePoint.Administration.SPContentDatabaseCollection.FindBestContentDatabaseForSiteCreation(SPSiteCreationParameters siteCreationParameters)     at Microsoft.SharePoint.Administration.SPSiteCollection.GetContentDatabaseForSiteCreation(SPSiteSubscription siteSubscription, Boolean useHostHeaderAsSiteName, Uri siteUri)     at Microsoft.SharePoint.Administration.SPSiteCo

User Profile Application Proxy failed to retrieve partitions from User Profile Application

This issue happens mostly on the Farm installation. Everyone will say to recreate the UPS, restart the server and then it should work fine. But if you have used the Custom properties and created a managed property in Search then its very difficult to recreate it and then to create it again. The better solution so far i have researched is the following Stop the User Profile Synchronization service Stop the User Profile Service Start the User Profile Service Start the User Profile Synchronization service. I hope the above should help you resolve the issues. Cheers.

SharePoint site suddenly Read Only even for Administrators!

So at some point in time something had happened to our SharePoint 2010 server to cause what appeared to be a total lock down on the SharePoint sites. It must have been something strange, something weird, who knows what but it resulted in is ALL users, even site administrators and users with full administrative rights unable to do anything!  Nobody could add new documents or edit documents; nearly every single Document or Library option is greyed out! The fix it would seem is performed via the central administration website for your server. Central Administration -> Site Collection Quotas and Locks. Select your site collection Change the Site Lock Information radio button from “Read-only” to “Not locked” OK the changes You don’t even need to reboot or issue an iisreset command.