Sergey81MemberJul 09, 2009 at 4:01 pm #143017
I’ve been dealing with my problem for a few months now. I have 3 servers/DC.
server1 – ex-SBS2003 (OS:wsk3 standard SP2)
server2 – new DC which ultimately will replace server1 (OS:wsk3 standard SP2)
server3 – exchange server (OS:wsk3 standard SP2)
server1 has migrated from 2003SBS to 2003 standard (using utility imove) but even being 2003SBS it has not being working properly (that was one of the reasons to move Exchange2003 to another machine).
Server1 and Serve2 are both DNS. AD replicates between all 3 servers. All 3 servers can resolve each other with no problems.
SYSVOL and NETLOGON never showed up on server2 and server3. I see a lot of 13508 events on both of them and Event 13516 never follows.
I’ve tried many things, including BurFlags D4/D2.
after D4/D2 trick event 13554 follows:
The File Replication Service successfully added the connections shown below to the replica set:
“DOMAIN SYSTEM VOLUME (SYSVOL SHARE)”
but right after the 2 of 13508 events follow for both servers:
The File Replication Service is having trouble enabling replication from server3 to server1 for c:adsysvoldomain using the DNS name server3.domain.com. FRS will keep retrying.
Following are some of the reasons you would see this warning.
 FRS can not correctly resolve the DNS name server3.domain.com from this computer.
 FRS is not running on server3.domain.com.
 The topology information in the Active Directory for this replica has not yet replicated to all the Domain Controllers.
This event log message will appear once per connection, After the problem is fixed you will see another event log message indicating that the connection has been established.
there is no errors or warnings in the eventlog on server1. dcdiag is “clean” as well as FRSdiag report.
You must be logged in to reply to this topic.