Announcement

Collapse
No announcement yet.

Replacing an Old Win2k DC with win2k3 Server

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

  • Replacing an Old Win2k DC with win2k3 Server

    Hi .
    I have one server in my network .
    doing DNS / DHCP / AD.

    I followed this article trying to add another server to replace the old one

    http://support.microsoft.com/kb/555549


    I dcpromo the server , and followed most of the steps there.
    My problem is , after DCPromo + restart + FSMO in graphical interface.
    I don't have the SYSVOL + NETLOGON folder .
    whenever I try to access the AD and look for the scripts I'm getting an error telling me to choose which DC to use ( Any / ..../)

    on the event log I get an error for the FRS


    Code:
    The File Replication Service is having trouble enabling replication from DYNSERVER to DYN-DC for c:\windows\sysvol\domain using the DNS name DynServer.DynNetwork.local. FRS will keep retrying. 
     Following are some of the reasons you would see this warning. 
     
     [1] FRS can not correctly resolve the DNS name DynServer.DynNetwork.local from this computer. 
     [2] FRS is not running on DynServer.DynNetwork.local. 
     [3] The topology information in the Active Directory for this replica has not yet replicated to all the Domain Controllers. 
     
     This event log message will appear once per connection, After the problem is fixed you will see another event log message indicating that the connection has been established.
    
    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

    I can ping servers from both sides
    FRS is started on both servers.

    Any Information would be much appreciated.

    Thanks !!

    Nadi.

  • #2
    Re: Replacing an Old Win2k DC with win2k3 Server

    Can you ping by FQDN as well as netbios name?
    Which server is generating the event?
    Tom Jones
    MCT, MCSE (2000:Security & 2003), MCSA:Security & Messaging, MCDBA, MCDST, MCITP(EA, EMA, SA, EDA, ES, CS), MCTS, MCP, Sec+
    PhD, MSc, FIAP, MIITT
    IT Trainer / Consultant
    Ossian Ltd
    Scotland

    ** Remember to give credit where credit is due and leave reputation points where appropriate **

    Comment


    • #3
      Re: Replacing an Old Win2k DC with win2k3 Server

      Error is on the New DC.

      cmd on the new box :


      C:\Documents and Settings\administrator.DYNNETWORK>ping dynserver

      Pinging dynserver.dynnetwork.local [10.10.10.200] with 32 bytes of data:

      Reply from 10.10.10.200: bytes=32 time<1ms TTL=128
      Reply from 10.10.10.200: bytes=32 time<1ms TTL=128
      Reply from 10.10.10.200: bytes=32 time<1ms TTL=128

      Ping statistics for 10.10.10.200:
      Packets: Sent = 3, Received = 3, Lost = 0 (0% loss),
      Approximate round trip times in milli-seconds:
      Minimum = 0ms, Maximum = 0ms, Average = 0ms
      Control-C
      ^C
      C:\Documents and Settings\administrator.DYNNETWORK>ping dynserver.dynnetwork.local

      Pinging dynserver.dynnetwork.local [10.10.10.200] with 32 bytes of data:

      Reply from 10.10.10.200: bytes=32 time<1ms TTL=128
      Reply from 10.10.10.200: bytes=32 time<1ms TTL=128


      cmd on the old box :


      Microsoft Windows 2000 [Version 5.00.2195]
      (C) Copyright 1985-2000 Microsoft Corp.

      C:\Documents and Settings\Administrator>ping dyn-dc

      Pinging dyn-dc.DynNetwork.local [10.10.10.220] with 32 bytes of data:

      Reply from 10.10.10.220: bytes=32 time<10ms TTL=128
      Reply from 10.10.10.220: bytes=32 time<10ms TTL=128

      Ping statistics for 10.10.10.220:
      Packets: Sent = 2, Received = 2, Lost = 0 (0% loss),
      Approximate round trip times in milli-seconds:
      Minimum = 0ms, Maximum = 0ms, Average = 0ms
      Control-C
      ^C
      C:\Documents and Settings\Administrator>ping dyn-dc.dynnetwork.local

      Pinging dyn-dc.DynNetwork.local [10.10.10.220] with 32 bytes of data:

      Reply from 10.10.10.220: bytes=32 time<10ms TTL=128

      Ping statistics for 10.10.10.220:
      Packets: Sent = 1, Received = 1, Lost = 0 (0% loss),


      Want me to include
      netdiag
      dcdiag

      ?

      Comment


      • #4
        Re: Replacing an Old Win2k DC with win2k3 Server

        You've not posted the subnet mask but I assume looking at the IPs that the servers are in the same AD site? Make sure that your NICs are registering their IPs in DNS and that there are no rogue entries for either server.

        It's well worth downloading and installing the Server 2003 Support tools. Replmon in particular is a great tool for troubleshooting AD replication issues.
        BSc, MCSA: Server 2008, MCSE, MCSA: Messaging, MCTS
        sigpic
        Cruachan's Blog

        Comment


        • #5
          Re: Replacing an Old Win2k DC with win2k3 Server

          Whats the status of the FRS Log on the OLD DC.

          Restart the FRS Service on OLD DC.
          Check FRS Log on the OLD DC and provide us with events you get after restarting the service.

          Regards,
          Pledge Technologies.
          Best Regards,
          Pledge Technologies

          Comment


          • #6
            Re: Replacing an Old Win2k DC with win2k3 Server

            i tried restarting the FRS , and then went to the event viewer but theres not a single entry there
            not even on app / system .. etc...
            and the event log srvice is started ... makes you wonder ...

            the ip : of the old :
            10.10.10.200
            255.255.255.0
            10.10.10.100

            10.10.10.200


            new server :
            10.10.10.220
            255.255.255.0
            10.10.10.100

            10.10.10.220


            is that ok ?
            how do i make sure that nics are registering them selfs in dns ?
            isn't it enough to just ping on both end (dcs) and see that you're getting a proper reply by the server name ?


            I installed the support tools but I'm not really sure how to go about them .

            Thanks for any help.

            Comment


            • #7
              Re: Replacing an Old Win2k DC with win2k3 Server

              Could you please post the DCDIAG /V report for the old and the new DC..!! Also please reconfirm that you did not find any New Event in File Replication Log, after restarting the FRS Service.!!
              Best Regards,
              Pledge Technologies

              Comment


              • #8
                Re: Replacing an Old Win2k DC with win2k3 Server

                it's going bad by the minute now .
                i restarted the new d/c
                and now when i'm trying to connect i'm getting an error telling me the specified domain either does not exist or could not be contacted...
                how is that possible when you're trying to login into your own dc.

                Comment


                • #9
                  Re: Replacing an Old Win2k DC with win2k3 Server

                  heres DCDIAG
                  of the old dc
                  where i'm logged in


                  Domain Controller Diagnosis

                  Performing initial setup:
                  * Verifying that the local machine DynServer, is a DC.
                  * Connecting to directory service on server DynServer.
                  * Collecting site info.
                  * Identifying all servers.
                  * Found 2 DC(s). Testing 1 of them.
                  Done gathering initial info.

                  Doing initial required tests

                  Testing server: Default-First-Site-Name\DYNSERVER
                  Starting test: Connectivity
                  * Active Directory LDAP Services Check
                  * Active Directory RPC Services Check
                  ......................... DYNSERVER passed test Connectivity

                  Doing primary tests

                  Testing server: Default-First-Site-Name\DYNSERVER
                  Starting test: Replications
                  * Replications Check
                  ......................... DYNSERVER passed test Replications
                  Test omitted by user request: Topology
                  Test omitted by user request: CutoffServers
                  Starting test: NCSecDesc
                  * Security Permissions Check for
                  CN=Schema,CN=Configuration,DC=DynNetwork,DC=local
                  * Security Permissions Check for
                  CN=Configuration,DC=DynNetwork,DC=local
                  * Security Permissions Check for
                  DC=DynNetwork,DC=local
                  ......................... DYNSERVER passed test NCSecDesc
                  Starting test: NetLogons
                  * Network Logons Privileges Check
                  ......................... DYNSERVER passed test NetLogons
                  Starting test: Advertising
                  The DC DYNSERVER is advertising itself as a DC and having a DS.
                  The DC DYNSERVER is advertising as an LDAP server
                  The DC DYNSERVER is advertising as having a writeable directory
                  The DC DYNSERVER is advertising as a Key Distribution Center
                  The DC DYNSERVER is advertising as a time server
                  ......................... DYNSERVER passed test Advertising
                  Starting test: KnowsOfRoleHolders
                  Role Schema Owner = CN=NTDS Settings,CN=DYN-DC,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=DynNetwork,DC=lo cal
                  Role Domain Owner = CN=NTDS Settings,CN=DYN-DC,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=DynNetwork,DC=lo cal
                  Role PDC Owner = CN=NTDS Settings,CN=DYN-DC,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=DynNetwork,DC=lo cal
                  Role Rid Owner = CN=NTDS Settings,CN=DYN-DC,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=DynNetwork,DC=lo cal
                  Role Infrastructure Update Owner = CN=NTDS Settings,CN=DYN-DC,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=DynNetwork,DC=lo cal
                  ......................... DYNSERVER passed test KnowsOfRoleHolders
                  Starting test: RidManager
                  * Available RID Pool for the Domain is 3607 to 1073741823
                  * dyn-dc.DynNetwork.local is the RID Master
                  * DsBind with RID Master was successful
                  * rIDAllocationPool is 1607 to 2106
                  * rIDNextRID: 1384
                  * rIDPreviousAllocationPool is 1107 to 1606
                  ......................... DYNSERVER passed test RidManager
                  Starting test: MachineAccount
                  * SPN found :LDAP/DynServer.DynNetwork.local/DynNetwork.local
                  * SPN found :LDAP/DynServer.DynNetwork.local
                  * SPN found :LDAP/DYNSERVER
                  * SPN found :LDAP/DynServer.DynNetwork.local/DYNNETWORK
                  * SPN found :LDAP/85dcec10-6c27-4c34-9211-0fce1b3260e2._msdcs.DynNetwork.local
                  * SPN found :E3514235-4B06-11D1-AB04-00C04FC2DCD2/85dcec10-6c27-4c34-9211-0fce1b3260e2/DynNetwork.local
                  * SPN found :HOST/DynServer.DynNetwork.local/DynNetwork.local
                  * SPN found :HOST/DynServer.DynNetwork.local
                  * SPN found :HOST/DYNSERVER
                  * SPN found :HOST/DynServer.DynNetwork.local/DYNNETWORK
                  * SPN found :GC/DynServer.DynNetwork.local/DynNetwork.local
                  ......................... DYNSERVER passed test MachineAccount
                  Starting test: Services
                  * Checking Service: Dnscache
                  * Checking Service: NtFrs
                  * Checking Service: IsmServ
                  * Checking Service: kdc
                  * Checking Service: SamSs
                  * Checking Service: LanmanServer
                  * Checking Service: LanmanWorkstation
                  * Checking Service: RpcSs
                  * Checking Service: RPCLOCATOR
                  * Checking Service: w32time
                  * Checking Service: TrkWks
                  * Checking Service: TrkSvr
                  * Checking Service: NETLOGON
                  * Checking Service: Dnscache
                  Could not open IISADMIN Service on [DYNSERVER]:failed with 1060: Win32 Error 1060
                  * Checking Service: NtFrs
                  Could not open SMTPSVC Service on [DYNSERVER]:failed with 1060: Win32 Error 1060
                  ......................... DYNSERVER failed test Services
                  Test omitted by user request: OutboundSecureChannels
                  Starting test: ObjectsReplicated
                  DYNSERVER is in domain DC=DynNetwork,DC=local
                  Checking for CN=DYNSERVER,OU=Domain Controllers,DC=DynNetwork,DC=local in domain DC=DynNetwork,DC=local on 1 servers
                  Object is up-to-date on all servers.
                  Checking for CN=NTDS Settings,CN=DYNSERVER,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=DynNetwork,DC=lo cal in domain CN=Configuration,DC=DynNetwork,DC=local on 1 servers
                  Object is up-to-date on all servers.
                  ......................... DYNSERVER passed test ObjectsReplicated
                  Starting test: frssysvol
                  * The File Replication Service Event log test
                  Error: No record of File Replication System, SYSVOL started.
                  The Active Directory may be prevented from starting.
                  ......................... DYNSERVER passed test frssysvol
                  Starting test: kccevent
                  * The KCC Event log test
                  Found no KCC errors in Directory Service Event log in the last 15 minutes.
                  ......................... DYNSERVER passed test kccevent
                  Starting test: systemlog
                  * The System Event log test
                  Found no errors in System Event log in the last 60 minutes.
                  ......................... DYNSERVER passed test systemlog

                  Running enterprise tests on : DynNetwork.local
                  Starting test: Intersite
                  Skipping site Default-First-Site-Name, this site is outside the scope

                  provided by the command line arguments provided.
                  ......................... DynNetwork.local passed test Intersite
                  Starting test: FsmoCheck
                  Warning: DcGetDcName(GC_SERVER_REQUIRED) call failed, error 1355
                  A Global Catalog Server could not be located - All GC's are down.
                  PDC Name: \\dyn-dc.DynNetwork.local
                  Locator Flags: 0xe00003fd
                  Time Server Name: \\DynServer.DynNetwork.local
                  Locator Flags: 0xe00001f8
                  Preferred Time Server Name: \\DynServer.DynNetwork.local
                  Locator Flags: 0xe00001f8
                  KDC Name: \\DynServer.DynNetwork.local
                  Locator Flags: 0xe00001f8
                  ......................... DynNetwork.local failed test FsmoCheck

                  Comment


                  • #10
                    Re: Replacing an Old Win2k DC with win2k3 Server

                    after rechecking Global Catalog on the old DC i can login to the new DC
                    i guess FSMO wasn't replicated and that is why i can't tick that off.

                    Comment


                    • #11
                      Re: Replacing an Old Win2k DC with win2k3 Server

                      new dc dcdiag /v
                      part 1 :

                      Domain Controller Diagnosis

                      Performing initial setup:
                      * Verifying that the local machine dyn-dc, is a DC.
                      * Connecting to directory service on server dyn-dc.
                      * Collecting site info.
                      * Identifying all servers.
                      * Identifying all NC cross-refs.
                      * Found 2 DC(s). Testing 1 of them.
                      Done gathering initial info.

                      Doing initial required tests

                      Testing server: Default-First-Site-Name\DYN-DC
                      Starting test: Connectivity
                      * Active Directory LDAP Services Check
                      * Active Directory RPC Services Check
                      ......................... DYN-DC passed test Connectivity

                      Doing primary tests

                      Testing server: Default-First-Site-Name\DYN-DC
                      Starting test: Replications
                      * Replications Check
                      * Replication Latency Check
                      CN=Schema,CN=Configuration,DC=DynNetwork,DC=local
                      Latency information for 2 entries in the vector were ignored.
                      2 were retired Invocations. 0 were either: read-only replicas and are not verifiably latent, or dc's no longer replicating this nc. 0 had no latency information (Win2K DC).
                      CN=Configuration,DC=DynNetwork,DC=local
                      Latency information for 2 entries in the vector were ignored.
                      2 were retired Invocations. 0 were either: read-only replicas and are not verifiably latent, or dc's no longer replicating this nc. 0 had no latency information (Win2K DC).
                      DC=DynNetwork,DC=local
                      Latency information for 2 entries in the vector were ignored.
                      2 were retired Invocations. 0 were either: read-only replicas and are not verifiably latent, or dc's no longer replicating this nc. 0 had no latency information (Win2K DC).
                      * Replication Site Latency Check
                      ......................... DYN-DC passed test Replications
                      Test omitted by user request: Topology
                      Test omitted by user request: CutoffServers
                      Starting test: NCSecDesc
                      * Security Permissions check for all NC's on DC DYN-DC.
                      * Security Permissions Check for
                      DC=ForestDnsZones,DC=DynNetwork,DC=local
                      (NDNC,Version 2)
                      * Security Permissions Check for
                      DC=DomainDnsZones,DC=DynNetwork,DC=local
                      (NDNC,Version 2)
                      * Security Permissions Check for
                      CN=Schema,CN=Configuration,DC=DynNetwork,DC=local
                      (Schema,Version 2)
                      * Security Permissions Check for
                      CN=Configuration,DC=DynNetwork,DC=local
                      (Configuration,Version 2)
                      * Security Permissions Check for
                      DC=DynNetwork,DC=local
                      (Domain,Version 2)
                      ......................... DYN-DC passed test NCSecDesc
                      Starting test: NetLogons
                      * Network Logons Privileges Check
                      Unable to connect to the NETLOGON share! (\\DYN-DC\netlogon)
                      [DYN-DC] An net use or LsaPolicy operation failed with error 1203, Win32 Error 1203.
                      ......................... DYN-DC failed test NetLogons
                      Starting test: Advertising
                      Warning: DsGetDcName returned information for \\DynServer.DynNetwork.local, when we were trying to reach DYN-DC.
                      Server is not responding or is not considered suitable.
                      The DC DYN-DC is advertising itself as a DC and having a DS.
                      The DC DYN-DC is advertising as an LDAP server
                      The DC DYN-DC is advertising as having a writeable directory
                      The DC DYN-DC is advertising as a Key Distribution Center
                      The DC DYN-DC is advertising as a time server
                      Warning: DYN-DC is not advertising as a global catalog.
                      Check that server finished GC promotion.
                      Check the event log on server that enough source replicas for the GC are available.
                      Last edited by nadi; 2nd April 2010, 00:46.

                      Comment


                      • #12
                        Re: Replacing an Old Win2k DC with win2k3 Server

                        the rest :

                        ......................... DYN-DC failed test Advertising
                        Starting test: KnowsOfRoleHolders
                        Role Schema Owner = CN=NTDS Settings,CN=DYN-DC,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=DynNetwork,DC=lo cal
                        Role Domain Owner = CN=NTDS Settings,CN=DYN-DC,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=DynNetwork,DC=lo cal
                        Role PDC Owner = CN=NTDS Settings,CN=DYN-DC,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=DynNetwork,DC=lo cal
                        Role Rid Owner = CN=NTDS Settings,CN=DYN-DC,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=DynNetwork,DC=lo cal
                        Role Infrastructure Update Owner = CN=NTDS Settings,CN=DYN-DC,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=DynNetwork,DC=lo cal
                        ......................... DYN-DC passed test KnowsOfRoleHolders
                        Starting test: RidManager
                        * Available RID Pool for the Domain is 3607 to 1073741823
                        * dyn-dc.DynNetwork.local is the RID Master
                        * DsBind with RID Master was successful
                        * rIDAllocationPool is 3107 to 3606
                        * rIDPreviousAllocationPool is 3107 to 3606
                        * rIDNextRID: 3107
                        ......................... DYN-DC passed test RidManager
                        Starting test: MachineAccount
                        Checking machine account for DC DYN-DC on DC DYN-DC.
                        * SPN found :LDAP/dyn-dc.DynNetwork.local/DynNetwork.local
                        * SPN found :LDAP/dyn-dc.DynNetwork.local
                        * SPN found :LDAP/DYN-DC
                        * SPN found :LDAP/dyn-dc.DynNetwork.local/DYNNETWORK
                        * SPN found :LDAP/8081c88c-c98a-431a-a1ea-c033e0bf69ce._msdcs.DynNetwork.local
                        * SPN found :E3514235-4B06-11D1-AB04-00C04FC2DCD2/8081c88c-c98a-431a-a1ea-c033e0bf69ce/DynNetwork.local
                        * SPN found :HOST/dyn-dc.DynNetwork.local/DynNetwork.local
                        * SPN found :HOST/dyn-dc.DynNetwork.local
                        * SPN found :HOST/DYN-DC
                        * SPN found :HOST/dyn-dc.DynNetwork.local/DYNNETWORK
                        * SPN found :GC/dyn-dc.DynNetwork.local/DynNetwork.local
                        ......................... DYN-DC passed test MachineAccount
                        Starting test: Services
                        * Checking Service: Dnscache
                        * Checking Service: NtFrs
                        * Checking Service: IsmServ
                        * Checking Service: kdc
                        * Checking Service: SamSs
                        * Checking Service: LanmanServer
                        * Checking Service: LanmanWorkstation
                        * Checking Service: RpcSs
                        * Checking Service: w32time
                        * Checking Service: NETLOGON
                        ......................... DYN-DC passed test Services
                        Test omitted by user request: OutboundSecureChannels
                        Starting test: ObjectsReplicated
                        DYN-DC is in domain DC=DynNetwork,DC=local
                        Checking for CN=DYN-DC,OU=Domain Controllers,DC=DynNetwork,DC=local in domain DC=DynNetwork,DC=local on 1 servers
                        Object is up-to-date on all servers.
                        Checking for CN=NTDS Settings,CN=DYN-DC,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=DynNetwork,DC=lo cal in domain CN=Configuration,DC=DynNetwork,DC=local on 1 servers
                        Object is up-to-date on all servers.
                        ......................... DYN-DC passed test ObjectsReplicated
                        Starting test: frssysvol
                        * The File Replication Service SYSVOL ready test
                        The registry lookup failed to determine the state of the SYSVOL. The

                        error returned was 0 (Win32 Error 0). Check the FRS event log to see

                        if the SYSVOL has successfully been shared.
                        ......................... DYN-DC passed test frssysvol
                        Starting test: frsevent
                        * The File Replication Service Event log test
                        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.
                        An Warning Event occured. EventID: 0x800034FE
                        Time Generated: 04/02/2010 02:18:56
                        (Event String could not be retrieved)
                        An Warning Event occured. EventID: 0x800034C4
                        Time Generated: 04/02/2010 02:24:48
                        (Event String could not be retrieved)
                        An Warning Event occured. EventID: 0x800034C4
                        Time Generated: 04/02/2010 02:32:24
                        (Event String could not be retrieved)
                        ......................... DYN-DC failed test frsevent
                        Starting test: kccevent
                        * The KCC Event log test
                        An Error Event occured. EventID: 0xC0000466
                        Time Generated: 04/02/2010 02:33:39
                        (Event String could not be retrieved)
                        ......................... DYN-DC failed test kccevent
                        Starting test: systemlog
                        * The System Event log test
                        An Error Event occured. EventID: 0x00000457
                        Time Generated: 04/02/2010 01:48:06
                        (Event String could not be retrieved)
                        An Error Event occured. EventID: 0x00000457
                        Time Generated: 04/02/2010 01:48:06
                        (Event String could not be retrieved)
                        An Error Event occured. EventID: 0x00000457
                        Time Generated: 04/02/2010 01:48:06
                        (Event String could not be retrieved)
                        An Error Event occured. EventID: 0x00000457
                        Time Generated: 04/02/2010 02:37:23
                        (Event String could not be retrieved)
                        An Error Event occured. EventID: 0x00000457
                        Time Generated: 04/02/2010 02:37:23
                        (Event String could not be retrieved)
                        An Error Event occured. EventID: 0x00000457
                        Time Generated: 04/02/2010 02:37:24
                        (Event String could not be retrieved)
                        ......................... DYN-DC failed test systemlog
                        Test omitted by user request: VerifyReplicas
                        Starting test: VerifyReferences
                        The system object reference (serverReference)

                        CN=DYN-DC,OU=Domain Controllers,DC=DynNetwork,DC=local and backlink on

                        CN=DYN-DC,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=DynNetwork,DC=lo cal

                        are correct.
                        The system object reference (frsComputerReferenceBL)

                        CN=DYN-DC,CN=Domain System Volume (SYSVOL share),CN=File Replication Service,CN=System,DC=DynNetwork,DC=local

                        and backlink on CN=DYN-DC,OU=Domain Controllers,DC=DynNetwork,DC=local

                        are correct.
                        The system object reference (serverReferenceBL)

                        CN=DYN-DC,CN=Domain System Volume (SYSVOL share),CN=File Replication Service,CN=System,DC=DynNetwork,DC=local

                        and backlink on

                        CN=NTDS Settings,CN=DYN-DC,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=DynNetwork,DC=lo cal

                        are correct.
                        ......................... DYN-DC passed test VerifyReferences
                        Test omitted by user request: VerifyEnterpriseReferences
                        Test omitted by user request: CheckSecurityError

                        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 : DynNetwork
                        Starting test: CrossRefValidation
                        ......................... DynNetwork passed test CrossRefValidation
                        Starting test: CheckSDRefDom
                        ......................... DynNetwork passed test CheckSDRefDom

                        Running enterprise tests on : DynNetwork.local
                        Starting test: Intersite
                        Skipping site Default-First-Site-Name, this site is outside the scope

                        provided by the command line arguments provided.
                        ......................... DynNetwork.local passed test Intersite
                        Starting test: FsmoCheck
                        Warning: DcGetDcName(GC_SERVER_REQUIRED) call failed, error 1355
                        A Global Catalog Server could not be located - All GC's are down.
                        PDC Name: \\dyn-dc.DynNetwork.local
                        Locator Flags: 0xe00003fd
                        Time Server Name: \\DynServer.DynNetwork.local
                        Locator Flags: 0xe00001fc
                        Preferred Time Server Name: \\DynServer.DynNetwork.local
                        Locator Flags: 0xe00001fc
                        KDC Name: \\DynServer.DynNetwork.local
                        Locator Flags: 0xe00001fc
                        ......................... DynNetwork.local failed test FsmoCheck
                        Test omitted by user request: DNS
                        Test omitted by user request: DNS

                        Comment


                        • #13
                          Re: Replacing an Old Win2k DC with win2k3 Server

                          Seems like you figured it out after looking on the DCDAIG of the Win2K DC.

                          Coming back to the point, as DCDAIG of old domain controller shows no events on sysvol.. could you please confirm that you have restarted the FRS Service, but you did not see any New Events.

                          Step 1. Open Event Viewer, check FRS Log. Note the last event date/time if there is any and exit.
                          Step 2. Open Command Prompt, type the following command.

                          net stop ntfrs

                          net start ntfrs

                          Step 3. Open Event Viewer and check for New Events in FRS Log. (No need to look in any other log.)

                          Step 4. You should atleast get Event ID: 13501, 13502, which confirms that the service has been restarted. Let me know if there is any other event being generated after restarting the service.

                          Step 5. Check the following location:

                          "C:\Windows\Sysvol\Domain" and tell me do you see the "Policies" and "Scripts" folder in there or not. If not, is there any NTFRS_PreExisting folder present???


                          Reply back with the results.


                          Regards,
                          Pledge Technologies.
                          Best Regards,
                          Pledge Technologies

                          Comment


                          • #14
                            Re: Replacing an Old Win2k DC with win2k3 Server

                            As per the issue described by you, and looking at the reports, the OLD DC is not replicating the SYSVOL and NETLOGON share to the new DC, which is why the issue is occuring. Please go through the previous post, and let me know the outcome...


                            Best Regards,
                            Pledge Technologies.
                            Best Regards,
                            Pledge Technologies

                            Comment


                            • #15
                              Re: Replacing an Old Win2k DC with win2k3 Server

                              C:\PROGRA~1\Support Tools>net stop ntfrs
                              The File Replication Service service is stopping....
                              The File Replication Service service was stopped successfully.


                              C:\PROGRA~1\Support Tools>net start ntfrs
                              The File Replication Service service is starting.
                              The File Replication Service service was started successfully.

                              Like I said before ,
                              on the old DC i see 0 events everywhere on the event viewer no events at all
                              and the logs isn't full. i'm not sure why.
                              maybe i need to reconfigure the event log somehow ?

                              D:\WINNT\SYSVOL
                              exists

                              if i go to
                              \\dynserver
                              the SYSVOL
                              share is also there
                              and theres the policies,etc ,etc,

                              Thanks .

                              Comment

                              Working...
                              X