asked on

EventID 40961: LSASRV: ......No authentication protocol was available.

We get this error on a workstation:

EventID 40961
Type: Warning
Source: LSASRV
SPNEGO (Negotiator)

The Security System could not establish a secured connection with the server ldap/PERSVR03.pmom.local/pmom.local@pmom.local. No authentication protocol was available.

What is the sulution for this error?

SOLUTION

souseran

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

andrewijnholds

ASKER

We have 5 servers, and PERSVR03 is the Domain Controller, with Windows 2003 Enterprise.
The error occurs a few times a day...

ASKER CERTIFIED SOLUTION

souseran

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

andrewijnholds

ASKER

Tomorrow I install the hotfix, and the day after tomorrow, I can check if the problem is solved.

Thanks!

bigusdickus

did it fix let people know

andrewijnholds

ASKER

Yes, problem solved :)

bigusdickus

Andrew what hotfix did you try any thing to point me in the dorection please

andrewijnholds

ASKER

I don't know anymore, but you could first try a reboot...

And then try the hotfixes...

good luck!

harisri

Hi,
I am facing a problem in my LAN. We have a router, which has 2 network cards. From one (Card A) network card, the connection goes to the switch of one floor, and other card (Card B) is connected to the switch of the other floor. One day, we had a an issue with the Card B card. Then some of the systems under networkcard B was connected to Card A.

After changing the network card B, those system changed back to network card B. But after this, internet is getting disconnected in these systems. When I change the IP address, net gets restored. After few hours, it will get disconnected again. Can somebody help me to resolve this issue ?

Note: Card A IP: 10.10.10.0 series
Card B IP: 192.168.10.0 series

Regards,

DAQuintyne

would the simple removal from the domain resolve this issue at the client end or simply resetting the password at the server end to restore syncronisation with the Kerberos Ticket!