Solved

Unable to add second node to cluster

Posted on 2004-09-24
16
585 Views
Last Modified: 2013-11-15
A few steps into configuring a second machine to join an existing cluster, using the Cluster Service Configuration Wizard, I am prompted for a cluster name & prompted for credentials to connect to the cluster I get this error:

The specified cluster name could not be found on the network. Make sure the cluster node is running and the cluster node is reachable from this node.

I am able to ping the cluster node by name & the cluster service is running on the cluster node.
0
Comment
Question by:gpietila
  • 9
  • 4
  • 2
  • +1
16 Comments
 
LVL 3

Expert Comment

by:DanGilbertTX
Comment Utility
You are running AD, right? You can't do MSCS without a domain structure in place. When the second node (potential node at least) looks for the cluster it actually is looking in AD. Anyway, just make sure it is in AD and that it has been replicated to all DCs.

Other than that, I would have to see the actual error message you are getting to figure out what is going on.
0
 

Author Comment

by:gpietila
Comment Utility
I am running AD & the second node is a memberserver in the domain. The only error message I get is:

The specified cluster name could not be found on the network. Make sure the cluster node is running and the cluster node is reachable from this node.
0
 

Expert Comment

by:astonMarton
Comment Utility
I am going to go out on a limb here and say this is absolutely an AD/DNS (same thing at times) error. However, upon doing a little digging on the web I found the following from Microsoft:

http://support.microsoft.com/default.aspx?scid=kb;en-us;272129

I would say to make sure and check that the second Node has the correct DNS (should be pointed to one of the DCs that is running DNS) in it. Make sure that the DNS on that DC has entries in it for the Cluster, the first Node, and the potential second Node. If none of this works then I have a few more questions:

1. You have more than one DC in your forest? Is so, how many?

2. Are you getting any errors in the event logs on your DCs? More specifically replication errors.

3. Have you run DCDIAG to see if your AD structure has any problems?

Anyway, look at the Microsoft solution and see if it fits. If not, get back to me with the information and we will go from there. Thanks.
0
 
LVL 3

Expert Comment

by:DanGilbertTX
Comment Utility
Ugggghhhh.... I was logged in to a coworker's machine when I wrote those last comment. I would appreciate it not being credited to them if you like the answer. Sorry about that.
0
 

Author Comment

by:gpietila
Comment Utility
I have 4 DC's

2 here in the US & 2 in China.

No replication errors in the DC event logs.

DCDiag has a couple of errors
0
 
LVL 3

Expert Comment

by:DanGilbertTX
Comment Utility
If the errors are anything other than Event Log errors I would suggest fixing them. Frankly, I run DCDIAG and pipe it to a text file. I then search the file for "fail". I fix everything so that I don't find any failures before trying to implement anything new. It is just a good practice. Here is what I use for it:

dcdiag /s:SERVER /e /c /v > c:\dcdiag.txt

If there are some issues with the dcdiag output that you are not sure about how to fix I can help diagnose it for you.

Also, did the article from Microsoft have any relevance?
0
 

Author Comment

by:gpietila
Comment Utility
The MS article did not help.

Here is the output of the DCDIAG:


Domain Controller Diagnosis

Performing initial setup:
   * Connecting to directory service on server inadc01.
   * Collecting site info.
   * Identifying all servers.
   * Found 4 DC(s). Testing 4 of them.
   Done gathering initial info.

Doing initial required tests
   
   Testing server: Carlsbad\INADC01
      Starting test: Connectivity
         * Active Directory LDAP Services Check
         * Active Directory RPC Services Check
         ......................... INADC01 passed test Connectivity
   
   Testing server: China\NJDC01
      Starting test: Connectivity
         * Active Directory LDAP Services Check
         * Active Directory RPC Services Check
         ......................... NJDC01 passed test Connectivity
   
   Testing server: China\NJDC02
      Starting test: Connectivity
         * Active Directory LDAP Services Check
         * Active Directory RPC Services Check
         ......................... NJDC02 passed test Connectivity
   
   Testing server: Carlsbad\INADC02
      Starting test: Connectivity
         * Active Directory LDAP Services Check
         * Active Directory RPC Services Check
         ......................... INADC02 passed test Connectivity

Doing primary tests
   
   Testing server: Carlsbad\INADC01
      Starting test: Replications
         * Replications Check
         ......................... INADC01 passed test Replications
      Starting test: Topology
         * Configuration Topology Integrity Check
         * Analyzing the connection topology for CN=Schema,CN=Configuration,DC=inasoft,DC=com.
         * Performing upstream (of target) analysis.
         * Performing downstream (of target) analysis.
         * Analyzing the connection topology for CN=Configuration,DC=inasoft,DC=com.
         * Performing upstream (of target) analysis.
         * Performing downstream (of target) analysis.
         * Analyzing the connection topology for DC=inasoft,DC=com.
         * Performing upstream (of target) analysis.
         * Performing downstream (of target) analysis.
         * Analyzing the connection topology for DC=nj,DC=inasoft,DC=com.
         * Performing upstream (of target) analysis.
         * Performing downstream (of target) analysis.
         ......................... INADC01 passed test Topology
      Starting test: CutoffServers
         * Configuration Topology Aliveness Check
         * Analyzing the alive system replication topology for CN=Schema,CN=Configuration,DC=inasoft,DC=com.
         * Performing upstream (of target) analysis.
         * Performing downstream (of target) analysis.
         * Analyzing the alive system replication topology for CN=Configuration,DC=inasoft,DC=com.
         * Performing upstream (of target) analysis.
         * Performing downstream (of target) analysis.
         * Analyzing the alive system replication topology for DC=inasoft,DC=com.
         * Performing upstream (of target) analysis.
         * Performing downstream (of target) analysis.
         * Analyzing the alive system replication topology for DC=nj,DC=inasoft,DC=com.
         * Performing upstream (of target) analysis.
         * Performing downstream (of target) analysis.
         ......................... INADC01 passed test CutoffServers
      Starting test: NCSecDesc
         * Security Permissions Check for
           CN=Schema,CN=Configuration,DC=inasoft,DC=com
         * Security Permissions Check for
           CN=Configuration,DC=inasoft,DC=com
         * Security Permissions Check for
           DC=inasoft,DC=com
         * Security Permissions Check for
           DC=nj,DC=inasoft,DC=com
         ......................... INADC01 passed test NCSecDesc
      Starting test: NetLogons
         * Network Logons Privileges Check
         ......................... INADC01 passed test NetLogons
      Starting test: Advertising
         The DC INADC01 is advertising itself as a DC and having a DS.
         The DC INADC01 is advertising as an LDAP server
         The DC INADC01 is advertising as having a writeable directory
         The DC INADC01 is advertising as a Key Distribution Center
         The DC INADC01 is advertising as a time server
         The DS INADC01 is advertising as a GC.
         ......................... INADC01 passed test Advertising
      Starting test: KnowsOfRoleHolders
         Role Schema Owner = CN=NTDS Settings,CN=INADC01,CN=Servers,CN=Carlsbad,CN=Sites,CN=Configuration,DC=inasoft,DC=com
         Role Domain Owner = CN=NTDS Settings,CN=INADC01,CN=Servers,CN=Carlsbad,CN=Sites,CN=Configuration,DC=inasoft,DC=com
         Role PDC Owner = CN=NTDS Settings,CN=INADC01,CN=Servers,CN=Carlsbad,CN=Sites,CN=Configuration,DC=inasoft,DC=com
         Role Rid Owner = CN=NTDS Settings,CN=INADC01,CN=Servers,CN=Carlsbad,CN=Sites,CN=Configuration,DC=inasoft,DC=com
         Role Infrastructure Update Owner = CN=NTDS Settings,CN=INADC01,CN=Servers,CN=Carlsbad,CN=Sites,CN=Configuration,DC=inasoft,DC=com
         ......................... INADC01 passed test KnowsOfRoleHolders
      Starting test: RidManager
         * Available RID Pool for the Domain is 3101 to 1073741823
         * inadc01.inasoft.com is the RID Master
         * DsBind with RID Master was successful
         * rIDAllocationPool is 2101 to 2600
         * rIDNextRID: 1435
         * rIDPreviousAllocationPool is 1101 to 1600
         ......................... INADC01 passed test RidManager
      Starting test: MachineAccount
         * SPN found :LDAP/inadc01.inasoft.com/inasoft.com
         * SPN found :LDAP/inadc01.inasoft.com
         * SPN found :LDAP/INADC01
         * SPN found :LDAP/inadc01.inasoft.com/INASOFT
         * SPN found :LDAP/f10110b5-0462-4ac8-a1d0-fd2ce9e59aa6._msdcs.inasoft.com
         * SPN found :E3514235-4B06-11D1-AB04-00C04FC2DCD2/f10110b5-0462-4ac8-a1d0-fd2ce9e59aa6/inasoft.com
         * SPN found :HOST/inadc01.inasoft.com/inasoft.com
         * SPN found :HOST/inadc01.inasoft.com
         * SPN found :HOST/INADC01
         * SPN found :HOST/inadc01.inasoft.com/INASOFT
         * SPN found :GC/inadc01.inasoft.com/inasoft.com
         ......................... INADC01 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
         ......................... INADC01 passed test Services
      Starting test: OutboundSecureChannels
         * The Outbound Secure Channels test
         ** Did not run Outbound Secure Channels test
         because /testdomain: was not entered
         ......................... INADC01 passed test OutboundSecureChannels
      Starting test: ObjectsReplicated
         INADC01 is in domain DC=inasoft,DC=com
         Checking for CN=INADC01,OU=Domain Controllers,DC=inasoft,DC=com in domain DC=inasoft,DC=com on 4 servers
            Object is up-to-date on all servers.
         Checking for CN=NTDS Settings,CN=INADC01,CN=Servers,CN=Carlsbad,CN=Sites,CN=Configuration,DC=inasoft,DC=com in domain CN=Configuration,DC=inasoft,DC=com on 4 servers
            Object is up-to-date on all servers.
         ......................... INADC01 passed test ObjectsReplicated
      Starting test: frssysvol
         * The File Replication Service Event log test
         The SYSVOL has been shared, and the AD is no longer
         prevented from starting by the File Replication Service.
         There are errors after the SYSVOL has been shared.
         The SYSVOL can prevent the AD from starting.
         An Warning Event occured.  EventID: 0x800034FA
            Time Generated: 09/15/2004   10:41:59
            Event String: Following is the summary of warnings and errors

