Šta je novo?

problem sa domain controllerom

gogi100

Slavan
Učlanjen(a)
30.12.2005
Poruke
239
Poena
319
windows server 2003 mi se usporio totalno. Sta moze biti u pitanju? event viewer-u

dobijam poruke

Kod:
Event Type:    Error
Event Source:    NTDS Replication
Event Category:    DS RPC Client 
Event ID:    2087
Date:        28.6.2009
Time:        20:48:36
User:        NT AUTHORITY\ANONYMOUS LOGON
Computer:    moj server
Description:
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: 
 stari domen kontroler
Failing DNS host name: 
 9ae5100a-a9fa-4207-97ad-8974ebc1ad4b._msdcs.moj domen 
 
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.


Event Type:    Error
Event Source:    NTDS Replication
Event Category:    Replication 
Event ID:    1864
Date:        28.6.2009
Time:        16:17:36
User:        NT AUTHORITY\ANONYMOUS LOGON
Computer:    moj server
Description:
This is the replication status for the following directory partition on the local domain controller. 
 
Directory partition:
DC=ForestDnsZones,DC=domen,DC=ORG,DC=YU 
 
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. 
 
More than 24 hours:
1 
More than a week:
1 
More than one month:
1 
More than two months:
1 
More than a tombstone lifetime:
1 
Tombstone lifetime (days):
180 
 Domain controllers that do not replicate in a timely manner may encounter errors. It may miss password changes and be unable to authenticate. A DC that has not replicated in a tombstone lifetime may have missed the deletion of some objects, and may be automatically blocked from future replication until it is reconciled. 
 
To identify the domain controllers by name, install the support tools included on the installation  CD and run dcdiag.exe. 
You can also use the support tool repadmin.exe to display the replication latencies of the domain controllers in the forest.   The command is "repadmin /showvector /latency <partition-dn>".

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

Ja sam ranije izvrsio prebacivanje komplet servera sa starog na novi: Active Directory,Domain Controllera,DNS-a,DHCP-a. Pokusao sam da obrisem trgove starog servera rucno. Sad je pitanje da li je to dovoljno. Jedino sto ne mogu da obrisem je u Active Directory Sites and Services-Sites-Servers, tu mi se nalaze oba servera i stari i novi. Kad pokusam da to uradim izbaci mi poruku da moram da oristim dcpromo. Moze li mi ko dati uputstvo sta da radim?
Hvala
 
Gogi prosao ti je tombstone lifetime. 6 meseci ti se nije replicirao domain controller sto znaci da sad moras demote/promote da uradis.

Vrlo nezgodna situacija, pogledaj sites and services zasto ti ne radi sinhronizacija.
A sto se usporio to je jos jedno pitanje.
 
demontirao sam stari server pomocu komande ntdsutil i brisanjem starog servera iz active directory site and services i active directory user and computers. U event vieweru se vise ne pojavljuje ova greska. Mislim da je posao dobro odradjen i server se ubrzao. Ostalo mi je da resim jos WSUS. On mi nije radio,ali cinimi se da cu i njega resiti upgradom sa WSUS 3.0 u WSUS 3.0 SP1
 
WSUS bi trebao da radi, mozda nesto nisi potrefio kod namestanja.
Jel sam WSUS ne radi ili se klijenti ne updatuju? Mozda ti polisa nije dobra?
 
resio sam i wsus. na nekim klijentima na kojima su bili virusi, oni su ocisceni ali je program za njihovo sklanjanje ugasio automatic update service. cim sam ga ukljucio sve je profunkcionisalo
hvala
 
Nazad
Vrh Dno