Announcement

Collapse
No announcement yet.

Added 2003 server to 2000 network, some AD errors now

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Added 2003 server to 2000 network, some AD errors now

    Hello!

    I installed a new server with intentions to migrate everything from a 2000 server to a 2003 server on a small network (8 users). The 2000 server is SP4 and the 2003 is SP1 as a guest in VMware Server 1.0.4 on SUSE Linux host.

    I first ran adprep to upgrade AD, joined the 2003 box to the network, and made it a domain controller. Then, I followed the Petri document on transferring the FSMO roles, and that went fine. I also made the 2003 server a GC.

    I ran dcdiag and it seems as not everything has transferred over as previously thought. The NETLOGON and SYSVOL replication seems to be busted.

    I found numerous articles about resetting the SYSVOL replication and seizing the FSMO roles to be sure they are moved, but was unsure if I should do that or if another method would be advisable. The 2000 server is still here and running, so I have options.

    Thanks for any opinions.

    -m

    dcdiag:
    Domain Controller Diagnosis

    Performing initial setup:
    Done gathering initial info.

    Doing initial required tests

    Testing server: Default-First-Site-Name\CKSERVER2
    Starting test: Connectivity
    ......................... CKSERVER2 passed test Connectivity

    Doing primary tests

    Testing server: Default-First-Site-Name\CKSERVER2
    Starting test: Replications
    ......................... CKSERVER2 passed test Replications
    Starting test: NCSecDesc
    ......................... CKSERVER2 passed test NCSecDesc
    Starting test: NetLogons
    Unable to connect to the NETLOGON share! (\\CKSERVER2\netlogon)
    [CKSERVER2] An net use or LsaPolicy operation failed with error 1203, No network provider accepted the given network path..
    ......................... CKSERVER2 failed test NetLogons
    Starting test: Advertising
    Warning: DsGetDcName returned information for \\ckserver.captainkens.com, when we were trying to reach CKSERVER2.
    Server is not responding or is not considered suitable.
    ......................... CKSERVER2 failed test Advertising
    Starting test: KnowsOfRoleHolders
    ......................... CKSERVER2 passed test KnowsOfRoleHolders
    Starting test: RidManager
    ......................... CKSERVER2 passed test RidManager
    Starting test: MachineAccount
    ......................... CKSERVER2 passed test MachineAccount
    Starting test: Services
    ......................... CKSERVER2 passed test Services
    Starting test: ObjectsReplicated
    ......................... CKSERVER2 passed test ObjectsReplicated
    Starting test: frssysvol
    ......................... CKSERVER2 passed test frssysvol
    Starting test: frsevent
    There are warning or error events within the last 24 hours after the

    SYSVOL has been shared. Failing SYSVOL replication problems may cause

    Group Policy problems.
    ......................... CKSERVER2 failed test frsevent
    Starting test: kccevent
    ......................... CKSERVER2 passed test kccevent
    Starting test: systemlog
    ......................... CKSERVER2 passed test systemlog
    Starting test: VerifyReferences
    ......................... CKSERVER2 passed test VerifyReferences

    Running partition tests on : ForestDnsZones
    Starting test: CrossRefValidation
    ......................... ForestDnsZones passed test CrossRefValidation
    Starting test: CheckSDRefDom
    ......................... ForestDnsZones passed test CheckSDRefDom

    Running partition tests on : DomainDnsZones
    Starting test: CrossRefValidation
    ......................... DomainDnsZones passed test CrossRefValidation
    Starting test: CheckSDRefDom
    ......................... DomainDnsZones passed test CheckSDRefDom

    Running partition tests on : Schema
    Starting test: CrossRefValidation
    ......................... Schema passed test CrossRefValidation
    Starting test: CheckSDRefDom
    ......................... Schema passed test CheckSDRefDom

    Running partition tests on : Configuration
    Starting test: CrossRefValidation
    ......................... Configuration passed test CrossRefValidation
    Starting test: CheckSDRefDom
    ......................... Configuration passed test CheckSDRefDom

    Running partition tests on : captainkens
    Starting test: CrossRefValidation
    ......................... captainkens passed test CrossRefValidation
    Starting test: CheckSDRefDom
    ......................... captainkens passed test CheckSDRefDom

    Running enterprise tests on : captainkens.com
    Starting test: Intersite
    ......................... captainkens.com passed test Intersite
    Starting test: FsmoCheck
    ......................... captainkens.com passed test FsmoCheck

  • #2
    Re: Added 2003 server to 2000 network, some AD errors now

    Looks like there is either some junk in DNS or something related to computer names.

    DNS resolves a query for CKSERVER2 to CKSERVER. Did you rename the DC after DCPROMO ? before DCPROMO ?
    Guy Teverovsky
    "Smith & Wesson - the original point and click interface"

    Comment


    • #3
      Re: Added 2003 server to 2000 network, some AD errors now

      Hi, no, no renaming was done before or after the process. DNS has stayed the same as well.

      -m

      Comment


      • #4
        Re: Added 2003 server to 2000 network, some AD errors now

        Hi,

        Once clear your event viewer (I mean just save them before clearing them) and try DCdiag.

        Because I have seen that sometime DCDiag picks information from past events also.

        Regards,
        Kapil Sharma
        ~~~~~~~~~~~~~
        Life is too short, Enjoy It.

        Comment

        Working...
        X