Re: Event ID: 40960 SPNEGO (Negotiator) authentication error



Are you experiencing any problems with users being able to access resources
or other problems? IMHO if not I would not worry about it as an error one or
two times a day as most likely nothing to worry about if everything works
fine and you have already done your homework with netdiag and checking
EventID.net. The link below is to a Google search on that Event ID where
you may find some more info. --- Steve

http://www.google.com/search?hl=en&lr=&q=event+id+40960+SPNEGO&btnG=Search

"Mauricio Reyes" <maoreyes@xxxxxxxxxxx> wrote in message
news:eF5ubOhWGHA.1220@xxxxxxxxxxxxxxxxxxxxxxx
Hi!
I have upgraded one of my domaincontrollers from Windows 2000 to Windows
2003.
I have still got one domaincontroller that is windows 2000.
The 2003 DC have the FSMO roles, both DC's has the global catalog and
running DNS server .
After the upgrade I frequently get error loggings on 3 of my Windows 2003
memberservers.
I get Lsasrv Event ID 40960 and 40961 in the systemlogs one to two times
a
day.
I tried to restart one of the memberservers and then the logging stopped
for
a week.
I have installed one new server after the upgrade of the domain, on that
server I don't get any
errors. I don't have any lsasrv errors on my windows 2000 memberservers or
the domaincontrollers. I been reading the suggestions on Event id net
regarding this error, but no luck when it comes to solving the problem.
I have tried to find the error with netdiag. but every test gets passed.

Has anyone a solution to this problem?


Event Type: Warning
Event Source: LSASRV
Event Category: SPNEGO (Negotiator)
Event ID: 40960
Date: 2006-04-05
Time: 05:59:15
User: N/A
Computer: vidstige
Description:
The Security System detected an authentication error for the server
cifs/donald.test.nu. The failure code from authentication protocol
Kerberos
was "The attempted logon is invalid. This is either due to a bad username
or
authentication information.
(0xc000006d)".

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 6d 00 00 c0

Event Type: Warning
Event Source: LSASRV
Event Category: SPNEGO (Negotiator)
Event ID: 40961
Date: 2006-04-05
Time: 05:59:15
User: N/A
Computer: vidstige
Description:
The Security System could not establish a secured connection with the
server
cifs/donald.test.nu. No authentication protocol was available.





.



Relevant Pages

  • Event ID: 40960 SPNEGO (Negotiator) authentication error
    ... I have upgraded one of my domaincontrollers from Windows 2000 to Windows ... running DNS server. ... After the upgrade I frequently get error loggings on 3 of my Windows 2003 ...
    (microsoft.public.windows.server.security)
  • Virtual PC 2004 with Windows 2003?
    ... Has anyone succesfully used Microsoft's Virtual PC 2004 with Windows ... physical box running Windows Server 2003. ... No authentication protocol was available. ... and the clock skew in the event log. ...
    (microsoft.public.cert.exam.mcse)
  • Virtual PC 2004 with Windows 2003?
    ... >physical box running Windows Server 2003. ... >The Security System could not establish a secured ... >No authentication protocol was available. ...
    (microsoft.public.cert.exam.mcse)
  • Re: add 2003 domaincontrollers to a windows 2000 domain
    ... > servers and want to install them as 2003 domaincontrollers in the windows ... > windows 2003 server CD) ... Make the 2 new servers additional domaincontrollers in the ...
    (microsoft.public.windows.server.active_directory)
  • Strange Issue - Date goes to the future!
    ... is running Windows XP Pro in a Windows 2003 AD domain. ... The Security System could not establish a secured connection with the ... server cifs/SQLSERVER.domainx.local. ... No authentication protocol was ...
    (microsoft.public.windowsxp.help_and_support)