encountered by File Replication Service while

polling the Domain Controller inadc01.inasoft.com

for FRS replica set configuration information.

 



The nTDSConnection object cn=6c43f7fa-d819-42fc-ac69-f6aa992f4422,cn=ntds settings,cn=inadc02,cn=servers,cn=carlsbad,cn=sites,cn=configuration,dc=inasoft,dc=com is conflicting with cn=inadc01,cn=ntds settings,cn=inadc02,cn=servers,cn=carlsbad,cn=sites,cn=configuration,dc=inasoft,dc=com. Using cn=6c43f7fa-d819-42fc-ac69-f6aa992f4422,cn=ntds settings,cn=inadc02,cn=servers,cn=carlsbad,cn=sites,cn=configuration,dc=inasoft,dc=com





 
         An Warning Event occured.  EventID: 0x800034FA
            Time Generated: 09/16/2004   10:42:41
            Event String: Following is the summary of warnings and errors

encountered by File Replication Service while

polling the Domain Controller inadc01.inasoft.com

for FRS replica set configuration information.

 



The nTDSConnection object cn=6c43f7fa-d819-42fc-ac69-f6aa992f4422,cn=ntds settings,cn=inadc02,cn=servers,cn=carlsbad,cn=sites,cn=configuration,dc=inasoft,dc=com is conflicting with cn=inadc01,cn=ntds settings,cn=inadc02,cn=servers,cn=carlsbad,cn=sites,cn=configuration,dc=inasoft,dc=com. Using cn=6c43f7fa-d819-42fc-ac69-f6aa992f4422,cn=ntds settings,cn=inadc02,cn=servers,cn=carlsbad,cn=sites,cn=configuration,dc=inasoft,dc=com





 
         An Warning Event occured.  EventID: 0x800034FA
            Time Generated: 09/17/2004   10:43:16
            Event String: Following is the summary of warnings and errors

encountered by File Replication Service while

polling the Domain Controller inadc01.inasoft.com

for FRS replica set configuration information.

 



The nTDSConnection object cn=6c43f7fa-d819-42fc-ac69-f6aa992f4422,cn=ntds settings,cn=inadc02,cn=servers,cn=carlsbad,cn=sites,cn=configuration,dc=inasoft,dc=com is conflicting with cn=inadc01,cn=ntds settings,cn=inadc02,cn=servers,cn=carlsbad,cn=sites,cn=configuration,dc=inasoft,dc=com. Using cn=6c43f7fa-d819-42fc-ac69-f6aa992f4422,cn=ntds settings,cn=inadc02,cn=servers,cn=carlsbad,cn=sites,cn=configuration,dc=inasoft,dc=com





 
         An Warning Event occured.  EventID: 0x800034FA
            Time Generated: 09/18/2004   10:43:50
            Event String: Following is the summary of warnings and errors

encountered by File Replication Service while

polling the Domain Controller inadc01.inasoft.com

for FRS replica set configuration information.

 



The nTDSConnection object cn=6c43f7fa-d819-42fc-ac69-f6aa992f4422,cn=ntds settings,cn=inadc02,cn=servers,cn=carlsbad,cn=sites,cn=configuration,dc=inasoft,dc=com is conflicting with cn=inadc01,cn=ntds settings,cn=inadc02,cn=servers,cn=carlsbad,cn=sites,cn=configuration,dc=inasoft,dc=com. Using cn=6c43f7fa-d819-42fc-ac69-f6aa992f4422,cn=ntds settings,cn=inadc02,cn=servers,cn=carlsbad,cn=sites,cn=configuration,dc=inasoft,dc=com





 
         An Warning Event occured.  EventID: 0x800034FA
            Time Generated: 09/19/2004   10:44:24
            Event String: Following is the summary of warnings and errors

encountered by File Replication Service while

polling the Domain Controller inadc01.inasoft.com

for FRS replica set configuration information.

 



The nTDSConnection object cn=6c43f7fa-d819-42fc-ac69-f6aa992f4422,cn=ntds settings,cn=inadc02,cn=servers,cn=carlsbad,cn=sites,cn=configuration,dc=inasoft,dc=com is conflicting with cn=inadc01,cn=ntds settings,cn=inadc02,cn=servers,cn=carlsbad,cn=sites,cn=configuration,dc=inasoft,dc=com. Using cn=6c43f7fa-d819-42fc-ac69-f6aa992f4422,cn=ntds settings,cn=inadc02,cn=servers,cn=carlsbad,cn=sites,cn=configuration,dc=inasoft,dc=com





 
         An Warning Event occured.  EventID: 0x800034FA
            Time Generated: 09/20/2004   10:45:12
            Event String: Following is the summary of warnings and errors

encountered by File Replication Service while

polling the Domain Controller inadc01.inasoft.com

for FRS replica set configuration information.

 



The nTDSConnection object cn=6c43f7fa-d819-42fc-ac69-f6aa992f4422,cn=ntds settings,cn=inadc02,cn=servers,cn=carlsbad,cn=sites,cn=configuration,dc=inasoft,dc=com is conflicting with cn=inadc01,cn=ntds settings,cn=inadc02,cn=servers,cn=carlsbad,cn=sites,cn=configuration,dc=inasoft,dc=com. Using cn=6c43f7fa-d819-42fc-ac69-f6aa992f4422,cn=ntds settings,cn=inadc02,cn=servers,cn=carlsbad,cn=sites,cn=configuration,dc=inasoft,dc=com





 
         An Warning Event occured.  EventID: 0x800034FA
            Time Generated: 09/21/2004   10:46:15
            Event String: Following is the summary of warnings and errors

encountered by File Replication Service while

