Re: PDC/BDC problem



Hello cgbaten@xxxxxxxxx,

Did your BDC got all the FSMO rules after takeover? Check here:
http://support.microsoft.com/kb/324801

Seems that it is missing one of the roles after you take out the broken server and cleanup your metadata.


Best regards

myweb
Disclaimer: This posting is provided "AS IS" with no warranties, and confers no rights.



1 week ago, my PDC had a motherboard failure. The BDC with a shared
active directory immediately took over. I thought I had to run
dcpromo, but when I did it said it would uninstall AD and demote it to
a member server. Obviously I didn't want that to happen, so I left it
alone, and copied the critical files from backup tp the BDC, and sent
the PDC out for repair.

The PDC arrived last Monday. I had trouble introducing it back into
the domain because the server was still listed as a domain controller
in AD users and computers. I did a metadata cleanup to remove it. I
added the PDC back into the domain, used Configure your server to add
in DNS and AD, set up WINS, just as before. On Tuesday, I copied all
backup files to the DC, set up shares and permissions, and tested some
of the clients. The clients remembered user profiles and shares,
everything as if it never happened. The users were in the middle of
the workday on the backup server, so I waited until end of workday to
move any files they accessed back to the original server and told them
to log in as normal on Wednesday.

Here's the problem: The trusts between this domain (domain A) and one
in a building down the street (domain B) stopped working. I tried
everything to reestablish the trust. Somewhere in my panic I noticed I
could set up domain B at the trusting domain on the PDC, but could not
get domain B to trust domain A. Then I was able to get domain B to
trust domain A by setting up the trust on the BDC. So now the 2 way
trusts are dependent on both the PDC and BDC running at the same time.

The reason I got the errors, according to M$ and the event viewer,
have to do with the RID on the PDC not synchonizing with the domain,
caused when it suddenly dropped out of the domain, then was
reintoduced when fixed. I tried several things to get it to synch, but
all that I have read seems to say I need to take the servers out of
prodcution and start over. I can't have these users sitting around
while I try something that may not work. What if it's something else?
Does anyone have a suggestion, or should I live with the trust split?



.



Relevant Pages

  • Re: PDC/BDC problem
    ... Did your BDC got all the FSMO rules after takeover? ... broken server and cleanup your metadata. ... sent the PDC out for repair. ... everything to reestablish the trust. ...
    (microsoft.public.win2000.networking)
  • RE: Trust relationship betwen Win2003 & WinNT 4.0 Server
    ... the NT4.0 PDC from the Win2003 DC. ... I ping the simple name "qtech1" ... "RPS.LOCAL" in the Trusting Domains section of the Trust Relationships ... from the Win2003 server I can ping qtech1 without issue. ...
    (microsoft.public.windows.server.dns)
  • Re: PDC/BDC problem
    ... Did your BDC got all the FSMO rules after takeover? ... broken server and cleanup your metadata. ... The PDC arrived last Monday. ... everything to reestablish the trust. ...
    (microsoft.public.win2000.networking)
  • Re: Second Trust
    ... Will the Trust be there when I change my current PDC and make my new ... server a PDC? ... you'll have AD with the NT4 server as a BDC" Why would it be a BDC and ...
    (microsoft.public.win2000.active_directory)
  • Re: NT 4.0 to windows 2003 AD in place upgrade.
    ... PDC that I make a BDC is the one I will take offline before I do the ... Exchange server the PDC, allow to SYNC. ...
    (microsoft.public.windows.server.migration)