|
Question : Event Errors: dnsapi (11165); LsaSrv (40961 & 40960); and W32Time (14 & 29)
|
|
In a Windows 2003 SBS environment with all XP Pro clients several of the systems are producing event warnings and errors as follows: dnsapi (11165); LsaSrv (40961 & 40960); netlogon (5719); and W32Time (14 & 29).
Of the six workstations, three are experiencing periodic disconnects from the server which require a restart to reconnect. I have posted this disconnect issues as a separate question as I am not sure if all of theses events are related.
Detail event messages are posted below:
Event Type: Error
Event Source: NETLOGON
Event Category: None
Event ID: 5719
Date: 2/3/2007
Time: 11:34:46 AM
User: N/A
Computer: JIM-PC
Description:
No Domain Controller is available for domain PROCTORDAVISCOM due to the following:
There are currently no logon servers available to service the logon request. .
Make sure that the computer is connected to the network and try again. If the problem persists, please contact your domain administrator.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 5e 00 00 c0 ^..À
Event Type: Warning
Event Source: W32Time
Event Category: None
Event ID: 14
Date: 2/3/2007
Time: 11:34:50 AM
User: N/A
Computer: JIM-PC
Description:
The time provider NtpClient was unable to find a domain controller to use as a time source. NtpClient will try again in 15 minutes.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Event Type: Error
Event Source: W32Time
Event Category: None
Event ID: 29
Date: 2/3/2007
Time: 11:34:50 AM
User: N/A
Computer: JIM-PC
Description:
The time provider NtpClient is configured to acquire time from one or more time sources, however none of the sources are currently accessible. No attempt to contact a source will be made for 14 minutes. NtpClient has no source of accurate time.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
====
Event Type: Warning
Event Source: DnsApi
Event Category: None
Event ID: 11165
Date: 2/3/2007
Time: 9:55:20 AM
User: N/A
Computer: STAFF1-PC
Description:
The system failed to register host (A) resource records (RRs) for network adapter
with settings:
Adapter Name : {2CE5304C-7418-48B6-A3C0-074CEBFD102F}
Host Name : staff1-pc
Primary Domain Suffix : ProctorDavisCompany.local
DNS server list :
68.94.156.1, 68.94.157.1, 64.160.192.70
Sent update to server :
IP Address(es) :
10.1.1.161
The reason the system could not register these RRs was because the DNS server contacted refused the update request. The reasons for this might be (a) you are not allowed to update the specified DNS domain name, or (b) because the DNS server authoritative for this name does not support the DNS dynamic update protocol.
To register the DNS host (A) resource records using the specific DNS domain name and IP addresses for this adapter, contact your DNS server or network systems administrator.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 2a 23 00 00 *#..
====
Event Type: Warning
Event Source: LSASRV
Event Category: SPNEGO (Negotiator)
Event ID: 40960
Date: 2/3/2007
Time: 11:49:44 AM
User: N/A
Computer: STAFF2-PC
Description:
The Security System detected an attempted downgrade attack for server cifs/STAFF1-PC. The failure code from authentication protocol Kerberos was "There are currently no logon servers available to service the logon request.
(0xc000005e)".
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
====
Event Type: Warning
Event Source: LSASRV
Event Category: SPNEGO (Negotiator)
Event ID: 40961
Date: 2/3/2007
Time: 11:49:45 AM
User: N/A
Computer: STAFF2-PC
Description:
The Security System could not establish a secured connection with the server cifs/STAFF1-PC. No authentication protocol was available.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
|
Answer : Event Errors: dnsapi (11165); LsaSrv (40961 & 40960); and W32Time (14 & 29)
|
|
I would guess that the workstations DNS settings are pointing to your ISP DNS servers. In a windows domain the workstations need to point DNS requests to the Windows Server (domain controller with DNS server running) Various problems can occur when DNS isn't setup properly, including the time error, and netlogon error.
|
|
|
|
|
