Re: HTTP 500 Error - Local Security Authority Cannot be contacted
- From: Michael Bailey <Michael Bailey@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Fri, 2 Feb 2007 13:46:01 -0800
I am having this problem as well, and I can give the following background:
· If you are immediately brought to the error screen (without being
prompted for credentials), it is because Windows has cached your
username/password for the site, and those credentials are no longer valid.
· You SHOULD be prompted for new credentials in situations like this, but
this error seems to occur only when the username is the userPrincipalName (as
opposed to the sAMAccountName), and you are connecting via NTLM.
Does anyone out there know anything else on how to eliminate the problem
altogether?
"itenginerd" wrote:
I just ran into this problem today and have a workaround in place. I'm not.
using Sharepoint, but FWIW, here's what I've found...
Server setup is 2003/IIS, with an application running as a service account
one page set as Windows Integrated Auth + Basic Auth--which is roughly how
Sharepoint works. This security is for one specific page that I want users
to have to authenticate to (for logging purposes). I tried, and tried, but
was getting 401.1 errors (access denied/invalid credentials) and the
occasional 500/LSA error. This problem occurred regardless of user
account--joe user or domain admin acct.
- When I was seeing this error with IE, I was able to authenticate
successfully via Firefox (even if I changed to purely IWA without Basic
enabled).
- I was able to use the server's browser to access the content.
- I fiddled with the local security policy to no avail.
That's the setup. Here's what fixed it for me:
- Disabling IWA from the server allows me to authenticate (i.e. using Basic
Auth only)
- Using one of my coworker's computers. I run Vista on mine (IE7), and she
has XP (IE6)
So from *my* testing, this looks to be an issue with the browser not
properly authenticating via IWA. The browser negotiates to use IWA as
opposed to Basic, but then isn't using the right protocol NTLM/NTLM2/Kerb/etc.
Very strange. Especially since IE7 is being pushed via WinUpdate currently...
Hope that helps make sense for you guys. Let me know how it goes, or if
that was a one-off fix!
(j)
James
"Jeffrey Sparks" wrote:
I still haven't been able to figure out what the problem is. If you find a
solution, please let me know.
--
Jeff
"Daniel" <Daniel@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:5BE90746-5614-414E-9ED0-781A17CB7832@xxxxxxxxxxxxxxxx
I've been expereincing the same thing and haven't found anything as a
workaround. I'm hoping someone will reply to this thread.
"Jeffrey Sparks" wrote:
I just started having this problem on my computer. It happened after I
had to reboot the server and change my personal password.
Anytime I try to access the windows SharePoint services website I get the
following error:
The Local Security Authority cannot be contacted
Has anyone else run into this problem? I can't seem to find any fix for
this.
--
Jeff Sparks
IT Director
Business Communication Center
- Prev by Date: Re: Eliminate use of Shared Workspace from Sharepoint 2003
- Next by Date: Starting over from scratch.
- Previous by thread: Re: Eliminate use of Shared Workspace from Sharepoint 2003
- Next by thread: Re: HTTP 500 Error - Local Security Authority Cannot be contacted
- Index(es):
Relevant Pages
|
Loading
