RE: Sharepoint logon error- "Local Security Authority Cannot be Contac

Bejoy

unread,

Sep 14, 2005, 3:39:03 AM9/14/05

to

Hi,

Did you get to resolve the problem , i am having the same issue with Local
Security Authority cannot be contacted. And the problem seems to be
increasing. I can browse all other sites etc..

Regards,
Bejoy

"synaesthasia" wrote:

> We are developing a serious problem with our Sharepoint Portal Server 2003
> installation.
>
> Certain users in our AD domain have been experiencing problems with logging
> in to our portal and any of its subsites. When they try, they get an HTTP 500
> ("The Local Security Authority Cannot Be Contacted"). There is nothing wrong
> with their domain accounts that I can determine.
>
> The problem appears to be spreading. Users that previously had no difficulty
> will suddenly start experiencing this error on their computers. In some
> cases, they can successfully logon from a different computer, but not always.
> In any case, once they start getting the HTTP 500 error on a given PC, they
> are never able to log on again from that PC. Here are the event logs from our
> portal:
>
> Security:
> Type: Failure Audit/Event ID: 537
> User: NT AUTHORITY\SYSTEM
> Reason: An error occurred during logon
> Logon type: 3
> Logon process: NtLmSsp
> Authentication package: NTLM
> Status code: 0xC0000225
> Substatus code: 0x0
>
> Can anyone help?
>
> Eric Jones
> IT Manager, Ipas
> http://www.ipas.org
>

Bejoy

unread,

Sep 14, 2005, 3:56:03 AM9/14/05

to

Sorry forgot to add. I can browse the same site with the netbios name and no
problem, i cant use th eFQDN.

Please HELPPPPPPPPPP.

Bejoy

unread,

Sep 14, 2005, 6:41:04 AM9/14/05

to

I just gave more rights to one of the machines on the IUSR and it seems to
work. Please check and let me know.

synaesthasia

unread,

Sep 15, 2005, 12:17:07 PM9/15/05

to

No, we've not yet resolved the issue, but we found a partial workaround.

Users on our system typically login in the format "user...@domain.org" . We
found that when we had users re-authenticate with the older format
DOMAIN\username, suddenly it would work, and they no longer had problems
getting to the SPS site(s), even if they went back to using
user...@domain.org when authenticating.

It's as if authentication info is getting cached somewhere, and
authenticating with the older DOMAIN\username format "flushed" it out. Or
there's some kind of authentication miscommunication between IIS6 and IE6
(we've replicated the problem using Firefox, too, but not consistently).

I should stipulate that this (authenticating as DOMAIN\username) has
resolved the problem on all of the PCs that experienced the problem, except
one. Nothing we've done on that computer (including deleting and recreating
the profile) has worked.

We're still investigating this problem, since we don't think we've really
resolved anything - just found a quick fix. Anyone else out there got an idea?

synaesthasia

unread,

Sep 16, 2005, 11:55:06 AM9/16/05

to

I'm sorry, your message is unclear. What rights, specifically, did you give
to the IUSR account that resolved the problem? I assume that you're referring
to the local IUSR account on the Portal server machine itself.

Eddie

unread,

Oct 14, 2005, 8:58:01 PM10/14/05

to

I had the same issue the work around I found was to allow ntlm authenication
on both the sharepoint server and your domain controllers. I am waiting for
an answer from microsoft because that is weak to honest.

synaesthasia

unread,

Oct 14, 2005, 10:33:02 PM10/14/05

to

We already use NTLM authentication on our sharepoint & domain controllers;
always have.

Garrett

unread,

Dec 13, 2005, 6:28:25 PM12/13/05

to

I am experiencing the same thing with SP2 of Sharepoint portal 2003
installed. If we use the old style domain\username login it works fine. As
soon as we try the email address style-- we get the error most of the time.
Has anyone found a solution to this bug or has MS released a fix yet??

Garrett