C
Chris Hall
Greetings,
I was checking event logs on server1yesterday, when I noticed a warning for
NtFRS, event id: 13508. "The file replication service is having trouble
enabling replication from server2 to server1 for c:\winnt\sysvol\domain\
using the dns name server2.domain.com." Past that, it says that dns couldn't
resolve the name, frs is not running on server2 or the topology info in AD
hasn't replicated yet. I'm not getting and 13509 event ids following the
13508 error. On both servers, I run dcdiag /fix and get the following
message: Starting test: frssysvol There are errors after the sysvol has been
shared. The sysvol can stop the AD from starting. Server2 passed test
sysvol. I get the same message on Server1. In fact, I get this message on
all DCs except for the forest root DC. I belive my dns is properly
configured and whenever I add a dc, I ALWAYS verify the installation. I see
there are a couple of tools out there to check for frs problems, any
suggestions on which to try first?
I was checking event logs on server1yesterday, when I noticed a warning for
NtFRS, event id: 13508. "The file replication service is having trouble
enabling replication from server2 to server1 for c:\winnt\sysvol\domain\
using the dns name server2.domain.com." Past that, it says that dns couldn't
resolve the name, frs is not running on server2 or the topology info in AD
hasn't replicated yet. I'm not getting and 13509 event ids following the
13508 error. On both servers, I run dcdiag /fix and get the following
message: Starting test: frssysvol There are errors after the sysvol has been
shared. The sysvol can stop the AD from starting. Server2 passed test
sysvol. I get the same message on Server1. In fact, I get this message on
all DCs except for the forest root DC. I belive my dns is properly
configured and whenever I add a dc, I ALWAYS verify the installation. I see
there are a couple of tools out there to check for frs problems, any
suggestions on which to try first?