Re: Event Warning 40961 LSASRV


OK, thanks, that makes sense... unfortuantely however I'm still getting
event warnings as follows:
----------------------------------------------------------------------------------
Event Type: Warning
Event Source: LSASRV
Event Category: SPNEGO (Negotiator)
Event ID: 40960
Date: 29.10.2005
Time: 23:12:48
User: N/A
Computer: DNS1
Description:
The Security System detected an authentication error for the server
DNS/ns.provider.net. The failure code from authentication protocol Kerberos
was "There are currently no logon servers available to service the logon
request.
(0xc000005e)".
----------------------------------------------------------------------------------
Event Type: Warning
Event Source: LSASRV
Event Category: SPNEGO (Negotiator)
Event ID: 40961
Date: 29.10.2005
Time: 23:12:48
User: N/A
Computer: DNS1
Description:
The Security System could not establish a secured connection with the server
DNS/ns.provider.net. No authentication protocol was available.
----------------------------------------------------------------------------------

Note that these event warnings are occuring together at a frequency of
exactly one hour on both my primary and secondary DNS servers...





"Todd J Heron" wrote:

> Now that you've set the primary and secondary DNS servers in TCP/IP settings
> on the NIC to be your own DNS servers, you will not see the LSASRV errors
> (as you've confirmed). The reason is the system whether a DC or not will
> attempt to register it's computer name into the DNS zone of it's primary DNS
> suffix (which will be it's AD domain). Your ISP's server will not hold a
> zone for your AD domain therefore the registration will fail.
>
> --
> Todd J Heron, MCSE
> Windows Server 2003/2000/NT; CCA
> ----------------------------------------------------------------------------
> This posting is provided "as is" with no warranties and confers no rights
>
>
> "The Vogon" <TheVogon@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:13B44657-BCC8-4A3B-853A-B6D31DA9C792@xxxxxxxxxxxxxxxx
> Thanks for the reply Todd...
>
> Ok, but I'm curious now :-)
>
> ....the servers throwing the LSASRV error were in fact, amongst other things,
> my primary and secondary DNS servers... and are on the same physical network
> and subnet as my provider's DNS servers... I've set the primary and
> secondary
> DNS servers in TCP/IP settings on the NIC to be my own DNS servers, and as
> yet haven't seen the LSASRV error... but why? Please note my servers are NOT
> DC's and NOT using ADS :-S
>
> The Vogon
>
>
.

Relevant Pages

  • Re: Help SMPT Errors
    ... FAIL Reverse DNS entries for MX records ERROR: The IP of one or more of your ... it may mean that your DNS servers did not respond fast enough). ... INFO NS records at parent servers Your NS records at the parent servers ... PASS Parent nameservers have your nameservers listed OK. ...
    (microsoft.public.exchange.admin)
  • Re: Windows 2000 logon process
    ... Paul Williams ... when clients are accessing the GPO stored in SYSVOL during logon. ... PW>> Sound's like - that's a combination of DNS and Dfs client pointing ... Global Catalogue servers? ...
    (microsoft.public.win2000.active_directory)
  • Re: Replication issues
    ... I wanted to say Zone Transfers not Zone Forwarding. ... on 2 servers out of 4 DNS servers. ... DNS and 2003 DNS and how to set up Conditional Forwarding. ...
    (microsoft.public.windows.server.active_directory)
  • Re: Howto refresh IIS 6 Application pool identity credential info
    ... You already have 80% of the work setup (DNS Aliases and HostHeaders) on the ... domain accounts (one for each layer) should be sufficient. ... The Application Servers are load balanced clustered, ... as the account name and SPN alias is correctly defined on both nodes. ...
    (microsoft.public.inetserver.iis.security)
  • Re: ad and dns setup
    ... domain It gave me 2 errors, no dns servers have dns records for this dc ... error no logon servers.. ... Make sure that the _msdcs zone exists and the scope is set to ... MCSE, MVP Directory Services ...
    (microsoft.public.windows.server.active_directory)