polling the Domain Controller inadc01.inasoft.com

for FRS replica set configuration information.

 



The nTDSConnection object cn=6c43f7fa-d819-42fc-ac69-f6aa992f4422,cn=ntds settings,cn=inadc02,cn=servers,cn=carlsbad,cn=sites,cn=configuration,dc=inasoft,dc=com is conflicting with cn=inadc01,cn=ntds settings,cn=inadc02,cn=servers,cn=carlsbad,cn=sites,cn=configuration,dc=inasoft,dc=com. Using cn=6c43f7fa-d819-42fc-ac69-f6aa992f4422,cn=ntds settings,cn=inadc02,cn=servers,cn=carlsbad,cn=sites,cn=configuration,dc=inasoft,dc=com





 
         An Warning Event occured.  EventID: 0x800034FA
            Time Generated: 09/22/2004   10:46:52
            Event String: Following is the summary of warnings and errors

encountered by File Replication Service while

polling the Domain Controller inadc01.inasoft.com

for FRS replica set configuration information.

 



The nTDSConnection object cn=6c43f7fa-d819-42fc-ac69-f6aa992f4422,cn=ntds settings,cn=inadc02,cn=servers,cn=carlsbad,cn=sites,cn=configuration,dc=inasoft,dc=com is conflicting with cn=inadc01,cn=ntds settings,cn=inadc02,cn=servers,cn=carlsbad,cn=sites,cn=configuration,dc=inasoft,dc=com. Using cn=6c43f7fa-d819-42fc-ac69-f6aa992f4422,cn=ntds settings,cn=inadc02,cn=servers,cn=carlsbad,cn=sites,cn=configuration,dc=inasoft,dc=com





 
         An Warning Event occured.  EventID: 0x800034FA
            Time Generated: 09/23/2004   10:47:37
            Event String: Following is the summary of warnings and errors

encountered by File Replication Service while

polling the Domain Controller inadc01.inasoft.com

for FRS replica set configuration information.

 



The nTDSConnection object cn=6c43f7fa-d819-42fc-ac69-f6aa992f4422,cn=ntds settings,cn=inadc02,cn=servers,cn=carlsbad,cn=sites,cn=configuration,dc=inasoft,dc=com is conflicting with cn=inadc01,cn=ntds settings,cn=inadc02,cn=servers,cn=carlsbad,cn=sites,cn=configuration,dc=inasoft,dc=com. Using cn=6c43f7fa-d819-42fc-ac69-f6aa992f4422,cn=ntds settings,cn=inadc02,cn=servers,cn=carlsbad,cn=sites,cn=configuration,dc=inasoft,dc=com





 
         An Warning Event occured.  EventID: 0x800034FA
            Time Generated: 09/24/2004   10:48:21
            Event String: Following is the summary of warnings and errors

encountered by File Replication Service while

polling the Domain Controller inadc01.inasoft.com

for FRS replica set configuration information.

 



The nTDSConnection object cn=6c43f7fa-d819-42fc-ac69-f6aa992f4422,cn=ntds settings,cn=inadc02,cn=servers,cn=carlsbad,cn=sites,cn=configuration,dc=inasoft,dc=com is conflicting with cn=inadc01,cn=ntds settings,cn=inadc02,cn=servers,cn=carlsbad,cn=sites,cn=configuration,dc=inasoft,dc=com. Using cn=6c43f7fa-d819-42fc-ac69-f6aa992f4422,cn=ntds settings,cn=inadc02,cn=servers,cn=carlsbad,cn=sites,cn=configuration,dc=inasoft,dc=com





 
         An Warning Event occured.  EventID: 0x800034FA
            Time Generated: 09/25/2004   10:48:49
            Event String: Following is the summary of warnings and errors

encountered by File Replication Service while

polling the Domain Controller inadc01.inasoft.com

for FRS replica set configuration information.

 



The nTDSConnection object cn=6c43f7fa-d819-42fc-ac69-f6aa992f4422,cn=ntds settings,cn=inadc02,cn=servers,cn=carlsbad,cn=sites,cn=configuration,dc=inasoft,dc=com is conflicting with cn=inadc01,cn=ntds settings,cn=inadc02,cn=servers,cn=carlsbad,cn=sites,cn=configuration,dc=inasoft,dc=com. Using cn=6c43f7fa-d819-42fc-ac69-f6aa992f4422,cn=ntds settings,cn=inadc02,cn=servers,cn=carlsbad,cn=sites,cn=configuration,dc=inasoft,dc=com





 
         An Warning Event occured.  EventID: 0x800034FA
            Time Generated: 09/26/2004   10:49:16
            Event String: Following is the summary of warnings and errors

encountered by File Replication Service while

polling the Domain Controller inadc01.inasoft.com

for FRS replica set configuration information.

 



The nTDSConnection object cn=6c43f7fa-d819-42fc-ac69-f6aa992f4422,cn=ntds settings,cn=inadc02,cn=servers,cn=carlsbad,cn=sites,cn=configuration,dc=inasoft,dc=com is conflicting with cn=inadc01,cn=ntds settings,cn=inadc02,cn=servers,cn=carlsbad,cn=sites,cn=configuration,dc=inasoft,dc=com. Using cn=6c43f7fa-d819-42fc-ac69-f6aa992f4422,cn=ntds settings,cn=inadc02,cn=servers,cn=carlsbad,cn=sites,cn=configuration,dc=inasoft,dc=com





 
         An Warning Event occured.  EventID: 0x800034FA
            Time Generated: 09/27/2004   10:49:51
            Event String: Following is the summary of warnings and errors

encountered by File Replication Service while

polling the Domain Controller inadc01.inasoft.com

for FRS replica set configuration information.

 



The nTDSConnection object cn=6c43f7fa-d819-42fc-ac69-f6aa992f4422,cn=ntds settings,cn=inadc02,cn=servers,cn=carlsbad,cn=sites,cn=configuration,dc=inasoft,dc=com is conflicting with cn=inadc01,cn=ntds settings,cn=inadc02,cn=servers,cn=carlsbad,cn=sites,cn=configuration,dc=inasoft,dc=com. Using cn=6c43f7fa-d819-42fc-ac69-f6aa992f4422,cn=ntds settings,cn=inadc02,cn=servers,cn=carlsbad,cn=sites,cn=configuration,dc=inasoft,dc=com





 
         An Warning Event occured.  EventID: 0x800034FA
            Time Generated: 09/28/2004   10:50:58
            Event String: Following is the summary of warnings and errors

encountered by File Replication Service while

polling the Domain Controller inadc01.inasoft.com

for FRS replica set configuration information.

 



