﻿<?xml version="1.0" encoding="UTF-8"?>
<!--RSS generated by Windows SharePoint Services V3 RSS Generator on 9/9/2010 12:02:41 AM-->
<?xml-stylesheet type="text/xsl" href="/blog/_layouts/RssXslt.aspx?List=9b1cc4d9-40d2-492e-abf0-2aeb5b3950c3" version="1.0"?>
<rss version="2.0">
  <channel>
    <title>PathLight: Posts</title>
    <link>http://www.lpsol.com/blog/Lists/Posts/AllPosts.aspx</link>
    <description>RSS feed for the Posts list.</description>
    <lastBuildDate>Thu, 09 Sep 2010 04:02:41 GMT</lastBuildDate>
    <generator>Windows SharePoint Services V3 RSS Generator</generator>
    <ttl>60</ttl>
    <image>
      <title>PathLight: Posts</title>
      <url>/blog/_layouts/images/homepage.gif</url>
      <link>http://www.lpsol.com/blog/Lists/Posts/AllPosts.aspx</link>
    </image>
    <item>
      <title>Unable To Login to WSS Sites Locally</title>
      <link>http://www.lpsol.com/blog/Lists/Posts/ViewPost.aspx?ID=19</link>
      <description><![CDATA[<div><b>Body:</b> <div class=ExternalClass7BE99425A1D24071ADDADF1857796646><p>I was having a neat little problem where I was unable to login to WSS sites on my development virtual machine. I would keep getting prompted and prompted for credentials even though the credentials belonged to the admins group. This was a particularly painful issue given that some of the web parts were failing with the wonderful “non-specific error.”</p> <p>After a little scouring I found <a href="http://support.microsoft.com/kb/896861" target="_blank">this little registry hack</a> (Method 1) which fixed the problem:</p> <ol> <ol> <li> <p>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: </p> <p><a href="http://support.microsoft.com/kb/281308/">281308</a> Connecting to SMB share on a Windows 2000-based computer or a Windows Server 2003-based computer may not work with an alias name</p> <li>Click <strong>Start</strong>, click <strong>Run</strong>, type regedit, and then click <strong>OK</strong>.  <li>In Registry Editor, locate and then click the following registry key:  <p><strong>HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa</strong></p> <li>Right-click <strong>Lsa</strong>, point to <strong>New</strong>, and then click <strong>DWORD Value</strong>.  <li>Type DisableLoopbackCheck, and then press ENTER.  <li>Right-click <strong>DisableLoopbackCheck</strong>, and then click <strong>Modify</strong>.  <li>In the <strong>Value data</strong> box, type 1, and then click <strong>OK</strong>.  <li>Quit Registry Editor, and then restart your computer.</li></ol></ol> <p>Curiously the login problem didn’t exist with the Central Admin site.</p></div></div>
<div><b>Category:</b> SharePoint;SysAdmin</div>
<div><b>Published:</b> 12/14/2009 10:11 AM</div>
]]></description>
      <author>Michael A. Vickers</author>
      <category>SharePoint;SysAdmin</category>
      <pubDate>Mon, 14 Dec 2009 15:11:45 GMT</pubDate>
      <guid isPermaLink="true">http://www.lpsol.com/blog/Lists/Posts/ViewPost.aspx?ID=19</guid>
    </item>
  </channel>
</rss>