Failed frsevent test

I am running dcdiag from a Server2003 box (member server) on a domain with 2 W2K domain controllers. I am getting the following message when the test fails for both domain controllers:

Starting test: frsevent
         There are warning or error events within the last 24 hours after the

         SYSVOL has been shared.  Failing SYSVOL replication problems may cause

         Group Policy problems.
         ......................... MCST-DC failed test frsevent

In the event viewer I get the following error which I believe is what the test is refering to:

Event Type:      Warning
Event Source:      NtFrs
Event Category:      None
Event ID:      13508
Date:            11/30/2004
Time:            7:50:31 AM
User:            N/A
Computer:      MCST-DC
The File Replication Service is having trouble enabling replication from MCST_FILE to MCST-DC for c:\winnt\sysvol\domain using the DNS name FRS will keep retrying.
 Following are some of the reasons you would see this warning.
 [1] FRS can not correctly resolve the DNS name from this computer.
 [2] FRS is not running on
 [3] 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.

For more information, see Help and Support Center at
0000: ba 06 00 00               º...    

Are these two errors related? How do I troubleshoot deeper to resolve (what is the next step)?

Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Sounds like a DNS issue.  Try hooking up to the sysvol share from the other dc via command line.  Start-Run-\\mcst-dc\sysvol.  If that doesn't work you probably have a DNS infrastructure issue (maybe misconfigured TCP/IP settings or the DNS service isn't working properly).  If DNS is OK then check your sites and services topology.
It could very well be DNS. It could also be just a passing warning. See if you have an Event 13509 after the 13508. If so, you have nothing to worry about.
Go to and search for event 13508. It is a very common error

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Glad I could help!
Error 13508 means the DC cannot become a Domain controller. Check if the syslog folder and netlogon folder have been shared by the DC. If they haven't it sounds like some of the ports are closed that enable the DC to replicate ( probably due to a firewall).

Try this link it will tell you what ports need to be open and ways around a firewall.

If there is a ristriction on your network for UDP byte size it will stop Kerberos Authentication from working

Try this link

There is also a link to a utility on this page called Portquery that will allow you to test for the open ports you need.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows 2000

From novice to tech pro — start learning today.