The nTDSConnection object cn=6c43f7fa-d819-42fc-ac69-f6aa992f4422,cn=ntds settings,cn=inadc02,cn=servers,cn=carlsbad,cn=sites,cn=configuration,dc=inasoft,dc=com is conflicting with cn=inadc01,cn=ntds settings,cn=inadc02,cn=servers,cn=carlsbad,cn=sites,cn=configuration,dc=inasoft,dc=com. Using cn=6c43f7fa-d819-42fc-ac69-f6aa992f4422,cn=ntds settings,cn=inadc02,cn=servers,cn=carlsbad,cn=sites,cn=configuration,dc=inasoft,dc=com





 
         ......................... INADC01 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.
         ......................... INADC01 passed test kccevent
      Starting test: systemlog
         * The System Event log test
         Found no errors in System Event log in the last 60 minutes.
         ......................... INADC01 passed test systemlog
   
   Testing server: China\NJDC01
      Starting test: Replications
         * Replications Check
         [Replications Check,NJDC01] A recent replication attempt failed:
            From INADC02 to NJDC01
            Naming Context: CN=Schema,CN=Configuration,DC=inasoft,DC=com
            The replication generated an error (8524):
            The DSA operation is unable to proceed because of a DNS lookup failure.
            The failure occurred at 2004-09-29 09:13.14.
            The last success occurred at (never).
            9 failures have occurred since the last success.
            The guid-based DNS name 4e9b2b3c-d058-450b-a76f-23277550772e._msdcs.inasoft.com
            is not registered on one or more DNS servers.
         REPLICATION LATENCY WARNING
         NJDC01: A full synchronization is in progress
            from INADC02 to NJDC01
            Replication of new changes along this path will be delayed.
            The full sync is 0.00% complete.
         [Replications Check,NJDC01] A recent replication attempt failed:
            From INADC01 to NJDC01
            Naming Context: CN=Schema,CN=Configuration,DC=inasoft,DC=com
            The replication generated an error (8524):
            The DSA operation is unable to proceed because of a DNS lookup failure.
            The failure occurred at 2004-09-29 09:33.30.
            The last success occurred at 2004-09-28 18:59.43.
            18 failures have occurred since the last success.
            The guid-based DNS name f10110b5-0462-4ac8-a1d0-fd2ce9e59aa6._msdcs.inasoft.com
            is not registered on one or more DNS servers.
         [Replications Check,NJDC01] A recent replication attempt failed:
            From INADC02 to NJDC01
            Naming Context: CN=Configuration,DC=inasoft,DC=com
            The replication generated an error (8524):
            The DSA operation is unable to proceed because of a DNS lookup failure.
            The failure occurred at 2004-09-29 09:13.56.
            The last success occurred at (never).
            9 failures have occurred since the last success.
            The guid-based DNS name 4e9b2b3c-d058-450b-a76f-23277550772e._msdcs.inasoft.com
            is not registered on one or more DNS servers.
         REPLICATION LATENCY WARNING
         NJDC01: A full synchronization is in progress
            from INADC02 to NJDC01
            Replication of new changes along this path will be delayed.
            The full sync is 0.00% complete.
         [Replications Check,NJDC01] A recent replication attempt failed:
            From INADC01 to NJDC01
            Naming Context: CN=Configuration,DC=inasoft,DC=com
            The replication generated an error (8524):
            The DSA operation is unable to proceed because of a DNS lookup failure.
            The failure occurred at 2004-09-29 09:34.00.
            The last success occurred at 2004-09-28 18:59.42.
            18 failures have occurred since the last success.
            The guid-based DNS name f10110b5-0462-4ac8-a1d0-fd2ce9e59aa6._msdcs.inasoft.com
            is not registered on one or more DNS servers.
         [Replications Check,NJDC01] A recent replication attempt failed:
            From INADC02 to NJDC01
            Naming Context: DC=inasoft,DC=com
            The replication generated an error (8524):
            The DSA operation is unable to proceed because of a DNS lookup failure.
            The failure occurred at 2004-09-29 09:14.52.
            The last success occurred at (never).
            9 failures have occurred since the last success.
            The guid-based DNS name 4e9b2b3c-d058-450b-a76f-23277550772e._msdcs.inasoft.com
            is not registered on one or more DNS servers.
         REPLICATION LATENCY WARNING
         NJDC01: A full synchronization is in progress
            from INADC02 to NJDC01
            Replication of new changes along this path will be delayed.
            The full sync is 0.00% complete.
         [Replications Check,NJDC01] A recent replication attempt failed:
            From INADC01 to NJDC01
            Naming Context: DC=inasoft,DC=com
            The replication generated an error (8524):
            The DSA operation is unable to proceed because of a DNS lookup failure.
            The failure occurred at 2004-09-29 09:34.24.
            The last success occurred at 2004-09-28 18:59.57.
            17 failures have occurred since the last success.
            The guid-based DNS name f10110b5-0462-4ac8-a1d0-fd2ce9e59aa6._msdcs.inasoft.com
            is not registered on one or more DNS servers.
         ......................... NJDC01 passed test Replications
      Starting test: Topology
         * Configuration Topology Integrity Check
         * Analyzing the connection topology for DC=nj,DC=inasoft,DC=com.
         * Performing upstream (of target) analysis.
         * Performing downstream (of target) analysis.
         * Analyzing the connection topology for CN=Schema,CN=Configuration,DC=inasoft,DC=com.
         * Performing upstream (of target) analysis.
         * Performing downstream (of target) analysis.
         * Analyzing the connection topology for CN=Configuration,DC=inasoft,DC=com.
         * Performing upstream (of target) analysis.
         * Performing downstream (of target) analysis.
         * Analyzing the connection topology for DC=inasoft,DC=com.
         * Performing upstream (of target) analysis.
         * Performing downstream (of target) analysis.
         ......................... NJDC01 passed test Topology
      Starting test: CutoffServers
         * Configuration Topology Aliveness Check
         * Analyzing the alive system replication topology for DC=nj,DC=inasoft,DC=com.
         * Performing upstream (of target) analysis.
         * Performing downstream (of target) analysis.
         * Analyzing the alive system replication topology for CN=Schema,CN=Configuration,DC=inasoft,DC=com.
         * Performing upstream (of target) analysis.
         * Performing downstream (of target) analysis.
         * Analyzing the alive system replication topology for CN=Configuration,DC=inasoft,DC=com.
         * Performing upstream (of target) analysis.
         * Performing downstream (of target) analysis.
         * Analyzing the alive system replication topology for DC=inasoft,DC=com.
         * Performing upstream (of target) analysis.
         * Performing downstream (of target) analysis.
         ......................... NJDC01 passed test CutoffServers
      Starting test: NCSecDesc
         * Security Permissions Check for
           DC=nj,DC=inasoft,DC=com
         * Security Permissions Check for
           CN=Schema,CN=Configuration,DC=inasoft,DC=com
         * Security Permissions Check for
           CN=Configuration,DC=inasoft,DC=com
         * Security Permissions Check for
           DC=inasoft,DC=com
         ......................... NJDC01 passed test NCSecDesc
      Starting test: NetLogons
         * Network Logons Privileges Check
         ......................... NJDC01 passed test NetLogons
      Starting test: Advertising
         The DC NJDC01 is advertising itself as a DC and having a DS.
         The DC NJDC01 is advertising as an LDAP server
         The DC NJDC01 is advertising as having a writeable directory
         The DC NJDC01 is advertising as a Key Distribution Center
         Warning: NJDC01 is not advertising as a time server.
         The DS NJDC01 is advertising as a GC.
         ......................... NJDC01 failed test Advertising
      Starting test: KnowsOfRoleHolders
         Role Schema Owner = CN=NTDS Settings,CN=INADC01,CN=Servers,CN=Carlsbad,CN=Sites,CN=Configuration,DC=inasoft,DC=com
         Role Domain Owner = CN=NTDS Settings,CN=INADC01,CN=Servers,CN=Carlsbad,CN=Sites,CN=Configuration,DC=inasoft,DC=com
         Role PDC Owner = CN=NTDS Settings,CN=NJDC01,CN=Servers,CN=China,CN=Sites,CN=Configuration,DC=inasoft,DC=com
         Role Rid Owner = CN=NTDS Settings,CN=NJDC01,CN=Servers,CN=China,CN=Sites,CN=Configuration,DC=inasoft,DC=com
         Role Infrastructure Update Owner = CN=NTDS Settings,CN=NJDC01,CN=Servers,CN=China,CN=Sites,CN=Configuration,DC=inasoft,DC=com
         ......................... NJDC01 passed test KnowsOfRoleHolders
      Starting test: RidManager
         * Available RID Pool for the Domain is 2101 to 1073741823
         * njdc01.nj.inasoft.com is the RID Master
         * DsBind with RID Master was successful
         * rIDAllocationPool is 1101 to 1600
         * rIDNextRID: 1149
         * rIDPreviousAllocationPool is 1101 to 1600
         ......................... NJDC01 passed test RidManager
      Starting test: MachineAccount
         * SPN found :LDAP/njdc01.nj.inasoft.com/nj.inasoft.com
         * SPN found :LDAP/njdc01.nj.inasoft.com
         * SPN found :LDAP/NJDC01
         * SPN found :LDAP/njdc01.nj.inasoft.com/NJINASOFT
         * SPN found :LDAP/0b4b29bf-7fa1-485f-959c-21a19dbbdacb._msdcs.inasoft.com
         * SPN found :E3514235-4B06-11D1-AB04-00C04FC2DCD2/0b4b29bf-7fa1-485f-959c-21a19dbbdacb/nj.inasoft.com
         * SPN found :HOST/njdc01.nj.inasoft.com/nj.inasoft.com
         * SPN found :HOST/njdc01.nj.inasoft.com
         * SPN found :HOST/NJDC01
         * SPN found :HOST/njdc01.nj.inasoft.com/NJINASOFT
         * SPN found :GC/njdc01.nj.inasoft.com/inasoft.com
         ......................... NJDC01 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
            w32time Service is stopped on [NJDC01]
         * Checking Service: TrkWks
         * Checking Service: TrkSvr
         * Checking Service: NETLOGON
         ......................... NJDC01 failed test Services
      Starting test: OutboundSecureChannels
         * The Outbound Secure Channels test
         ** Did not run Outbound Secure Channels test
         because /testdomain: was not entered
         ......................... NJDC01 passed test OutboundSecureChannels
      Starting test: ObjectsReplicated
         NJDC01 is in domain DC=nj,DC=inasoft,DC=com
         Checking for CN=NJDC01,OU=Domain Controllers,DC=nj,DC=inasoft,DC=com in domain DC=nj,DC=inasoft,DC=com on 4 servers
            Object is up-to-date on all servers.
         Checking for CN=NTDS Settings,CN=NJDC01,CN=Servers,CN=China,CN=Sites,CN=Configuration,DC=inasoft,DC=com in domain CN=Configuration,DC=inasoft,DC=com on 4 servers
            Object is up-to-date on all servers.
         ......................... NJDC01 passed test ObjectsReplicated
      Starting test: frssysvol
         * The File Replication Service Event log test
         The SYSVOL has been shared, and the AD is no longer
         prevented from starting by the File Replication Service.
         An Warning Event occured.  EventID: 0x800034C4
            Time Generated: 09/26/2004   02:12:39
            Event String: The File Replication Service is having trouble

