So, return to the original thread and ask. This allows both you and people
willing to contribute to track the issue.
The mirror you returned to is out of sync with the 2nd DC, the method of
restore needs to be discussed but the event logs will contain errors
indicating the problems.
You need to clarify whether the workstations were removed from the domain
and rejoined while the SBS was offline or whether this was at the time of
SBS coming back online. If both DC's were online at the time there's some
reason to doubt the status of all workstations.
I would not, at this time, perform a 'DCPromo /forceremoval' (something
easily found in the MS KB's) on the 2nd DC due to the indeterminate state of
the DC-DC relationship and that of the workstations to either DC.
You need to stop 'doing stuff' and start 'working through the problem'.
and you need to do so in the original thread.
"Jean Paul Mertens" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Indeed but no one was of any use...
>
> grts
>
> "SuperGumby [SBS MVP]" <(E-Mail Removed)> schreef in bericht
> news:%(E-Mail Removed)...
>> Jean Paul,
>> Several questions were asked and ideas discussed in response to your
>> first post on this, please refer back to the original thread.
>>
>> "Jean Paul Mertens" <(E-Mail Removed)> wrote in message
>> news:(E-Mail Removed)...
>>> Hello to all,
>>>
>>> I have a problem with a BDC (windows 2000 server) who does not see that
>>> the
>>> PDC (SBS 2000) is back on-line. I have got my PDC crashed,and for some
>>> reason the NT-Mirror had stopped some time ago. I have taken the PDC out
>>> of
>>> the network, and the BDC took over the security with no problem. I have
>>> put
>>> my (early stopped) mirror disk as master and restored alle backups so
>>> that
>>> the PDC is ok. I have put the PDC back in the network and had to
>>> disconnect
>>> (temporary set them to workgroup) all workstations and servers from the
>>> domain and then reconnect them to the domain. So far so good until I
>>> tried
>>> to do the same with my BDC but he keeps saying that there is no PDC so
>>> he
>>> can not disconnect and he is not trusted by the domain any more. I cant
>>> stop
>>> the AD becourse the server is BDC etc.. I'm turning in a round so my BDC
>>> in
>>> no more reachable by the domain and vise versa.
>>>
>>> The problem is , if I run DCPromo (on the BDC) I got the answer that a
>>> domain
>>> controller could not be contacted for the domain so he would not
>>> continue.
>>> The message window says that I have to take out the server out of the
>>> domain
>>> by making him member of a workgroup and then rejoin the domain. Bus as
>>> long
>>> as AD is running on the machine I can not leave the domain (In the
>>> system
>>> properties I can not change the identification of the computer becourse
>>> he
>>> aims to be a domaincontroller...
>>>
>>> and so we are back to start.
>>>
>>> Is there a tool (or a way) to force the BDC server to stop from thinking
>>> he
>>> has to stay a domain on his own so that I can downgrade the BDC to a
>>> simple
>>> server, take is 'out of the domain' and reconnect it to the 'new domain'
>>>
>>> Many tanks in advance
>>>
>>> Jean Paul
>>>
>>>
>>>
>>>
>>
>>
>
>
|
Similar Threads
Linear Mode
