Solved

File replication doesn't work after promoting a server to dc

Posted on 2010-11-11
7
1,171 Views
Last Modified: 2012-05-10
I decommissioned a server today and promoted a different one. The server Did not have any fsmo roles. The new server is 2008 and I have 3 other dc's in the domain. I keep getting a warning on the newly promoted server saying it could not communicate with another specified dc in my domain and frs will not allow the new dc to operate as a dc until this happeneds. The new dc does not have the sysvol or netlogon shares. The event log told me to check the connection between the servers. I can ping all of the servers and connect to file shares on the other servers locally, but get a no network specified error when trying to connect to a file share on a dc in another site, but I can ping it by ip and fqdn. I have been messing with this all day and have done everything I know to do
0
Comment
Question by:j_crow1
  • 3
  • 2
  • 2
7 Comments
 
LVL 10

Assisted Solution

by:George Khairallah
George Khairallah earned 250 total points
ID: 34117416
Can you run netdiag /v and dcdiag /v on that server?
either post anything that is showing up as failure, or the whole log.
Usually, NTFRS not working could be due to DNS not working properly.

Also, what is the event ID you are getting in the NTFRS log?
0
 
LVL 59

Assisted Solution

by:Darius Ghassem
Darius Ghassem earned 250 total points
ID: 34117467
Remove any AV or firewall you have running on both DCs. SEP has been causing these types of issues

Make sure the new DC is pointing to an existing DC for DNS.
Disable all NICs except for one NIC.

Demote the new server
Run a metadata cleanup on a existing DC to make sure you have removed any lingering objects http://www.petri.co.il/delete_failed_dcs_from_ad.htm

0
 
LVL 59

Assisted Solution

by:Darius Ghassem
Darius Ghassem earned 250 total points
ID: 34117469
Once you have done the above repromote the servers again
0
Ransomware-A Revenue Bonanza for Service Providers

Ransomware – malware that gets on your customers’ computers, encrypts their data, and extorts a hefty ransom for the decryption keys – is a surging new threat.  The purpose of this eBook is to educate the reader about ransomware attacks.

 

Accepted Solution

by:
j_crow1 earned 0 total points
ID: 34117482

Directory Server Diagnosis


