Discussion Locked

Trust Relationship

0 helpful
5 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I reconfigured my PDC completely. After I was complete my BDC's have been showing error messages in the Event Viewer as follows: The computer --- tried to connect to the server --- using the trust relationship established by the --- domain. However, the computer lost the correct security identifier (SID) when the domain was reconfigured. Reestablish the trust relationship.

I have tried to reestablish the trust relationship with no luck. I understand that I must run setup on all the BDC's to correct this. I would like to do this without setup. Does anyone no a better way? I thought that maybe if I could copy the SAM and paste it on each of the BDC's that might work. I need help.

5 replies

by avachon

hi, since you reconfigured your PDC, the BDC's will not be able to communicate with the PDC because they will not recognize the security identifier (SID). You could remove the BDCs from the domain (server manager) and then re- add them. When the bdcs rejoing the domain they will recognize each others' SIDS and be able to communicate. Make sure you are using the same admin password. Good luck.

by davew43boss

I tried this and did not have any luck. It still gives the same message in the event viewer. thanks anyway.

by ian mclaws

I assume that by "reconfiguring" you mean that the PDC was re-installed. There is no way to re-establish the internet trust between domain controllers in the same domain. You cannot remove BDC's from an NT domain, NT4 domain controllers will not migrate. You have only two options, if simply restoring the original PDC from a backup is not possible.
1. Run a setup on all BDC's, as you mentioned. This is a bit of a pain, though.
2. Using Server Manager on one of the BDC's, promote a BDC to the PDC role to save your SAM database, then re-install the old PDC as a new BDC. When you do this, you can then promote it back to PDC status; problem solved, with no loss of SAM.
You cannot simply copy the SAM database to another server. Each copy of the SAM is system specific, and will not start on another system.
Next time, promote a BDC to the PDC role before you reconfigure the PDC, then reconfigure it, then promote it back to PDC role.
Hope this helps

This discussion is closed to new replies.