2008 r2 Dns Replikasyon Hatası

bu normal bir durum.

hakan hocam dc uzerine logon olan kullanicilari nerden gorebilirim?

Loglardan görebilirsiniz.

http://www.ultimatewindowssecurity.com/securitylog/encyclopedia/event.aspx?eventid=4624

Merhaba Hakan bey,

eski dc i kapatıp yeni kurduğun 2008 dc i de restart ettim. yeni dc 2008 açılınca active director ve dns hiç bir şekilde ulaşamıyor aşağıdaki hatayı veriyor.

 "You cannot modify domain or trust information because a primary domain controller (PDC) emulator cannot be contacted. please verify that the pdc emulator for the current domain and the network are both online and functioning properly"

PDC rolunu kendinde görmüyor nedense ama ben rolleri ona geçirdim hatta active directory uzerinden baktığımdada roller onun ustunde gözüküyor

muhtemel geçiş öncesi dc yani 2003 çok sorunluydu bundan dolayıda geçiş başarılı olmadı. Bundan sonrası için yorum yapamıyorum çünkü görmek lazım, normal tüm tavsiyeleri yapmış görünüyorsunuz ancak yinede eski dc ye bağımlı iseniz elle yapılmış bir ayar veya gözünüzden kaçan bir sorun olabilir.

Hakan hocam

2003 r2 sp2 32 bit eski dc, yenisi 2008 r2 64 bit 32/64 bit uyumsuzluğu olamaz değilmi?

ayrıca yapımda site'lar vardı merkez ve antalya diye benim eski additional server antalyadaydı onu ortamdan kaldırıp burada 2008 r2 kurdum ve bunu additional yaptım daha sonra bu 2008 r2 sunucuda resetleme sorunu meydana geldi donanımsal sebeplerden dolayı o yüzden onuda ortamdan kaldırıp yeni bir 2008 sunucu kurdum ve onu additional yaptım şuandaki additional serverim bu yani.

 2003 r2 eski dc'min system state backup ları var elimde ben rolleri 2008 r2 sunucudan eski dc ye tekrar geri aktarsam additional serveride ortamdan kaldırsam ve daha sonra bu system state backup ile yeni bir 2008 r2 sunucu eklesem ortama nasıl olur?

Sen bir hayli kurcalamışsın 🙁 rolleri geri almak ve 2008 i ortamdan kaldırmak mantıklı, sonra dc deki sorunları çözmen ve yeniden eklemen daha mantılı.

Merhaba Hakan Bey,

 şuan 2008 server uzerinde aldığım tek hata aşağıdaki gibi. bunun haricinde iki server dada herhangibir hata yok.

security event larda kullanıcı loginlerini görebiliyorum 2008 uzerinde. bu akşam testi yapıcam eskisini katıp denicem eğer yine olmazsa dediğiniz gibi geri dönücem.

çok teşekkürler ilginize.

Log Name:      Active Directory Web Services
Source:        ADWS
Date:          30.09.2011 00:03:14
Event ID:      1202
Task Category: ADWS Instance Events
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      Dc.domain.com.tr
Description:
This computer is now hosting the specified directory instance, but Active Directory Web Services could not service it. Active Directory Web Services will retry this operation periodically.
 
 Directory instance: GC
 Directory instance LDAP port: 3268
 Directory instance SSL port: 3269

Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="ADWS" />
    <EventID Qualifiers="49152">1202</EventID>
    <Level>2</Level>
    <Task>3</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2011-09-29T21:03:14.000000000Z" />
    <EventRecordID>414</EventRecordID>
    <Channel>Active Directory Web Services</Channel>
    <Computer>Dc.domain.com.tr</Computer>
    <Security />
  </System>
  <EventData>
    <Data>GC</Data>
    <Data>3268</Data>
    <Data>3269</Data>
  </EventData>
</Event>

Bu önemli bir hata değil.

Merhaba Hakan Hocam

dedigim gibi eski dc yi kapattim suan 2008 r2 dc olarak calisiyor kullanicilar login olabiliyor paylasimlardada bir problem yok. ama event viewer da asagidaki gibi hatalar aliyorum. acaba bu hatalar eski c ile hala replication yapmak istedigi icinmi aliyorum eski dc i ortamdan tamamen kaldirsam duzelirmi acaba bu durum.

Log Name:      Directory Service
Source:        Microsoft-Windows-ActiveDirectory_DomainService
Date:          01.10.2011 00:11:44
Event ID:      2092
Task Category: Replication
Level:         Warning
Keywords:      Classic
User:          ANONYMOUS LOGON
Computer:      Dc.domain.com.tr
Description:

This server is the owner of the following FSMO role, but does not consider it valid. For the partition which contains the FSMO, this server has not replicated successfully with any of its partners since this server has been restarted. Replication errors are preventing validation of this role.
 
Operations which require contacting a FSMO operation master will fail until this condition is corrected.
 
FSMO Role: DC=domain,DC=com,DC=tr
 
User Action:
 
1. Initial synchronization is the first early replications done by a system as it is starting. A failure to initially synchronize may explain why a FSMO role cannot be validated. This process is explained in KB article 305476.
2. This server has one or more replication partners, and replication is failing for all of these partners. Use the command repadmin /showrepl to display the replication errors.  Correct the error in question. For example there maybe problems with IP connectivity, DNS name resolution, or security authentication that are preventing successful replication.
3. In the rare event that all replication partners being down is an expected occurance, perhaps because of maintenance or a disaster recovery, you can force the role to be validated. This can be done by using NTDSUTIL.EXE to seize the role to the same server. This may be done using the steps provided in KB articles 255504 and 324801 on http://support.microsoft.com .
 
