I have 2 remote sites and 1 main site, each remote site has it's own DC, DNS, DHCP and WINS. Each DC is checked to be it's own global catalog server. The main site has it's own DC, DNS, DHCP and wins as well.
Both remote sites replicate back with the main site. They do not replicate with each other.
IN event viewer I see no events for File replication event on each of the remote site DCs or in the main site DC.
In event viewer I see no replication events for directory services for the remote site DCs or in the main site.
I do have a warning of event 13508 but not event 13509. From what i understand, this means that the computer isn't really a DC even though i went through dcpromo.
The Sysvol and netlogon folder appears to be shared on the remote DCs. I can get to it from the main site DC.
I ran dcdiag,exe and all tests were passed with no errors.
I ran dcdiag.exe and both remote site passes all tests except 1
and it's "servername failed frsevent."
How do i fix this problem? What is frsevent.
What's strange is, if i make a change to user account, Like changing the phone number. after 30 minutes, the change is shown on the same user in the other DC's at the remote site. So what is happening here? is replication happening or is it not?
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Open AD Sites & Services on each DC. Drill down to the NTDS Settings object underneath each server, right-click on each connection and select "Replicate now", see if it errors out or indicates completion.
Additionally, run repadmin /replsum from the command line on each DC, as well as 'repadmin /syncall <DC FQDN> <DOMAIN DN>'
Please take a look at this article, it may be of good use:
http://technet.microsoft.c
I tried this and the DC that logged the 13508 error was from the main site not the remote sites.
"ntfrsutl version <FQDN of remote domain controller>
If this fails, check network connectivity by using the Ping command to ping the fully qualified domain name (FQDN) of the remote domain controller from the computer that logged the FRS event ID 13508. If this fails, then troubleshoot as a DNS or TCP/IP issue. If it succeeds, confirm that the FRS service is started on the remote domain controller."
I ran the command on the main site DC, and no errors, I ran it with the FQDN of itself and the FQDN of the remote DC. NO issues or errors.
I checked and file replication service is running on all the remote DC
"Open AD Sites & Services on each DC. Drill down to the NTDS Settings object underneath each server, right-click on each connection and select "Replicate now", see if it errors out or indicates completion."
I get one error related to replication from the main DC about one remote DC. THe remote DCs have no such error.
The file replication service is having truoble enabling replication from R2 to DC1 for c:\windows\sysvol\domain using the DNS name XXXXX. FRS will keep trying.
Following are some reason you would see this warning.
1. FRS can not correctly resolve the DNS XXXX from this computer
2. FRS is not running on R2
3. The topology information in AD for this replica has not yet replicated to all the domain controllers
Business Accounts
Answer for Membership
by: dooleydogPosted on 2008-03-31 at 11:19:04ID: 21247764
i would try to restart the FRS in services.
If that doesn't take care of the problem, then you may have a FRS version mismatch or a schema mismatch.
here are some steps to try.
Good Luck,
Procedures for Troubleshooting FRS Event 13508 without Event 13509
Examine the FRS event ID 13508 to determine the machine that FRS has been unable to communicate with.
Determine whether the remote machine is working properly, and verify that FRS is running on it. Type the following command at a command prompt on the computer that logged the FRS event ID 13508 and press ENTER:
ntfrsutl version <FQDN of remote domain controller>
If this fails, check network connectivity by using the Ping command to ping the fully qualified domain name (FQDN) of the remote domain controller from the computer that logged the FRS event ID 13508. If this fails, then troubleshoot as a DNS or TCP/IP issue. If it succeeds, confirm that the FRS service is started on the remote domain controller.
Determine whether FRS has ever been able to communicate with the remote computer by looking for FRS event ID 13509 in the event log and see if the FRS problem correlates to recent change management to networking, firewalls, DNS configuration, or Active Directory infrastructure.
Determine whether anything between the two machines is capable of blocking RPC traffic, such as a firewall or router.
Confirm that Active Directory replication is working. For more information about troubleshooting Active Directory replication, see Troubleshooting Active Directory Replication Problems in this guide.