Event Id Ve Ag kilitlenmesi Hk.

merhaba,

firmamizin diger bolgesinde serverden kisilere baglanamiyorum. kisilerden surekli agdaki paylasimlara baglanamiyorum sikayeti aliyiorum. 

server eventlere baktigimda bu hatalari goruyorum. bu konuda yardimci olabilirmisiniz?

tesekkurler.

Event warning 2089

This directory partition has not been backed up since at least the

following number of days.
 
Directory partition:
DC=ForestDnsZones,DC=domainadi,DC=local
 
'Backup latency interval' (days): 90
 
It is recommended that you take a backup as often as possible to

recover from accidental loss of data. However if you haven't taken a

backup since at least the 'backup latency interval' number of days,

this message will be logged every day until a backup is taken. You can

take a backup of any replica that holds this partition.
 
By default the 'Backup latency interval' is set to half the 'Tombstone

Lifetime Interval'. If you want to change the default 'Backup latency

interval', you could do so by adding the following registry key.
 
'Backup latency interval' (days) registry key:
System\CurrentControlSet\Services\NTDS\Parameters\Backup Latency

Threshold (days)

---------------------------------------------------------------

Event Error ID 1864

This is the replication status for the following directory partition on

the local domain controller.
 
Directory partition:
DC=ForestDnsZones,DC=domainadi,DC=local
 
The local domain controller has not recently received replication

information from a number of domain controllers.   The count of domain

controllers is shown, divided into the following intervals.

--------------------------------------------------------------------
Event Error Id2087

Active Directory could not resolve the following DNS host name of the source domain controller to an IP address. This error prevents additions, deletions and changes in Active Directory from replicating between one or more domain controllers in the forest. Security groups, group policy, users and computers and their passwords will be inconsistent between domain controllers until this error is resolved, potentially affecting logon authentication and access to network resources.
 
Source domain controller:
 serverfw
Failing DNS host name:
 59ad30b3-9b8d-44a6-8c26-b197aa237c6e._msdcs.domainadi.local
 
NOTE: By default, only up to 10 DNS failures are shown for any given 12 hour period, even if more than 10 failures occur.  To log all individual failure events, set the following diagnostics registry value to 1:
 
Registry Path:
HKLM\System\CurrentControlSet\Services\NTDS\Diagnostics\22 DS RPC Client
 
User Action:
 
 1) If the source domain controller is no longer functioning or its operating system has been reinstalled with a different computer name or NTDSDSA object GUID, remove the source domain controller's metadata with ntdsutil.exe, using the steps outlined in MSKB article 216498.
 
 2) Confirm that the source domain controller is running Active directory and is accessible on the network by typing "net view \\<source DC name>" or "ping <source DC name>".
 
 3) Verify that the source domain controller is using a valid DNS server for DNS services, and that the source domain controller's host record and CNAME record are correctly registered, using the DNS Enhanced version of DCDIAG.EXE available on http://www.microsoft.com/dns
 
  dcdiag /test:dns
 
 4) Verify that that this destination domain controller is using a valid DNS server for DNS services, by running the DNS Enhanced version of DCDIAG.EXE command on the console of the destination domain controller, as follows:
 
  dcdiag /test:dns
 
 5) For further analysis of DNS error failures see KB 824449:
   http://support.microsoft.com/?kbid=824449
 
Additional Data
Error value:
 11004 The requested name is valid, but no data of the requested type was found.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.