T
Tech Girl
I struggled with this for a while and finally had to call
Microsoft. They suggested KB 244474. It worked problem
solved. Now we are planning to push this out in a Group
Policy.
I suggested that Microsoft add the client error to their
knowledge base article in the future. Hopefully they will.
Previous posting was:
I'm seeing the following in the Syslog on my XP clients.
TechNet hasn't
provided me with any information about this warning. From
what I can tell,
the clients are able to login to the domain.
---
Event Type: Warning
Event Source: LSASRV
Event Category: SPNEGO (Negotiator)
Event ID: 40961
Date: 9/2/2004
Time: 3:21:07 PM
User: N/A
Computer: WORKSTATION1
Description:
The Security System could not establish a secured
connection with the server
cifs/domaincontroller.domain.loc. No authentication
protocol was available.
Microsoft. They suggested KB 244474. It worked problem
solved. Now we are planning to push this out in a Group
Policy.
I suggested that Microsoft add the client error to their
knowledge base article in the future. Hopefully they will.
Previous posting was:
I'm seeing the following in the Syslog on my XP clients.
TechNet hasn't
provided me with any information about this warning. From
what I can tell,
the clients are able to login to the domain.
---
Event Type: Warning
Event Source: LSASRV
Event Category: SPNEGO (Negotiator)
Event ID: 40961
Date: 9/2/2004
Time: 3:21:07 PM
User: N/A
Computer: WORKSTATION1
Description:
The Security System could not establish a secured
connection with the server
cifs/domaincontroller.domain.loc. No authentication
protocol was available.