help with lsasrv error 40961

[Jason Miller]

Has anyone seen this error in the event log before I have found some stuff
on msft but nothing worked so far.

event is similar to this

Event Type: Warning
Event Source: LSASRV
Event Category: SPNEGO (Negotiator)
Event ID: 40961
Date: 5/18/2004
Time: 7:00:53 AM
User: N/A
Computer: Servername
Description:
The Security System could not establish a secured connection with the server
DNS/prisoner.iana.org. No authentication protocol was available.
Data:
0000: 8b 01 00 c0 <..À


any ideas?

(e-mail address removed)

 

[Tomasz Onyszko]

Has anyone seen this error in the event log before I have found some stuff
on msft but nothing worked so far.

event is similar to this

Event Type: Warning
Event Source: LSASRV
Event Category: SPNEGO (Negotiator)
Event ID: 40961
Date: 5/18/2004
Time: 7:00:53 AM
User: N/A
Computer: Servername
Description:
The Security System could not establish a secured connection with the server
DNS/prisoner.iana.org. No authentication protocol was available.
Data:
0000: 8b 01 00 c0 <..À


any ideas?

general ideas on this event You will find here:

http://www.eventid.net/display.asp?eventid=40961&eventno=1398&source=LsaSrv&phase=1


but ... are You sure that prisoner.iana.org is the best DNS Server to
authenticate in Your domain - maybe change this to the ip addres of Your
DC / DNS holding Your AD data

 

[Tomasz Onyszko]

Tomasz Onyszko wrote:

but ... are You sure that prisoner.iana.org is the best DNS Server to
authenticate in Your domain - maybe change this to the ip addres of Your
DC / DNS holding Your AD data

OK it's late (in my time zone ) ) I'v just notice word "simmiliar"
before event - forget about this change DNS advice

from eventid.net

<quote>

DweezMon (Last update 8/12/2003):
If the server name is prisoner.iana.org, blackhole-1.iana.org or
blackhole-2.iana.org, this is just telling you that Windows could not
perform a reverse lookup on the IP address configured as a DNS server.
These names are used to respond with "server does not exist" when you
use a private IP range, for example 192.168.1.0. This can be quickly
cleared up by adding a Reverse Lookup zone, and adding a record for your
DNS Server.
</quote>