D
Dave Lykens
I have two Domain Controllers, win2k running AD. There
was an event log entry about not replicating properly so
one machine could become a domain controller(it seemed
like it was acting like one already) and the event message
said to go into the registry and add a Journal Wrapping
entry and make the value 1 so it would restart or
replicate than change the entry back to 0, which I did. I
now have no domain!! When I try to open AD users and
computers I get a warning that: Naming can not be found
because the domain does not exist! When I click ok the AD
MMC comes up with a red X over the active directory. If I
right click on it and connect to domain controller, I can
select either one and wala! my scdisted.psu.edu domain
comes up and appears normal. But first it says I am
administering the domain.________(blank) do I want to
switch to the scdisted.psu.edu domain. I say yes and it
comes up. So now I have no logon server available, DNS
does not work right since it needs Active Directory but I
can sit at the computers and both my domain controllers
show up in AD and even seem to replicate when I do a
replicate now in Sites and Services. (Same red x though
when I first go into it) I think it is a sysvol issue.
In the sysvol folder there is a domain folder and a
scdisted.psu.edu folder which I copied into the domain
folder after nothing else worked. However I discovered
that within the scdisted.psu.edu folder it is duplicated
about 12 levels deep! Same for the folder I put in the
domain folder. I can't delete these since they seem to be
protected, running or whatever. It seems it is a sys vol
issue but I do not know what to do to fix it, if there is
a fix. I restarted one machine in the AD restore mode but
that did not seem to solve anything, I reloaded windows
on one, then SP4 and then updates but that didn't help
either. If you have any ideas about this or could provide
some insight I would appreciate it. I even tried to
demote one machine from a DC but guess what, it wants to
connect to the domain before you remove it!
was an event log entry about not replicating properly so
one machine could become a domain controller(it seemed
like it was acting like one already) and the event message
said to go into the registry and add a Journal Wrapping
entry and make the value 1 so it would restart or
replicate than change the entry back to 0, which I did. I
now have no domain!! When I try to open AD users and
computers I get a warning that: Naming can not be found
because the domain does not exist! When I click ok the AD
MMC comes up with a red X over the active directory. If I
right click on it and connect to domain controller, I can
select either one and wala! my scdisted.psu.edu domain
comes up and appears normal. But first it says I am
administering the domain.________(blank) do I want to
switch to the scdisted.psu.edu domain. I say yes and it
comes up. So now I have no logon server available, DNS
does not work right since it needs Active Directory but I
can sit at the computers and both my domain controllers
show up in AD and even seem to replicate when I do a
replicate now in Sites and Services. (Same red x though
when I first go into it) I think it is a sysvol issue.
In the sysvol folder there is a domain folder and a
scdisted.psu.edu folder which I copied into the domain
folder after nothing else worked. However I discovered
that within the scdisted.psu.edu folder it is duplicated
about 12 levels deep! Same for the folder I put in the
domain folder. I can't delete these since they seem to be
protected, running or whatever. It seems it is a sys vol
issue but I do not know what to do to fix it, if there is
a fix. I restarted one machine in the AD restore mode but
that did not seem to solve anything, I reloaded windows
on one, then SP4 and then updates but that didn't help
either. If you have any ideas about this or could provide
some insight I would appreciate it. I even tried to
demote one machine from a DC but guess what, it wants to
connect to the domain before you remove it!