Old BDC can't see/sync with new 2003 AD

Discussion in 'Server Migration' started by Jesse, Jul 19, 2004.

  1. Jesse

    Jesse Guest

    We previously had an NT domain spanned over two sites
    (through a VPN). The primary site had the PDC while the
    other site had the BDC. I replaced the PDC with a new 2003
    box (using the same domain name, different IP, different
    computer name) and everything at the primary site works
    fine, but I can't get the BDC (which won't be upgraded for
    a while) to join/sync up with the domain. The physical
    connection is fine as both servers respond to pings from
    each other.

    I've tried using NETDOMO to reset the connection but that
    doesn't work.

    Any help?

    Jesse, Jul 19, 2004
    1. Advertisements

  2. Did you upgrade your original PDC or just replace it with a freshly built
    box? If you just replaced it and did not upgrade your PDC then you have a
    completely new domain and you will have to rebuild your NT BDC as it cannot
    move between domains like a Win2k/2k3 can. Let us know how you replaced this
    original PDC and maybe we can help.
    Scott Harding - MS MVP, Jul 19, 2004
    1. Advertisements

  3. Jesse

    Guest Guest

    the PDC was replaced with a new fresh box (the old domain
    was relatively small but quite messy, so I decided to
    start from scratch)

    Do you mean that I have to rebuild the domain on the BDC
    or do a fresh install of the OS (in which case I would
    probably use 2003 right away)?

    Guest, Jul 19, 2004
  4. Since you installed a new box you created a new domain so the NT4 BDC has no
    PDC to sync with and knows absolutely nothing about this new domain even
    though it has the same name. All of the clinet machines will have to join
    this new domain and the BDC will have to be rebuilt(only way to join a
    domain with a NT4 BDC). OR you could promote the BDC to PDC and setup a
    Trust between these two domains but since the names are the same this could
    cause issues and this would certainly be messy. As it stands now this BDC is
    the only member of the old domain and all the clients on it's side only know
    about it as the DC for this old domain. I would just upgrade the NT4 BDC to
    Window2k3 and then you could dcpromo it down and join the new domain. Or
    better yet rebuild the BDC from scratch with 2k3 and have it join the new
    domain and you could make it an additional DC for login purposes/fault
    Scott Harding - MS MVP, Jul 19, 2004
  5. Jesse

    Guest Guest

    thanks for the help
    Guest, Jul 19, 2004
  6. Hi Jesse,

    Thanks for your posting here and thanks for Scott's reply.

    It is recommended that you upgrade WinNT PDC to Windows Server 2003 not
    just replace it with a new box. As for your scenario, you can install a
    Windows 2003 server on the remote site then promote to be a DC.

    I believe the following documents will be helpful.

    HOW TO: Upgrade a Windows NT 4.0-Based PDC to a Windows Server 2003

    Upgrading from Windows NT Server 4.0 to Windows Server 2003

    Windows NT Server 4.0 Upgrade Guide

    Have a nice day!

    Bob Qin
    Product Support Services
    Microsoft Corporation

    Get Secure! - www.microsoft.com/security

    When responding to posts, please "Reply to Group" via your newsreader so
    that others may learn and benefit from your issue.
    This posting is provided "AS IS" with no warranties, and confers no rights.
    Bob Qin [MSFT], Jul 20, 2004
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.