The following operations may be impacted:
Schema: You will no longer be able to modify the schema for this forest.
Domain Naming: You will no longer be able to add or remove domains from this forest.
PDC: You will no longer be able to perform primary domain controller operations, such as Group Policy updates and password resets for non-Active Directory Domain Services accounts.
RID: You will not be able to allocation new security identifiers for new user accounts, computer accounts or security groups.
Infrastructure: Cross-domain name references, such as universal group memberships, will not be updated properly if their target object is moved or renamed.
Event Xml:
<Event xmlns=" http://schemas.microsoft.com/win/2004/08/events/event ">
  <System>
    <Provider Name="Microsoft-Windows-ActiveDirectory_DomainService" Guid="{0e8478c5-3605-4e8c-8497-1e730c959516}" EventSourceName="NTDS General" />
    <EventID Qualifiers="32768">2092</EventID>
    <Version>0</Version>
    <Level>3</Level>
    <Task>5</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8080000000000000</Keywords>
    <TimeCreated SystemTime="2011-09-30T21:11:44.771667800Z" />
    <EventRecordID>501</EventRecordID>
    <Correlation />
    <Execution ProcessID="528" ThreadID="676" />
    <Channel>Directory Service</Channel>
    <Computer>Dc.domain.com.tr</Computer>
    <Security UserID="S-1-5-7" />
  </System>
  <EventData>
    <Data>DC=domain,DC=com,DC=tr</Data>
  </EventData>
</Event>

Log Name:      Directory Service
Source:        Microsoft-Windows-ActiveDirectory_DomainService
Date:          30.09.2011 23:55:44
Event ID:      1168
Task Category: Internal Processing
Level:         Error
Keywords:      Classic
User:          ANONYMOUS LOGON
Computer:      Dc.domain.com.tr
Description:
Internal error: An Active Directory Domain Services error has occurred.
 
Additional Data
Error value (decimal):
1053
Error value (hex):
41d
Internal ID:
30007a0
Event Xml:
<Event xmlns=" http://schemas.microsoft.com/win/2004/08/events/event ">
  <System>
    <Provider Name="Microsoft-Windows-ActiveDirectory_DomainService" Guid="{0e8478c5-3605-4e8c-8497-1e730c959516}" EventSourceName="NTDS General" />
    <EventID Qualifiers="49152">1168</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>9</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8080000000000000</Keywords>
    <TimeCreated SystemTime="2011-09-30T20:55:44.667981500Z" />
    <EventRecordID>491</EventRecordID>
    <Correlation />
    <Execution ProcessID="528" ThreadID="692" />
    <Channel>Directory Service</Channel>
    <Computer>Dc.domain.com.tr</Computer>
    <Security UserID="S-1-5-7" />
  </System>
  <EventData>
    <Data>1053</Data>
    <Data>41d</Data>
    <Data>30007a0</Data>
  </EventData>
</Event>

Log Name:      System
Source:        Microsoft-Windows-DfsSvc
Date:          30.09.2011 23:56:09
Event ID:      14550
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      Dc.domain.com.tr
Description:
The DFS Namespace service could not initialize cross forest trust information on this domain controller, but it will periodically retry the operation. The return code is in the record data.
Event Xml:
<Event xmlns=" http://schemas.microsoft.com/win/2004/08/events/event ">
  <System>
    <Provider Name="Microsoft-Windows-DfsSvc" Guid="{7DA4FE0E-FD42-4708-9AA5-89B77A224885}" EventSourceName="DfsSvc" />
    <EventID Qualifiers="49152">14550</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2011-09-30T20:56:09.000000000Z" />
    <EventRecordID>9535</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>System</Channel>
    <Computer>Dc.domain.com.tr</Computer>
    <Security />
  </System>
  <EventData Name="DfsNoXForestInfo">
    <Binary>4B050000</Binary>
  </EventData>
</Event>

Log Name:      System
Source:        Microsoft-Windows-GroupPolicy
Date:          30.09.2011 23:55:52
Event ID:      1055
Task Category: None
Level:         Error
Keywords:     
User:          SYSTEM
Computer:      Dc.domain.com.tr
Description:
The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following:
a) Name Resolution failure on the current domain controller.
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
Event Xml:
<Event xmlns=" http://schemas.microsoft.com/win/2004/08/events/event ">
  <System>
    <Provider Name="Microsoft-Windows-GroupPolicy" Guid="{AEA1B4FA-97D1-45F2-A64C-4D69FFFD92C9}" />
    <EventID>1055</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>1</Opcode>
    <Keywords>0x8000000000000000</Keywords>
    <TimeCreated SystemTime="2011-09-30T20:55:52.639595500Z" />
    <EventRecordID>9517</EventRecordID>
    <Correlation ActivityID="{4E3C3BAB-D2BD-4FAF-8003-0E60A3A1358A}" />
    <Execution ProcessID="972" ThreadID="1160" />
    <Channel>System</Channel>
    <Computer>Dc.domain.com.tr</Computer>
    <Security UserID="S-1-5-18" />
  </System>
  <EventData>
    <Data Name="SupportInfo1">1</Data>
    <Data Name="SupportInfo2">1632</Data>
    <Data Name="ProcessingMode">1</Data>
    <Data Name="ProcessingTimeInMilliseconds">182380</Data>
    <Data Name="ErrorCode">10054</Data>
    <Data Name="ErrorDescription">An existing connection was forcibly closed by the remote host. </Data>
  </EventData>
</Event>