Existing NT 4 BDC not communicating with new 2003 AD DC

Discussion in 'Server Migration' started by RayT, Oct 19, 2005.

  1. RayT

    RayT Guest

    We have upgraded our existing NT 4 Domain to active directory domain and it
    appears we are having some authentication/replication issues between the
    existing BDC's and the new 2003 DC. We upgraded the NT PDC to Win 2003 and
    created a clean Win 2003 DC, joined the domain and then migrated all the FSMO
    roles to the new clean box, then demoted the old upgrated NT box. Post
    upgrade on the existing NT BDC's we added the new DNS server to the TCP/IP
    properties of the NIC and added the new suffix as well, aside from that we
    did nothing else to the existing NT boxes.

    Info:
    One Domain nothing special
    All BDC's are running NT 4.0 with SP6
    The new DC is running Win 2003 w/ SP1

    2 Event Errors on the Existing NT 4.0 machines

    Event ID 5719 Source: NETLOGON
    No Windows NT Domain Controller is available for domain newdomain. (This
    event is expected and can be ignored when booting with the 'No Net' Hardware
    Profile.) The following error occurred:
    The RPC server is unavailable.

    Event ID 3013 Source: rdr
    The redirector has timed out a request to Win2003PDC-01

    Problem:
    It appears that we are having some Replication issues, newly created users
    in the Win2003 AD cannot access recources on the NT 4.0 File Servers.

    Questions
    Where do you see/configure the replication of the AD to SAM?
    All the existing Domain Controllers are in the AD in the Domain Controllers
    Container, i see them no where else in AD should they be somewhere else like
    in the AD Sites/Services in the Servers container?

    Thanks...
     
    RayT, Oct 19, 2005
    #1
    1. Advertisements

  2. Hi,

    This error can be a result of the TCP/IP Netbios Helper service being
    disabled on the server or Netbios over TCP/IP being disabled on one of the
    NIC's used to access the Terminal server. You should also verify that the
    Client for Microsoft networks is bound to the adapter used to access the
    server.

    Please run Netdiag/v on the problematic box

    B. The error can also be a result of a T server with multiple clients
    already connected failing under load. You can edit the following registry
    values
    on the server from which the clients are requesting resources:

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters

    Value name: MaxCmds
    Data type: REG_DWORD
    Radix: Decimal
    Value data: 500

    Value name: MaxWorkItems
    Data type: REG_DWORD
    Radix: Decimal
    Value data: 8192

    Value name: MaxMpxCt
    Data type: REG_DWORD
    Radix: Decimal
    Value data: 500

    Note: You may have to increase these values if the registry key does not
    work.

    More information about these values are available in 232476 - "Terminal
    Server
    Client Connections and Logon Limited by MaxWorkItem and" at
    <http://support.microsoft.com/?id=232476>

    Best regards,

    Vincent Xu
    Microsoft Online Partner Support

    Get Secure! - www.microsoft.com/security


    --------------------
     
    Vincent Xu [MSFT], Oct 20, 2005
    #2
    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.