Event ID: 40960 SPNEGO (Negotiator) authentication error



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

  • Re: NT to W2K3 Migration
    ... You cannot just promote a member server to AD. ... upgrade your PDC to windows 2000 or 2003, whichever flavor of AD you want to ... Upgrading from Windows NT Server 4.0 ... ensure that you have designed a DNS ...
    (microsoft.public.windows.server.active_directory)
  • Re: NT to W2K3 Migration
    ... How to Upgrade from Windows NT Server 4.0 ... Best Practice Active Directory Design for Managing Windows Networks ...
    (microsoft.public.windows.server.active_directory)
  • Re: Native 2003 mode and NT4 workstations?
    ... Migrating from Windows NT Server 4.0 to Windows Server 2003 ... How to Upgrade from Windows NT Server 4.0 ... ensure that you have designed a DNS ...
    (microsoft.public.windows.server.active_directory)
  • Re: Migrating NT4 to Windows 2003
    ... Migrating from Windows NT Server 4.0 to Windows Server 2003 ... How to Upgrade from Windows NT Server 4.0 ... Best Practice Active Directory Design for Managing Windows Networks ...
    (microsoft.public.windows.server.active_directory)
  • Re: Migrating NT4 to Windows 2003
    ... Migrating from Windows NT Server 4.0 to Windows Server 2003 ... How to Upgrade from Windows NT Server 4.0 ... Best Practice Active Directory Design for Managing Windows Networks ...
    (microsoft.public.windows.server.active_directory)