Results 1 to 2 of 2

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

  1. #1
    Mauricio Reyes Guest

    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.




  2. #2
    Steven L Umbach Guest

    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&l...GO&btnG=Search

    "Mauricio Reyes" <maoreyes@hotmail.com> wrote in message
    news:eF5ubOhWGHA.1220@TK2MSFTNGP02.phx.gbl...
    > 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.
    >
    >
    >




Similar Threads

  1. Event ID 40960 error 0xc000006d after power failure
    By Scott2580 in forum Active Directory
    Replies: 3
    Last Post: 08-01-2014, 10:44 AM
  2. Event ID : 40960 LSAsrv / SPNego
    By Iraiyavan in forum Active Directory
    Replies: 3
    Last Post: 19-11-2009, 03:04 PM
  3. Event ID 40960 LSASRV SPNEGO
    By SB in forum Windows Server Help
    Replies: 1
    Last Post: 01-03-2007, 03:01 PM
  4. EventID 40960, authentication error
    By Hamish via WinServerKB.com in forum Windows Server Help
    Replies: 9
    Last Post: 16-02-2007, 06:32 AM
  5. Event ID 40960 + 40961 / SPNEGO
    By Spencer in forum Windows XP Support
    Replies: 3
    Last Post: 15-11-2006, 08:47 PM

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Page generated in 1,696,056,311.96435 seconds with 17 queries