DC not initializing Event ID 13508 and 13565

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I have 3 DC's on my network. I need to reinstall Win2k on my first DC. The
problem I am having is when I shut down my first DC, users cannot access the
other DC's or a member server. I looked at replication and that is fine.
Although, in the event log of 2nd DC, I have the following Event ID's 13508
and 13565 stating that it cannot initialize the first DC. I need to be able
to take this DC down with no interruption.

Any ideas/advice?

Thank you
 
Andrei,

Thank you. You are correct. It is the 2nd server that will not act as a
DC. However, I follow the instructions from the link you gave. I shared
the SYSVOL folder on the 2nd DC and also had to modify the registry on the
1st DC to allow it to the JRNL_WRAP_ERROR status automatically.

Now, I am receiving on both servers Event ID 13516 stating that the FRS is
no longer preventing the server from becoming a DC. Now, how do I verify my
2nd DC is "acting " as a DC becuase when I shut down the 1st DC, I still have
users complaining they can't authenticate.

Additonally, on the 2nd DC I am getting Event ID 213 staing replication of
license information failed. I looked at the 1st and the LLS service is
disabled. When I attemp to enable it, the system hangs. Is this service
preventing my 2nd DC to become "active"?
 
Have you make the second DC a Global Catalog? User can't authenticate
without a global catalog.
 
As a matter of fact, I was just going to let you know that I forgot to make
it a GC. Everything seems to be working now. Thanks for your initial help!
 
Back
Top