Re: LSASRV Event ID: 40961

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: Mike Blake (MikeBlake_at_discussions.microsoft.com)
Date: 01/20/05 

Date: Thu, 20 Jan 2005 05:41:04 -0800

The IP address of the DC is 192.168.205.14 (subnet 192.168.205.0/24) and
Primary DNS is currently set at 127.0.0.1, although I have tried
192.168.205.14. Secondary DNS is blank.

Thanks,

Mike

"lazyadmin" wrote:

> What is the IP address of the DC and what are the Primary and Secondary DNS
> IP's?
>
> --
> Rod
> http://www.thelazyadmin.com
>
>
> "Mike Blake" <MikeBlake@discussions.microsoft.com> wrote in message
> news:8647611F-EB35-441C-AEB9-D829154A76EA@microsoft.com...
> > Reverse Lookup Zone for the subnet is configured and correctly populated.
> > No
> > other errors in any of the event logs.
> >
> > This error has been written to the log once per hour since it started to
> > occur.
> >
> > Thanks,
> >
> > Mike
> >
> > "lazyadmin" wrote:
> >
> >> Do you have Reverse Lookup Zones set up? This can happen when you try
> >> to
> >> register PTR records, and don't have reverse lookup zones.
> >>
> >> If not, check the other logs to see if there are any other warnings or
> >> errors occuring at the same time.
> >>
> >> --
> >> Rod
> >> http://www.thelazyadmin.com
> >>
> >>
> >> "Mike Blake" <MikeBlake@discussions.microsoft.com> wrote in message
> >> news:0F7BA3B2-75F1-4A5B-95E2-4BCB0E4EC50E@microsoft.com...
> >> >I started getting this message in the System Event Log about a month ago
> >> >on
> >> > our DC. Nothing had changed on the server around this time and
> >> > everything
> >> > seems to be working. The server is the only DC and DNS server in the
> >> > domain.
> >> >
> >> > Computer: FILE1
> >> > Source: LSASRV
> >> > Category: SPNEGO (Negotiator)
> >> > Event ID: 40961
> >> > Description: The Security System could not establish a secured
> >> > connection
> >> > with the server DNS/file1.mydomain.internal. No authentication protocol
> >> > was
> >> > available.
> >> >
> >> > Any suggestions for resolving this error are appreciated.
> >> >
> >> > Thanks,
> >> >
> >> > Mike
> >>
> >>
> >>
>
>
>

Quantcast