enabling replication from NJDC02 to NJDC01 for

c:\winnt\sysvol\domain using the DNS name

njdc02.nj.inasoft.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

njdc02.nj.inasoft.com from this computer.

 [2] FRS is not running on njdc02.nj.inasoft.com.



 [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.
         An Warning Event occured.  EventID: 0x800034C4
            Time Generated: 09/27/2004   03:44:22
            Event String: The File Replication Service is having trouble

enabling replication from NJDC02 to NJDC01 for

c:\winnt\sysvol\domain using the DNS name

njdc02.nj.inasoft.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

njdc02.nj.inasoft.com from this computer.

 [2] FRS is not running on njdc02.nj.inasoft.com.



 [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.
         An Warning Event occured.  EventID: 0x800034C4
            Time Generated: 09/28/2004   04:59:47
            Event String: The File Replication Service is having trouble

enabling replication from NJDC02 to NJDC01 for

c:\winnt\sysvol\domain using the DNS name

njdc02.nj.inasoft.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

njdc02.nj.inasoft.com from this computer.

 [2] FRS is not running on njdc02.nj.inasoft.com.



 [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.
         An Warning Event occured.  EventID: 0x800034C4
            Time Generated: 09/29/2004   08:07:13
            Event String: The File Replication Service is having trouble

enabling replication from NJDC02 to NJDC01 for

c:\winnt\sysvol\domain using the DNS name

njdc02.nj.inasoft.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

njdc02.nj.inasoft.com from this computer.

 [2] FRS is not running on njdc02.nj.inasoft.com.



 [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.
         ......................... NJDC01 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.
         ......................... NJDC01 passed test kccevent
      Starting test: systemlog
         * The System Event log test
         Found no errors in System Event log in the last 60 minutes.
         ......................... NJDC01 passed test systemlog
   
   Testing server: China\NJDC02
      Starting test: Replications
         * Replications Check
         [Replications Check,NJDC02] A recent replication attempt failed:
            From NJDC01 to NJDC02
            Naming Context: DC=nj,DC=inasoft,DC=com
            The replication generated an error (8524):
            The DSA operation is unable to proceed because of a DNS lookup failure.
            The failure occurred at 2004-09-29 09:37.40.
            The last success occurred at 2004-09-26 01:52.59.
            233 failures have occurred since the last success.
            The guid-based DNS name 0b4b29bf-7fa1-485f-959c-21a19dbbdacb._msdcs.inasoft.com
            is not registered on one or more DNS servers.
         [Replications Check,NJDC02] A recent replication attempt failed:
            From NJDC01 to NJDC02
            Naming Context: CN=Schema,CN=Configuration,DC=inasoft,DC=com
            The replication generated an error (8524):
            The DSA operation is unable to proceed because of a DNS lookup failure.
            The failure occurred at 2004-09-29 09:38.55.
            The last success occurred at 2004-09-26 01:52.59.
            92 failures have occurred since the last success.
            The guid-based DNS name 0b4b29bf-7fa1-485f-959c-21a19dbbdacb._msdcs.inasoft.com
            is not registered on one or more DNS servers.
         [Replications Check,NJDC02] A recent replication attempt failed:
            From NJDC01 to NJDC02
            Naming Context: CN=Configuration,DC=inasoft,DC=com
            The replication generated an error (8524):
            The DSA operation is unable to proceed because of a DNS lookup failure.
            The failure occurred at 2004-09-29 09:43.14.
            The last success occurred at 2004-09-26 01:55.20.
            765 failures have occurred since the last success.
            The guid-based DNS name 0b4b29bf-7fa1-485f-959c-21a19dbbdacb._msdcs.inasoft.com
            is not registered on one or more DNS servers.
         [Replications Check,NJDC02] A recent replication attempt failed:
            From NJDC01 to NJDC02
            Naming Context: DC=inasoft,DC=com
            The replication generated an error (8524):
            The DSA operation is unable to proceed because of a DNS lookup failure.
            The failure occurred at 2004-09-29 09:43.56.
            The last success occurred at 2004-09-26 01:52.59.
            95 failures have occurred since the last success.
            The guid-based DNS name 0b4b29bf-7fa1-485f-959c-21a19dbbdacb._msdcs.inasoft.com
            is not registered on one or more DNS servers.
         ......................... NJDC02 passed test Replications
      Starting test: Topology
         * Configuration Topology Integrity Check
         * Analyzing the connection topology for DC=nj,DC=inasoft,DC=com.
         * Performing upstream (of target) analysis.
         * Performing downstream (of target) analysis.
         * Analyzing the connection topology for CN=Schema,CN=Configuration,DC=inasoft,DC=com.
         * Performing upstream (of target) analysis.
         * Performing downstream (of target) analysis.
         * Analyzing the connection topology for CN=Configuration,DC=inasoft,DC=com.
         * Performing upstream (of target) analysis.
         * Performing downstream (of target) analysis.
         * Analyzing the connection topology for DC=inasoft,DC=com.
         * Performing upstream (of target) analysis.
         * Performing downstream (of target) analysis.
         ......................... NJDC02 passed test Topology
      Starting test: CutoffServers
         * Configuration Topology Aliveness Check
         * Analyzing the alive system replication topology for DC=nj,DC=inasoft,DC=com.
         * Performing upstream (of target) analysis.
         * Performing downstream (of target) analysis.
         * Analyzing the alive system replication topology for CN=Schema,CN=Configuration,DC=inasoft,DC=com.
         * Performing upstream (of target) analysis.
         * Performing downstream (of target) analysis.
         * Analyzing the alive system replication topology for CN=Configuration,DC=inasoft,DC=com.
         * Performing upstream (of target) analysis.
         * Performing downstream (of target) analysis.
         * Analyzing the alive system replication topology for DC=inasoft,DC=com.
         * Performing upstream (of target) analysis.
         * Performing downstream (of target) analysis.
         ......................... NJDC02 passed test CutoffServers
      Starting test: NCSecDesc
         * Security Permissions Check for
           DC=nj,DC=inasoft,DC=com
         * Security Permissions Check for
           CN=Schema,CN=Configuration,DC=inasoft,DC=com
         * Security Permissions Check for
           CN=Configuration,DC=inasoft,DC=com
         * Security Permissions Check for
           DC=inasoft,DC=com
         [NJDC02] LDAP connection failed with error 58,
         The specified server cannot perform the requested operation..
         ......................... NJDC02 failed test NCSecDesc
      Starting test: NetLogons
         * Network Logons Privileges Check
         ......................... NJDC02 passed test NetLogons
      Starting test: Advertising
         Warning: DsGetDcName returned information for \\njdc01.nj.inasoft.com, when we were trying to reach NJDC02.
         Server is not responding or is not considered suitable.
         The DC NJDC02 is advertising itself as a DC and having a DS.
         The DC NJDC02 is advertising as an LDAP server
         The DC NJDC02 is advertising as having a writeable directory
         The DC NJDC02 is advertising as a Key Distribution Center
         Warning: NJDC02 is not advertising as a time server.
         Warning: NJDC02 has not finished promoting to be a GC.
         Check the event log for domains that cannot be replicated.
         The DS NJDC02 is advertising as a GC.
         ......................... NJDC02 failed test Advertising
      Starting test: KnowsOfRoleHolders
         Role Schema Owner = CN=NTDS Settings,CN=INADC01,CN=Servers,CN=Carlsbad,CN=Sites,CN=Configuration,DC=inasoft,DC=com
         Role Domain Owner = CN=NTDS Settings,CN=INADC01,CN=Servers,CN=Carlsbad,CN=Sites,CN=Configuration,DC=inasoft,DC=com
         Role PDC Owner = CN=NTDS Settings,CN=NJDC01,CN=Servers,CN=China,CN=Sites,CN=Configuration,DC=inasoft,DC=com
         Role Rid Owner = CN=NTDS Settings,CN=NJDC01,CN=Servers,CN=China,CN=Sites,CN=Configuration,DC=inasoft,DC=com
         Role Infrastructure Update Owner = CN=NTDS Settings,CN=NJDC01,CN=Servers,CN=China,CN=Sites,CN=Configuration,DC=inasoft,DC=com
         ......................... NJDC02 passed test KnowsOfRoleHolders
      Starting test: RidManager
         * Available RID Pool for the Domain is 2101 to 1073741823
         * njdc01.nj.inasoft.com is the RID Master
         * DsBind with RID Master was successful
         * rIDAllocationPool is 1601 to 2100
         * rIDNextRID: 1603
         * rIDPreviousAllocationPool is 1601 to 2100
         ......................... NJDC02 passed test RidManager
      Starting test: MachineAccount
         * SPN found :LDAP/njdc02.nj.inasoft.com/nj.inasoft.com
         * SPN found :LDAP/njdc02.nj.inasoft.com
         * SPN found :LDAP/NJDC02
         * SPN found :LDAP/njdc02.nj.inasoft.com/NJINASOFT
         * SPN found :LDAP/6dea0425-6572-4cf8-ba7d-ee615e558b20._msdcs.inasoft.com
         * SPN found :E3514235-4B06-11D1-AB04-00C04FC2DCD2/6dea0425-6572-4cf8-ba7d-ee615e558b20/nj.inasoft.com
         * SPN found :HOST/njdc02.nj.inasoft.com/nj.inasoft.com
         * SPN found :HOST/njdc02.nj.inasoft.com
         * SPN found :HOST/NJDC02
         * SPN found :HOST/njdc02.nj.inasoft.com/NJINASOFT
         * SPN found :GC/njdc02.nj.inasoft.com/inasoft.com
         ......................... NJDC02 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
         ......................... NJDC02 passed test Services
      Starting test: OutboundSecureChannels
         * The Outbound Secure Channels test
         ** Did not run Outbound Secure Channels test
         because /testdomain: was not entered
         ......................... NJDC02 passed test OutboundSecureChannels
      Starting test: ObjectsReplicated
         NJDC02 is in domain DC=nj,DC=inasoft,DC=com
         Checking for CN=NJDC02,OU=Domain Controllers,DC=nj,DC=inasoft,DC=com in domain DC=nj,DC=inasoft,DC=com on 4 servers
            Object is up-to-date on all servers.
         Checking for CN=NTDS Settings,CN=NJDC02,CN=Servers,CN=China,CN=Sites,CN=Configuration,DC=inasoft,DC=com in domain CN=Configuration,DC=inasoft,DC=com on 4 servers
            Authoritative attribute options on INADC02 (writeable)
               usnLocalChange = 218871
               LastOriginatingDsa = INADC02
               usnOriginatingChange = 218871
               timeLastOriginatingChange = 2004-09-28 14:17.20
               VersionLastOriginatingChange = 2
            Out-of-date attribute options on NJDC02 (writeable)
               usnLocalChange = 134788
               LastOriginatingDsa = INADC02
               usnOriginatingChange = 37382
               timeLastOriginatingChange = 2004-08-26 18:09.27
               VersionLastOriginatingChange = 1
         ......................... NJDC02 failed 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.
         An Warning Event occured.  EventID: 0x800034FD
            Time Generated: 09/26/2004   02:08:14
            Event String: File Replication Service is initializing the

system volume with data from another domain

controller. Computer NJDC02 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.
         ......................... NJDC02 passed test frssysvol
      Starting test: kccevent
         * The KCC Event log test
         An Warning Event occured.  EventID: 0x8000061E
            Time Generated: 09/29/2004   09:47:22
            Event String: All servers in site

CN=China,CN=Sites,CN=Configuration,DC=inasoft,DC=com

that can replicate partition DC=inasoft,DC=com

over transport

CN=IP,CN=Inter-Site Transports,CN=Sites,CN=Configuration,DC=inasoft,DC=com

are currently unavailable.
         An Error Event occured.  EventID: 0xC000051F
            Time Generated: 09/29/2004   09:47:22
            Event String: The Directory Service consistency checker has

determined that either (a) there is not enough

physical connectivity published via the Active

Directory Sites and Services Manager to create a

spanning tree connecting all the sites containing

the Partition DC=inasoft,DC=com, or (b)

replication cannot be performed with one or more

critical servers in order for changes to

propagate across all sites (most often due to the

servers being unreachable).  



For (a), please use the Active Directory Sites

and Services Manager to do one of the following:

1. Publish sufficient site connectivity

information such that the system can infer a

route by which this Partition can reach this

site.  This option is preferred.

2. Add an ntdsConnection object to a Domain

Controller that contains the Partition

DC=inasoft,DC=com in this site from a Domain

Controller that contains the same Partition in

another site.  



For (b), please see previous events logged by the

NTDS KCC source that identify the servers that

could not be contacted.
         An Warning Event occured.  EventID: 0x8000061E
            Time Generated: 09/29/2004   09:47:22
            Event String: All servers in site

CN=China,CN=Sites,CN=Configuration,DC=inasoft,DC=com

that can replicate partition

CN=Configuration,DC=inasoft,DC=com over transport

CN=IP,CN=Inter-Site Transports,CN=Sites,CN=Configuration,DC=inasoft,DC=com

 are currently unavailable.
         An Error Event occured.  EventID: 0xC000051F
            Time Generated: 09/29/2004   09:47:22
            Event String: The Directory Service consistency checker has

determined that either (a) there is not enough

physical connectivity published via the Active

Directory Sites and Services Manager to create a

spanning tree connecting all the sites containing

the Partition CN=Configuration,DC=inasoft,DC=com,

or (b) replication cannot be performed with one

or more critical servers in order for changes to

propagate across all sites (most often due to the

servers being unreachable).  



For (a), please use the Active Directory Sites

and Services Manager to do one of the following:

1. Publish sufficient site connectivity

information such that the system can infer a

route by which this Partition can reach this

site.  This option is preferred.

2. Add an ntdsConnection object to a Domain

Controller that contains the Partition

CN=Configuration,DC=inasoft,DC=com in this site

from a Domain Controller that contains the same

Partition in another site.  



For (b), please see previous events logged by the

NTDS KCC source that identify the servers that

could not be contacted.
         ......................... NJDC02 failed test kccevent
      Starting test: systemlog
         * The System Event log test
         An Error Event occured.  EventID: 0x40011006
            Time Generated: 09/29/2004   09:08:34
            Event String: The connection was aborted by the remote WINS.

Remote WINS may not be configured to replicate

with the server.
         An Error Event occured.  EventID: 0x40011006
            Time Generated: 09/29/2004   09:08:35
            Event String: The connection was aborted by the remote WINS.

Remote WINS may not be configured to replicate

with the server.
         An Error Event occured.  EventID: 0x40011006
            Time Generated: 09/29/2004   09:38:34
            Event String: The connection was aborted by the remote WINS.

Remote WINS may not be configured to replicate

with the server.
         An Error Event occured.  EventID: 0x40011006
            Time Generated: 09/29/2004   09:38:34
            Event String: The connection was aborted by the remote WINS.

Remote WINS may not be configured to replicate

with the server.
         ......................... NJDC02 failed test systemlog
   
   Testing server: Carlsbad\INADC02
      Starting test: Replications
         * Replications Check
         ......................... INADC02 passed test Replications
      Starting test: Topology
         * Configuration Topology Integrity Check
         * Analyzing the connection topology for CN=Schema,CN=Configuration,DC=inasoft,DC=com.
         * Performing upstream (of target) analysis.
         * Performing downstream (of target) analysis.
         * Analyzing the connection topology for CN=Configuration,DC=inasoft,DC=com.
         * Performing upstream (of target) analysis.
         * Performing downstream (of target) analysis.
         * Analyzing the connection topology for DC=inasoft,DC=com.
         * Performing upstream (of target) analysis.
         * Performing downstream (of target) analysis.
         * Analyzing the connection topology for DC=nj,DC=inasoft,DC=com.
         * Performing upstream (of target) analysis.
         * Performing downstream (of target) analysis.
         ......................... INADC02 passed test Topology
      Starting test: CutoffServers
         * Configuration Topology Aliveness Check
         * Analyzing the alive system replication topology for CN=Schema,CN=Configuration,DC=inasoft,DC=com.
         * Performing upstream (of target) analysis.
         * Performing downstream (of target) analysis.
         * Analyzing the alive system replication topology for CN=Configuration,DC=inasoft,DC=com.
         * Performing upstream (of target) analysis.
         * Performing downstream (of target) analysis.
         * Analyzing the alive system replication topology for DC=inasoft,DC=com.
         * Performing upstream (of target) analysis.
         * Performing downstream (of target) analysis.
         * Analyzing the alive system replication topology for DC=nj,DC=inasoft,DC=com.
         * Performing upstream (of target) analysis.
         * Performing downstream (of target) analysis.
         ......................... INADC02 passed test CutoffServers
      Starting test: NCSecDesc
         * Security Permissions Check for
           CN=Schema,CN=Configuration,DC=inasoft,DC=com
         * Security Permissions Check for
           CN=Configuration,DC=inasoft,DC=com
         * Security Permissions Check for
           DC=inasoft,DC=com
         * Security Permissions Check for
           DC=nj,DC=inasoft,DC=com
         ......................... INADC02 passed test NCSecDesc
      Starting test: NetLogons
         * Network Logons Privileges Check
         ......................... INADC02 passed test NetLogons
      Starting test: Advertising
         The DC INADC02 is advertising itself as a DC and having a DS.
         The DC INADC02 is advertising as an LDAP server
         The DC INADC02 is advertising as having a writeable directory
         The DC INADC02 is advertising as a Key Distribution Center
         The DC INADC02 is advertising as a time server
         The DS INADC02 is advertising as a GC.
         ......................... INADC02 passed test Advertising
      Starting test: KnowsOfRoleHolders
         Role Schema Owner = CN=NTDS Settings,CN=INADC01,CN=Servers,CN=Carlsbad,CN=Sites,CN=Configuration,DC=inasoft,DC=com
         Role Domain Owner = CN=NTDS Settings,CN=INADC01,CN=Servers,CN=Carlsbad,CN=Sites,CN=Configuration,DC=inasoft,DC=com
         Role PDC Owner = CN=NTDS Settings,CN=INADC01,CN=Servers,CN=Carlsbad,CN=Sites,CN=Configuration,DC=inasoft,DC=com
         Role Rid Owner = CN=NTDS Settings,CN=INADC01,CN=Servers,CN=Carlsbad,CN=Sites,CN=Configuration,DC=inasoft,DC=com
         Role Infrastructure Update Owner = CN=NTDS Settings,CN=INADC01,CN=Servers,CN=Carlsbad,CN=Sites,CN=Configuration,DC=inasoft,DC=com
         ......................... INADC02 passed test KnowsOfRoleHolders
      Starting test: RidManager
         * Available RID Pool for the Domain is 3101 to 1073741823
         * inadc01.inasoft.com is the RID Master
         * DsBind with RID Master was successful
         * rIDAllocationPool is 2601 to 3100
         * rIDNextRID: 2611
         * rIDPreviousAllocationPool is 2601 to 3100
         ......................... INADC02 passed test RidManager
      Starting test: MachineAccount
         * SPN found :LDAP/inadc02.inasoft.com/inasoft.com
         * SPN found :LDAP/inadc02.inasoft.com
         * SPN found :LDAP/INADC02
         * SPN found :LDAP/inadc02.inasoft.com/INASOFT
         * SPN found :LDAP/4e9b2b3c-d058-450b-a76f-23277550772e._msdcs.inasoft.com
         * SPN found :E3514235-4B06-11D1-AB04-00C04FC2DCD2/4e9b2b3c-d058-450b-a76f-23277550772e/inasoft.com
         * SPN found :HOST/inadc02.inasoft.com/inasoft.com
         * SPN found :HOST/inadc02.inasoft.com
         * SPN found :HOST/INADC02
         * SPN found :HOST/inadc02.inasoft.com/INASOFT
         * SPN found :GC/inadc02.inasoft.com/inasoft.com
         ......................... INADC02 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
         ......................... INADC02 passed test Services
      Starting test: OutboundSecureChannels
         * The Outbound Secure Channels test
         ** Did not run Outbound Secure Channels test
         because /testdomain: was not entered
         ......................... INADC02 passed test OutboundSecureChannels
      Starting test: ObjectsReplicated
         INADC02 is in domain DC=inasoft,DC=com
         Checking for CN=INADC02,OU=Domain Controllers,DC=inasoft,DC=com in domain DC=inasoft,DC=com on 4 servers
            Object is up-to-date on all servers.
         Checking for CN=NTDS Settings,CN=INADC02,CN=Servers,CN=Carlsbad,CN=Sites,CN=Configuration,DC=inasoft,DC=com in domain CN=Configuration,DC=inasoft,DC=com on 4 servers
            Authoritative attribute hasPartialReplicaNCs on INADC01 (writeable)
               usnLocalChange = 2671787
               LastOriginatingDsa = INADC02
               usnOriginatingChange = 219294
               timeLastOriginatingChange = 2004-09-28 14:33.19
               VersionLastOriginatingChange = 5
            Out-of-date attribute hasPartialReplicaNCs on NJDC02 (writeable)
               usnLocalChange = 134790
               LastOriginatingDsa = INADC02
               usnOriginatingChange = 31274
               timeLastOriginatingChange = 2004-08-25 16:31.03
               VersionLastOriginatingChange = 3
            Authoritative attribute options on INADC02 (writeable)
               usnLocalChange = 219286
               LastOriginatingDsa = INADC02
               usnOriginatingChange = 219286
               timeLastOriginatingChange = 2004-09-28 14:33.19
               VersionLastOriginatingChange = 5
            Out-of-date attribute options on NJDC02 (writeable)
               usnLocalChange = 134790
               LastOriginatingDsa = INADC02
               usnOriginatingChange = 31265
               timeLastOriginatingChange = 2004-08-25 16:31.01
               VersionLastOriginatingChange = 3
         ......................... INADC02 failed test ObjectsReplicated
      Starting test: frssysvol
         * The File Replication Service Event log test
         The SYSVOL has been shared, and the AD is no longer
         prevented from starting by the File Replication Service.
         An Warning Event occured.  EventID: 0x800034FA
            Time Generated: 09/28/2004   14:59:54
            Event String: Following is the summary of warnings and errors

encountered by File Replication Service while

polling the Domain Controller inadc02.inasoft.com

for FRS replica set configuration information.

 



The nTDSConnection object cn=6c43f7fa-d819-42fc-ac69-f6aa992f4422,cn=ntds settings,cn=inadc02,cn=servers,cn=carlsbad,cn=sites,cn=configuration,dc=inasoft,dc=com is conflicting with cn=inadc01,cn=ntds settings,cn=inadc02,cn=servers,cn=carlsbad,cn=sites,cn=configuration,dc=inasoft,dc=com. Using cn=6c43f7fa-d819-42fc-ac69-f6aa992f4422,cn=ntds settings,cn=inadc02,cn=servers,cn=carlsbad,cn=sites,cn=configuration,dc=inasoft,dc=com





 
         ......................... INADC02 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.
         ......................... INADC02 passed test kccevent
      Starting test: systemlog
         * The System Event log test
         Found no errors in System Event log in the last 60 minutes.
         ......................... INADC02 passed test systemlog
   
   Running enterprise tests on : inasoft.com
      Starting test: Intersite
         Doing intersite inbound replication test on site Carlsbad:
            Locating & Contacting Intersite Topology Generator (ISTG) ...
               The ISTG for site Carlsbad is: INADC02.
            Checking for down bridgeheads ...
               Bridghead China\NJDC01 is up and replicating fine.
               Bridghead Carlsbad\INADC01 is up and replicating fine.
            Doing in depth site analysis ...
               All expected sites and bridgeheads are replicating into site

               Carlsbad.
         Doing intersite inbound replication test on site China:
            Locating & Contacting Intersite Topology Generator (ISTG) ...
               The ISTG for site China is: NJDC02.
            Checking for down bridgeheads ...
               Bridghead Carlsbad\INADC01 is up and replicating fine.
               *Warning: Remote bridgehead China\NJDC01 is not eligible as a

               bridgehead due to too many failures.  Replication may be

               disrupted into the local site China.
            Doing in depth site analysis ...
               Remote site Carlsbad is replicating to the local site China the

               writeable NC Schema correctly.
               Remote site Carlsbad is replicating to the local site China the

               writeable NC Configuration correctly.
               ***Error: The remote site Carlsbad, has no servers that can act

               as bridgeheads between the Carlsbad and the local site China for

               the writeable NC inasoft.  Replication will not continue until

               this is resolved.
         ......................... inasoft.com passed test Intersite
      Starting test: FsmoCheck
         GC Name: \\inadc01.inasoft.com
         Locator Flags: 0xe00001fd
         PDC Name: \\inadc01.inasoft.com
         Locator Flags: 0xe00001fd
         Time Server Name: \\inadc01.inasoft.com
         Locator Flags: 0xe00001fd
         Preferred Time Server Name: \\inadc01.inasoft.com
         Locator Flags: 0xe00001fd
         KDC Name: \\inadc01.inasoft.com
         Locator Flags: 0xe00001fd
         ......................... inasoft.com passed test FsmoCheck
0
 
LVL 3

Expert Comment

by:DanGilbertTX
Comment Utility
Ok, after looking at the dcdiag output, you are definitely having replication errors between your DCs. This is probably the reason you can't get the second node in the Cluster. I need to do a little more analyzing (when I have some time mainly) on the dcdiag output to find the solution to your replication issues. Once we fix those I am pretty sure that adding the second Cluster node will work.
0
What Should I Do With This Threat Intelligence?

Are you wondering if you actually need threat intelligence? The answer is yes. We explain the basics for creating useful threat intelligence.

 
LVL 3

Accepted Solution

by:
DanGilbertTX earned 250 total points
Comment Utility
Well, you definitely have some problems. I think the 2 main ones are DNS and Time Server.

You have your FSMO roles split between 2 servers. NJDC01 is running as your PDC emulator so it HAS to have W32time running. That service is shut down on the server right now. So, that needs to be turned back on. Active Directory uses time stamps to validate the information it sends out. To do that one machine must be the master time keeper. The PDC emulator gets that job. It ain't doing it at the moment and that is bad.

Second, your DNS seems to be a problem. None of the machines are registering AD correctly. The most common cause of this is that you don't have the DCs pointed to the same DNS server inside YOUR environment. You should be running Dynamic DNS on at least one of your DCs. The DCs need to have their IP stack setup to point to that DNS server and NOT an upstream providor. So, go in to My Network Places, Properties, Local Area Connection, TCP/IP and see what you have in Preferred DNS Server. It should be pointing to the one DNS server you setup. Now, since you have 2 sites (California and China) you can point the Chinese servers at the one server over there doing DNS and the California ones at the server doing DNS there. DO NOT PUT THE UPSTREAM PROVIDER anywhere in the IP stack. That is what forwarding is for in DNS Server.

NOTE: You don't actually have to reboot the server to get it to re-register the DNS and AD stuff. Just stop and restart the NETLOGON service and that will re-register all the AD stuff once you have the correct DNS settings in the IP stack.


Ok, so does any of this make sense? You are going to need to take care of these issues before you can do pretty much anything else in AD.
0
 
LVL 18

Expert Comment

by:exx1976
Comment Utility
Or to register the dns stuff, you could just say         ipconfig /registerdns


-exx
0
 
LVL 3

Expert Comment

by:DanGilbertTX
Comment Utility
No, ipconfig /registerdns only registers the host name (A record and PTR). You have to restart NETLOGON for all of the Active Directory registration (SRV records).
0
 
LVL 18

Expert Comment

by:exx1976
Comment Utility
Oh...  Learn something new every day.   :)
0
 
LVL 3

Expert Comment

by:DanGilbertTX
Comment Utility
One of the really cool things about NETLOGON and AD is the SRV records. More specifically if your Forward Lookup Zone in DNS is AD-Integrated you can delete the whole zone (just click delete) and then restart NETLOGON and it will repopulate DNS for you. All of the AD-Integrated stuff will come back. So, if you accidentally delete something, stop NETLOGON and the restart it. Should repopulate all the DNS settings. Need to do that before it gets a chance to replicate those changes out, but if done quick enough then it works.
0
 
LVL 3

Expert Comment

by:DanGilbertTX
Comment Utility
Just wanted to check in and see how things are going? You get your AD issues fixed yet? Any more problems?
0
 

Author Comment

by:gpietila
Comment Utility
I have not been able to try your suggestions because the company ceased operations last week & I am out of a job. I am quite sure DanGilbertTX was on the right track so he gets the win.
0
 
LVL 3

Expert Comment

by:DanGilbertTX
Comment Utility
I am sorry to hear about the job. Monster, DICE, and HotJobs. Those are probably the best 3 job sites to post on. Good luck with the job hunt.
0

Featured Post

Get up to 2TB FREE CLOUD per backup license!

An exclusive Black Friday offer just for Expert Exchange audience! Buy any of our top-rated backup solutions & get up to 2TB free cloud per system! Perform local & cloud backup in the same step, and restore instantly—anytime, anywhere. Grab this deal now before it disappears!

Join & Write a Comment

Replication has always been one of those technologies that people run scared from. The main reason is usually cost. When you think of replication, your mind drifts to solutions that replicate from one disk frame to another using block level technolo…
A Bare Metal Image backup allows for the restore of an entire system to a similar or dissimilar hardware. They are highly useful for migrations and disaster recovery. Bare Metal Image backups support Full and Incremental backups. Differential backup…
To efficiently enable the rotation of USB drives for backups, storage pools need to be created. This way no matter which USB drive is installed, the backups will successfully write without any administrative intervention. Multiple USB devices need t…
This tutorial will walk an individual through configuring a drive on a Windows Server 2008 to perform shadow copies in order to quickly recover deleted files and folders. Click on Start and then select Computer to view the available drives on the se…

762 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

Need Help in Real-Time?

Connect with top rated Experts

11 Experts available now in Live!

Get 1:1 Help Now