www.eventid.net gibt zu deinem Problem folgendes aus:
Last update 10/27/2003):
This can occur if the File Replication Service (Ntfrs.exe) tries to authenticate before the directory service has started. See Q824217 to troubleshoot this problem.
From a newsgroup post: "In my case, this error occurred because the credentials specified in my DHCP server on “DC1” for dynamic DNS registration were misspelled".
Darren Monahan (Last update 10/26/2003):
If this warning appears by itself on an hourly basis, check that the credentials assigned to the DHCP server to register DNS dynamic updates are valid. Spelling errors or incorrect passwords and/or domain names can be to blame. To do this in Windows Server 2003, open the DHCP snap-in, open the properties for your DHCP server, select the "Advanced" tab, and click the "Credentials" button. Verify the username, password, and domain listed here are valid.
Anonymous (Last update 10/26/2003):
We had the same problem on one of the workstations that had a long logon timeout. This has worked for us:
1. logon as an admin.
2. remove from domain.
3. add to domain.
4. restart.
Adrian Grigorof (Last update 8/12/2003):
From a newsgroup post: "If there is there a matching 40960 event then it is more likely a forward lookup zone issue in DNS. If not, it probably is that Windows is looking for a reverse lookup zone."
As per Q823712, this may occur when you restart the server that was promoted to a domain controller.
DweezMon (Last update 8/12/2003):
If the server name is prisoner.iana.org, blackhole-1.iana.org or blackhole-2.iana.org, this is just telling you that Windows could not perform a reverse lookup on the IP address configured as a DNS server. These names are used to respond with "server does not exist" when you use a private IP range, for example 192.168.1.0. This can be quickly cleared up by adding a Reverse Lookup zone, and adding a record for your DNS Server.
Adrian Florin Moisei (Last update 5/23/2003):
From a newsgroup post: "If the system is Win XP and if the errors were not occuring under a different profile the folowing steps can solve the problem:
1. Log on as a different user
2. Back up the profile in mention.
3. Delete the profile.
4. Create a new profile by logging on.
5. Restore the files from the backed up profile."
Gunnar Carlson (Last update 5/18/2003):
I get this error on all DC's that I upgrade to Windows 2003 Server. I upgraded one DC from W2k3 beta3 to the released version, and the events immediately started to show up. After I created the reverse lookup zones for the network they stopped.
Anonymous (Last update 5/10/2003):
This happened when machines were trying to register PTR records, and we didn't have reverse lookup zones. The solution was to add them for all our subnets.
DJ (Last update 5/2/2003):
I'm on a small home test network with Win2k domain behind a Linksys 4 port DSL router. The router handles DNS. A power failure sacked my domain controllers. After some restores and GP resets, my DCs were up and talking. But my workstation could not access AD Users and computers. The problem was the order of DNS in the Lynksys. After putting my local DNS server first in the list on the Linksys, I was able to get to AD.
Greg Martin
Had this on a WinXP workstation which could no longer access domain resources. The fix was changing the DNS settings to point to a Win2k DNS which was tied into Active Directory. Apparently the workstation could no longer locate SVR records for the kerberos authentication server. These records were not in our UNIX DNS but were in the Win2k DNS. Related directly to Event 40960 - LsaSrv.
Links Q823712 , Q824217
Hoffe, du kannst damit was anfangen, eventid.net hat mir jedenfalls auch immer weitergeholfen.
Greetings
weimer