Performing initial setup:

   Trying to find home server...

   * Verifying that the local machine NEWDC, is a Directory Server.
   Home Server = NEWDC

   * Connecting to directory service on server NEWDC.

   * Identified AD Forest.
   Collecting AD specific global data
   * Collecting site info.

   Calling ldap_search_init_page(hld,CN=Sites,CN=Configuration,DC=DOMAIN,DC=com,LDAP_SCOPE_SUBTREE,(objectCategory=ntDSSiteSettings),.......
   The previous call succeeded
   Iterating through the sites
   Looking at base site object: CN=NTDS Site Settings,CN=Dallas,CN=Sites,CN=Configuration,DC=DOMAIN,DC=com
   Getting ISTG and options for the site
   Looking at base site object: CN=NTDS Site Settings,CN=Houston,CN=Sites,CN=Configuration,DC=DOMAIN,DC=com
   Getting ISTG and options for the site
   * Identifying all servers.

   Calling ldap_search_init_page(hld,CN=Sites,CN=Configuration,DC=DOMAIN,DC=com,LDAP_SCOPE_SUBTREE,(objectClass=ntDSDsa),.......
   The previous call succeeded....
   The previous call succeeded
   Iterating through the list of servers
   Getting information for the server CN=NTDS Settings,CN=MAINDC,CN=Servers,CN=Houston,CN=Sites,CN=Configuration,DC=DOMAIN,DC=com
   objectGuid obtained
   InvocationID obtained
   dnsHostname obtained
   site info obtained
   All the info for the server collected
   Getting information for the server CN=NTDS Settings,CN=SRG-DAL-FS-01,CN=Servers,CN=Dallas,CN=Sites,CN=Configuration,DC=DOMAIN,DC=com
   objectGuid obtained
   InvocationID obtained
   dnsHostname obtained
   site info obtained
   All the info for the server collected
   Getting information for the server CN=NTDS Settings,CN=SRG-DAL-MSX-02,CN=Servers,CN=Dallas,CN=Sites,CN=Configuration,DC=DOMAIN,DC=com
   objectGuid obtained
   InvocationID obtained
   dnsHostname obtained
   site info obtained
   All the info for the server collected
   Getting information for the server CN=NTDS Settings,CN=SRG-DAL-FS-02,CN=Servers,CN=Dallas,CN=Sites,CN=Configuration,DC=DOMAIN,DC=com
   objectGuid obtained
   InvocationID obtained
   dnsHostname obtained
   site info obtained
   All the info for the server collected
   Getting information for the server CN=NTDS Settings,CN=NEWDC,CN=Servers,CN=Houston,CN=Sites,CN=Configuration,DC=DOMAIN,DC=com
   objectGuid obtained
   InvocationID obtained
   dnsHostname obtained
   site info obtained
   All the info for the server collected
   * Identifying all NC cross-refs.

   * Found 5 DC(s). Testing 1 of them.

   Done gathering initial info.


Doing initial required tests

   
   Testing server: Houston\NEWDC

      Starting test: Connectivity

         * Active Directory LDAP Services Check
         Determining IP4 connectivity
         * Active Directory RPC Services Check
         ......................... NEWDC passed test Connectivity



Doing primary tests

   
   Testing server: Houston\NEWDC

      Starting test: Advertising

         Warning: DsGetDcName returned information for

         \\MAINDC.DOMAIN.com, when we were trying to reach NEWDC.

         SERVER IS NOT RESPONDING or IS NOT CONSIDERED SUITABLE.

         ......................... NEWDC failed test Advertising

      Test omitted by user request: CheckSecurityError

      Test omitted by user request: CutoffServers

      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.
         A warning event occurred.  EventID: 0x800034FD

            Time Generated: 11/11/2010   10:26:15

            Event String:

            File Replication Service is initializing the system volume with data from another domain controller. Computer NEWDC cannot become a domain controller until this process is complete. The system volume will then be shared as SYSVOL.

             

            To check for the SYSVOL share, at the command prompt, type:

            net share

             

            When File Replication Service completes the initialization process, the SYSVOL share will appear.

             

            The initialization of the system volume can take some time. The time is dependent on the amount of data in the system volume, the availability of other domain controllers, and the replication interval between domain controllers.

         A warning event occurred.  EventID: 0x800034C4

            Time Generated: 11/11/2010   10:35:58

            Event String:

            The File Replication Service is having trouble enabling replication from MAINDC to NEWDC for c:\windows\sysvol\domain using the DNS name MAINDC.DOMAIN.com. FRS will keep retrying.

             Following are some of the reasons you would see this warning.

             

             [1] FRS can not correctly resolve the DNS name MAINDC.DOMAIN.com from this computer.

             [2] FRS is not running on MAINDC.DOMAIN.com.

             [3] The topology information in the Active Directory Domain Services 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.

         A warning event occurred.  EventID: 0x800034FD

            Time Generated: 11/11/2010   10:39:45

            Event String:

            File Replication Service is initializing the system volume with data from another domain controller. Computer NEWDC cannot become a domain controller until this process is complete. The system volume will then be shared as SYSVOL.

             

            To check for the SYSVOL share, at the command prompt, type:

            net share

             

            When File Replication Service completes the initialization process, the SYSVOL share will appear.

             

            The initialization of the system volume can take some time. The time is dependent on the amount of data in the system volume, the availability of other domain controllers, and the replication interval between domain controllers.

         A warning event occurred.  EventID: 0x800034C4

            Time Generated: 11/11/2010   10:41:29

            Event String:

            The File Replication Service is having trouble enabling replication from MAINDC to NEWDC for c:\windows\sysvol\domain using the DNS name MAINDC.DOMAIN.com. FRS will keep retrying.

             Following are some of the reasons you would see this warning.

             

             [1] FRS can not correctly resolve the DNS name MAINDC.DOMAIN.com from this computer.

             [2] FRS is not running on MAINDC.DOMAIN.com.

             [3] The topology information in the Active Directory Domain Services 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.

         A warning event occurred.  EventID: 0x800034FE

            Time Generated: 11/11/2010   16:21:01

            Event String:

            File Replication Service is scanning the data in the system volume. Computer NEWDC cannot become a domain controller until this process is complete. The system volume will then be shared as SYSVOL.

             

            To check for the SYSVOL share, at the command prompt, type:

            net share

             

            When File Replication Service completes the scanning process, the SYSVOL share will appear.

             

            The initialization of the system volume can take some time. The time is dependent on the amount of data in the system volume.

         A warning event occurred.  EventID: 0x800034C4

            Time Generated: 11/11/2010   16:22:41

            Event String:

            The File Replication Service is having trouble enabling replication from MAINDC to NEWDC for c:\windows\sysvol\domain using the DNS name MAINDC.DOMAIN.com. FRS will keep retrying.

             Following are some of the reasons you would see this warning.

             

             [1] FRS can not correctly resolve the DNS name MAINDC.DOMAIN.com from this computer.

             [2] FRS is not running on MAINDC.DOMAIN.com.

             [3] The topology information in the Active Directory Domain Services 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.

         A warning event occurred.  EventID: 0x800034FD

            Time Generated: 11/11/2010   18:04:44

            Event String:

            File Replication Service is initializing the system volume with data from another domain controller. Computer NEWDC cannot become a domain controller until this process is complete. The system volume will then be shared as SYSVOL.

             

            To check for the SYSVOL share, at the command prompt, type:

            net share

             

            When File Replication Service completes the initialization process, the SYSVOL share will appear.

             

            The initialization of the system volume can take some time. The time is dependent on the amount of data in the system volume, the availability of other domain controllers, and the replication interval between domain controllers.

         A warning event occurred.  EventID: 0x800034C4

            Time Generated: 11/11/2010   18:06:27

            Event String:

            The File Replication Service is having trouble enabling replication from MAINDC to NEWDC for c:\windows\sysvol\domain using the DNS name MAINDC.DOMAIN.com. FRS will keep retrying.

             Following are some of the reasons you would see this warning.

             

             [1] FRS can not correctly resolve the DNS name MAINDC.DOMAIN.com from this computer.

             [2] FRS is not running on MAINDC.DOMAIN.com.

             [3] The topology information in the Active Directory Domain Services 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.

         A warning event occurred.  EventID: 0x800034FD

            Time Generated: 11/11/2010   18:30:47

            Event String:

            File Replication Service is initializing the system volume with data from another domain controller. Computer NEWDC cannot become a domain controller until this process is complete. The system volume will then be shared as SYSVOL.

             

            To check for the SYSVOL share, at the command prompt, type:

            net share

             

            When File Replication Service completes the initialization process, the SYSVOL share will appear.

             

            The initialization of the system volume can take some time. The time is dependent on the amount of data in the system volume, the availability of other domain controllers, and the replication interval between domain controllers.

         A warning event occurred.  EventID: 0x800034C4

            Time Generated: 11/11/2010   18:32:28

            Event String:

            The File Replication Service is having trouble enabling replication from MAINDC to NEWDC for c:\windows\sysvol\domain using the DNS name MAINDC.DOMAIN.com. FRS will keep retrying.

             Following are some of the reasons you would see this warning.

             

             [1] FRS can not correctly resolve the DNS name MAINDC.DOMAIN.com from this computer.

             [2] FRS is not running on MAINDC.DOMAIN.com.

             [3] The topology information in the Active Directory Domain Services 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.

         A warning event occurred.  EventID: 0x800034FD

            Time Generated: 11/11/2010   18:48:08

            Event String:

            File Replication Service is initializing the system volume with data from another domain controller. Computer NEWDC cannot become a domain controller until this process is complete. The system volume will then be shared as SYSVOL.

             

            To check for the SYSVOL share, at the command prompt, type:

            net share

             

            When File Replication Service completes the initialization process, the SYSVOL share will appear.

             

            The initialization of the system volume can take some time. The time is dependent on the amount of data in the system volume, the availability of other domain controllers, and the replication interval between domain controllers.

         A warning event occurred.  EventID: 0x800034C4

            Time Generated: 11/11/2010   18:49:48

            Event String:

            The File Replication Service is having trouble enabling replication from MAINDC to NEWDC for c:\windows\sysvol\domain using the DNS name MAINDC.DOMAIN.com. FRS will keep retrying.

             Following are some of the reasons you would see this warning.

             

             [1] FRS can not correctly resolve the DNS name MAINDC.DOMAIN.com from this computer.

             [2] FRS is not running on MAINDC.DOMAIN.com.

             [3] The topology information in the Active Directory Domain Services 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.

         A warning event occurred.  EventID: 0x800034FD

            Time Generated: 11/11/2010   19:00:02

            Event String:

            File Replication Service is initializing the system volume with data from another domain controller. Computer NEWDC cannot become a domain controller until this process is complete. The system volume will then be shared as SYSVOL.

             

            To check for the SYSVOL share, at the command prompt, type:

            net share

             

            When File Replication Service completes the initialization process, the SYSVOL share will appear.

             

            The initialization of the system volume can take some time. The time is dependent on the amount of data in the system volume, the availability of other domain controllers, and the replication interval between domain controllers.

         A warning event occurred.  EventID: 0x800034C4

            Time Generated: 11/11/2010   19:01:46

            Event String:

            The File Replication Service is having trouble enabling replication from MAINDC to NEWDC for c:\windows\sysvol\domain using the DNS name MAINDC.DOMAIN.com. FRS will keep retrying.

             Following are some of the reasons you would see this warning.

             

             [1] FRS can not correctly resolve the DNS name MAINDC.DOMAIN.com from this computer.

             [2] FRS is not running on MAINDC.DOMAIN.com.

             [3] The topology information in the Active Directory Domain Services 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.

         ......................... NEWDC passed test FrsEvent

      Starting test: DFSREvent

         The DFS Replication Event Log.
         Skip the test because the server is running FRS.

         ......................... NEWDC passed test DFSREvent

      Starting test: SysVolCheck

         * The File Replication Service SYSVOL ready test
         The registry lookup failed to determine the state of the SYSVOL.  The

         error returned  was 0x0 "The operation completed successfully.".

         Check the FRS event log to see if the SYSVOL has successfully been

         shared.
         ......................... NEWDC passed test SysVolCheck

      Starting test: KccEvent

         * The KCC Event log test
         Found no KCC errors in "Directory Service" Event log in the last 15 minutes.
         ......................... NEWDC passed test KccEvent

      Starting test: KnowsOfRoleHolders

         Role Schema Owner = CN=NTDS Settings,CN=MAINDC,CN=Servers,CN=Houston,CN=Sites,CN=Configuration,DC=DOMAIN,DC=com
         Role Domain Owner = CN=NTDS Settings,CN=MAINDC,CN=Servers,CN=Houston,CN=Sites,CN=Configuration,DC=DOMAIN,DC=com
         Role PDC Owner = CN=NTDS Settings,CN=MAINDC,CN=Servers,CN=Houston,CN=Sites,CN=Configuration,DC=DOMAIN,DC=com
         Role Rid Owner = CN=NTDS Settings,CN=MAINDC,CN=Servers,CN=Houston,CN=Sites,CN=Configuration,DC=DOMAIN,DC=com
         Role Infrastructure Update Owner = CN=NTDS Settings,CN=MAINDC,CN=Servers,CN=Houston,CN=Sites,CN=Configuration,DC=DOMAIN,DC=com
         ......................... NEWDC passed test KnowsOfRoleHolders

      Starting test: MachineAccount

         Checking machine account for DC NEWDC on DC NEWDC.
         * The current DC is not in the domain controller's OU

         * SPN found :LDAP/NEWDC.DOMAIN.com/DOMAIN.com
         * SPN found :LDAP/NEWDC.DOMAIN.com
         * SPN found :LDAP/NEWDC
         * SPN found :LDAP/NEWDC.DOMAIN.com/DOMAIN
         * SPN found :LDAP/7e0b1006-36d5-4be8-bd78-a3ebf5388878._msdcs.DOMAIN.com
         * SPN found :E3514235-4B06-11D1-AB04-00C04FC2DCD2/7e0b1006-36d5-4be8-bd78-a3ebf5388878/DOMAIN.com
         * SPN found :HOST/NEWDC.DOMAIN.com/DOMAIN.com
         * SPN found :HOST/NEWDC.DOMAIN.com
         * SPN found :HOST/NEWDC
         * SPN found :HOST/NEWDC.DOMAIN.com/DOMAIN
         * SPN found :GC/NEWDC.DOMAIN.com/DOMAIN.com
         ......................... NEWDC failed test MachineAccount

      Starting test: NCSecDesc

         * Security Permissions check for all NC's on DC NEWDC.
         The forest is not ready for RODC. Will skip checking ERODC ACEs.
         * Security Permissions Check for

           DC=ForestDnsZones,DC=DOMAIN,DC=com
            (NDNC,Version 3)
         Error NT AUTHORITY\ENTERPRISE DOMAIN CONTROLLERS doesn't have

            Replicating Directory Changes In Filtered Set
         access rights for the naming context:

         DC=ForestDnsZones,DC=DOMAIN,DC=com
         * Security Permissions Check for

           DC=DomainDnsZones,DC=DOMAIN,DC=com
            (NDNC,Version 3)
         Error NT AUTHORITY\ENTERPRISE DOMAIN CONTROLLERS doesn't have

            Replicating Directory Changes In Filtered Set
         access rights for the naming context:

         DC=DomainDnsZones,DC=DOMAIN,DC=com
         * Security Permissions Check for

           CN=Schema,CN=Configuration,DC=DOMAIN,DC=com
            (Schema,Version 3)
         * Security Permissions Check for

           CN=Configuration,DC=DOMAIN,DC=com
            (Configuration,Version 3)
         * Security Permissions Check for

           DC=DOMAIN,DC=com
            (Domain,Version 3)
         ......................... NEWDC failed test NCSecDesc

      Starting test: NetLogons

         * Network Logons Privileges Check
         Unable to connect to the NETLOGON share! (\\NEWDC\netlogon)

         [NEWDC] An net use or LsaPolicy operation failed with error 67,

         The network name cannot be found..

         ......................... NEWDC failed test NetLogons

      Starting test: ObjectsReplicated

         NEWDC is in domain DC=DOMAIN,DC=com
         Checking for CN=NEWDC,OU=Domain Conrtollers,OU=Great Jones,OU=Servers,DC=DOMAIN,DC=com in domain DC=DOMAIN,DC=com on 1 servers
            Object is up-to-date on all servers.
         Checking for CN=NTDS Settings,CN=NEWDC,CN=Servers,CN=Houston,CN=Sites,CN=Configuration,DC=DOMAIN,DC=com in domain CN=Configuration,DC=DOMAIN,DC=com on 1 servers
            Object is up-to-date on all servers.
         ......................... NEWDC passed test ObjectsReplicated

      Test omitted by user request: OutboundSecureChannels

      Starting test: Replications

         * Replications Check
         * Replication Latency Check
            DC=ForestDnsZones,DC=DOMAIN,DC=com
               Latency information for 4 entries in the vector were ignored.
                  4 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=DomainDnsZones,DC=DOMAIN,DC=com
               Latency information for 4 entries in the vector were ignored.
                  4 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=Schema,CN=Configuration,DC=DOMAIN,DC=com
               Latency information for 9 entries in the vector were ignored.
                  9 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=DOMAIN,DC=com
               Latency information for 9 entries in the vector were ignored.
                  9 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=DOMAIN,DC=com
               Latency information for 9 entries in the vector were ignored.
                  9 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).  
         ......................... NEWDC passed test Replications

      Starting test: RidManager

         * Available RID Pool for the Domain is 8124 to 1073741823
         * MAINDC.DOMAIN.com is the RID Master
         * DsBind with RID Master was successful
         * rIDAllocationPool is 7624 to 8123
         * rIDPreviousAllocationPool is 7624 to 8123
         * rIDNextRID: 7624
         ......................... NEWDC passed test RidManager

      Starting test: Services

         * Checking Service: EventSystem
         * Checking Service: RpcSs
         * Checking Service: NTDS
         * Checking Service: DnsCache
         * Checking Service: NtFrs
         * Checking Service: IsmServ
         * Checking Service: kdc
         * Checking Service: SamSs
         * Checking Service: LanmanServer
         * Checking Service: LanmanWorkstation
         * Checking Service: w32time
         * Checking Service: NETLOGON
         ......................... NEWDC passed test Services

      Starting test: SystemLog

         * The System Event log test
         Found no errors in "System" Event log in the last 60 minutes.
         ......................... NEWDC passed test SystemLog

      Test omitted by user request: Topology

      Test omitted by user request: VerifyEnterpriseReferences

      Starting test: VerifyReferences

         The system object reference (serverReference)

         CN=NEWDC,OU=Domain Conrtollers,OU=Great Jones,OU=Servers,DC=DOMAIN,DC=com

         and backlink on

         CN=NEWDC,CN=Servers,CN=Houston,CN=Sites,CN=Configuration,DC=DOMAIN,DC=com

         are correct.
         The system object reference (serverReferenceBL)

         CN=NEWDC,CN=Domain System Volume (SYSVOL share),CN=File Replication Service,CN=System,DC=DOMAIN,DC=com

         and backlink on

         CN=NTDS Settings,CN=NEWDC,CN=Servers,CN=Houston,CN=Sites,CN=Configuration,DC=DOMAIN,DC=com

         are correct.
         The system object reference (frsComputerReferenceBL)

         CN=NEWDC,CN=Domain System Volume (SYSVOL share),CN=File Replication Service,CN=System,DC=DOMAIN,DC=com

         and backlink on

         CN=NEWDC,OU=Domain Conrtollers,OU=Great Jones,OU=Servers,DC=DOMAIN,DC=com

         are correct.
         ......................... NEWDC passed test VerifyReferences

      Test omitted by user request: VerifyReplicas

   
      Test omitted by user request: DNS

      Test omitted by user request: DNS

   
   Running partition tests on : ForestDnsZones

      Starting test: CheckSDRefDom

         ......................... ForestDnsZones passed test CheckSDRefDom

      Starting test: CrossRefValidation

         ......................... ForestDnsZones passed test

         CrossRefValidation

   
   Running partition tests on : DomainDnsZones

      Starting test: CheckSDRefDom

         ......................... DomainDnsZones passed test CheckSDRefDom

      Starting test: CrossRefValidation

         ......................... DomainDnsZones passed test

         CrossRefValidation

   
   Running partition tests on : Schema

      Starting test: CheckSDRefDom

         ......................... Schema passed test CheckSDRefDom

      Starting test: CrossRefValidation

         ......................... Schema passed test CrossRefValidation

   
   Running partition tests on : Configuration

      Starting test: CheckSDRefDom

         ......................... Configuration passed test CheckSDRefDom

      Starting test: CrossRefValidation

         ......................... Configuration passed test CrossRefValidation

   
   Running partition tests on : DOMAIN

      Starting test: CheckSDRefDom

         ......................... DOMAIN passed test CheckSDRefDom

      Starting test: CrossRefValidation

         ......................... DOMAIN passed test CrossRefValidation

   
   Running enterprise tests on : DOMAIN.com

      Test omitted by user request: DNS

      Test omitted by user request: DNS

      Starting test: LocatorCheck

         GC Name: \\MAINDC.DOMAIN.com

         Locator Flags: 0xe00003fd
         PDC Name: \\MAINDC.DOMAIN.com
         Locator Flags: 0xe00003fd
         Time Server Name: \\MAINDC.DOMAIN.com
         Locator Flags: 0xe00003fd
         Preferred Time Server Name: \\MAINDC.DOMAIN.com
         Locator Flags: 0xe00003fd
         KDC Name: \\MAINDC.DOMAIN.com
         Locator Flags: 0xe00003fd
         ......................... DOMAIN.com passed test LocatorCheck

      Starting test: Intersite

         Skipping site Dallas, this site is outside the scope provided by the

         command line arguments provided.
         Skipping site Houston, this site is outside the scope provided by the

         command line arguments provided.
         ......................... DOMAIN.com passed test Intersite
0
 
LVL 10

Assisted Solution

by:George Khairallah
George Khairallah earned 250 total points
ID: 34117694
OK . thanks for the dcdiag. It looks like your DNS is having a problem. NEWDC FRS seems to be unable to correctly resolve the DNS
[1] FRS can not correctly resolve the DNS name MAINDC.DOMAIN.com from this computer.

             [2] FRS is not running on MAINDC.DOMAIN.com.

             [3] The topology information in the Active Directory Domain Services for this replica has not yet replicated to all the Domain Controllers.

It doesn't look like you have done a netdiag on the server.
You might want to do the same on MainDC as well (run netdiag , and dcdiag (not necessarily with /v).

Also, can you post the result from ipconfig /all from both servers?

If your server are missing entries (even if the A Record exists), but some _mscds records are missing, it would fail FRS and other directory services.
Usually, when you restart ntfrs and netlogon, it triggers a rebuild of these entries.
Also, in netdiag, you can run netdiag /fix , and dcdiag /fix , which will also attempt to fix some DNS entries,  (if fixable). There are drastic measure that we can do, in case your DNS has corruptions, but we don't have enough evidence to prove that you have DNS database corruption yet.

0
 
LVL 10

Expert Comment

by:George Khairallah
ID: 34118026
Glad you got it resolved!
0
 

Author Closing Comment

by:j_crow1
ID: 34143573
Found the problem....The MAINDC was still looking at the decommissioned server for DNS. Changed that and everything started working. Thanks for the help!
0

Featured Post

Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Many of us in IT utilize a combination of roaming profiles and folder redirection to ensure user information carries over from one workstation to another; in my environment, it was to enable virtualization without needing a separate desktop for each…
I'm a big fan of Windows' offline folder caching and have used it on my laptops for over a decade.  One thing I don't like about it, however, is how difficult Microsoft has made it for the cache to be moved out of the Windows folder.  Here's how to …
This tutorial will walk an individual through locating and launching the BEUtility application and how to execute it on the appropriate database. Log onto the server running the Backup Exec database. In a larger environment, this would generally be …
This tutorial will walk an individual through the steps necessary to enable the VMware\Hyper-V licensed feature of Backup Exec 2012. In addition, how to add a VMware server and configure a backup job. The first step is to acquire the necessary licen…

685 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question