Discussion Locked

Domain Changes

0 helpful
9 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
Our network recently removed a PDC from our domain. That PDC became a PDC for a different network (while we had a T-1 connection). Now I continue to get NETLOGON errors for the different domain (no longer connected at all) even though I have removedall instances referencing the PDC that was removed including the WINS database as well as the registry on our promoted PDC. How do I keep the NETLOGON errors from occuring?

9 replies

by dc1

Make sure that you remove any trust relationships that may have been created. Also verify that there are no entries in your Lmhost and host files

by daleg_48

After looking for trusts in User Mgr for Domains, I found that a trust was automatically created for the new domain as the other admin brought the new PDC on line before our T-1 was disconnected. Thanks.

by agibbs

Let me make sure I understand what you did:

You took your PDC and removed it from an existing domain, then used it to create a NEW domain, not physically connected to the first one?

If that's the case, I say wipe out your server & reinstall itas a new PDC. I've tried what you've done several times and never have been able to get it to work straight. I think it has something to do with the SIDs generated when you create a domain.

by tgotschall

The PDC must be demoted in the original domain by promopting one of the other BDC's to a PDC. It then can be shut down and deleted from the domain. Then take it to the other site and re-install NT with the new domain's name. The Domain is identifiedby the SIDs comprising it, the name is only for our convenience.

This discussion is closed to new replies.