Problemas de replicacion

Buenas tardes,

Tengo un controlador de dominio principal (SERVER A) en una CIUDAD A y otro
controlador de dominio adicional (SERVER B) en una CIUDAD B, ambos estan
conectados a traves de enlaces frame-relay de 64K, (los sitios estan creados
y las subredes respectivas tambien), la replicacion entre estos servidores
funciona perfectamente.

Recientemente se configuro un controlador de dominio adicional (SERVER C)
para instalarlo en una CIUDAD C, este proceso de configuracion se hizo en la
misma ciudad (CIUDAD A) para que no hubiesen problemas de ancho de banda
debido a la primera replicacion cuando se instala el dcpromo, despues se
llevo el (SERVER C) a la localidad remota (CIUDAD C) y se conecto con la
(CIUDAD A) a traves de un enlace frame-relay de 64K. (se creo el sitio y la
subred respectiva). El SERVER C estuvo desconectado del SERVER A
aproximadamente 50 dias.

El problema es el siguiente:

El SERVER A no replica ahora con el SERVER C a pesar de que existe
conectividad
y no hay ningun firewall filtrando la comunicacion entre estos dos servidores.

S.O Instalado: Windows Server 2003 SP1 (en todos los servers)

Corri el comando DCDIAG y NETDIAG en ambos servidores y el resultado es el
siguiente:


SERVER A: (Controlador de Dominio principal, tiene todos los roles)



Domain Controller Diagnosis

Performing initial setup:
Done gathering initial info.

Doing initial required tests

Testing server: CCS\SERVER A
Starting test: Connectivity
. SERVER A passed test Connectivity

Doing primary tests

Testing server: CCS\SERVER A
Starting test: Replications
[Replications Check,SERVER A] A recent replication attempt failed:
From SERVER C to SERVER A
Naming Context: DC=ForestDnsZones,DC=dominio,DC=com,DC=ve
The replication generated an error (8418):
The replication operation failed because of a schema mismatch
between the servers involved.
The failure occurred at 2007-09-21 11:50:46.
The last success occurred at 2007-07-03 17:45:37.
597 failures have occurred since the last success.

[Replications Check,SERVER A] A recent replication attempt failed:
From SERVER C to SERVER A
Naming Context: DC=DomainDnsZones,DC=dominio,DC=com,DC=ve
The replication generated an error (8418):
The replication operation failed because of a schema mismatch
between the servers involved.
The failure occurred at 2007-09-21 11:50:45.
The last success occurred at 2007-07-03 17:45:37.
597 failures have occurred since the last success.

[Replications Check,SERVER A] A recent replication attempt failed:
From SERVER C to SERVER A
Naming Context: CN=Configuration,DC=dominio,DC=com,DC=ve
The replication generated an error (8418):
The replication operation failed because of a schema mismatch
between the servers involved.
The failure occurred at 2007-09-21 11:50:41.
The last success occurred at 2007-07-03 17:45:36.
597 failures have occurred since the last success.

[Replications Check,SERVER A] A recent replication attempt failed:
From SERVER C to SERVER A
Naming Context: DC=dominio,DC=com,DC=ve
The replication generated an error (8418):
The replication operation failed because of a schema mismatch
between the servers involved.
The failure occurred at 2007-09-21 11:50:40.
The last success occurred at 2007-07-03 17:45:36.
597 failures have occurred since the last success.

REPLICATION-RECEIVED LATENCY WARNING
SERVER A: Current time is 2007-09-21 13:52:15.
DC=ForestDnsZones,DC=dominio,DC=com,DC=ve
Last replication recieved from SERVER C at 2007-07-03 17:45:37.
DC=DomainDnsZones,DC=dominio,DC=com,DC=ve
Last replication recieved from SERVER C at 2007-07-03 17:45:37.
CN=Configuration,DC=dominio,DC=com,DC=ve
Last replication recieved from SERVER C at 2007-07-03 17:45:36.
DC=dominio,DC=com,DC=ve
Last replication recieved from SERVER C at 2007-07-03 17:45:36.
REPLICATION-RECEIVED LATENCY WARNING
Source site:
CN=NTDS Site
Settings,CN=VAL,CN=Sites,CN=Configuration,DC=dominio,DC=com,DC=ve
Current time: 2007-09-21 13:52:15
Last update time: 2007-07-03 17:41:04
Check if source site has an elected ISTG running.
Check replication from source site to this server.

. SERVER A passed test Replications
Starting test: NCSecDesc
. SERVER A passed test NCSecDesc
Starting test: NetLogons
. SERVER A passed test NetLogons
Starting test: Advertising
. SERVER A passed test Advertising
Starting test: KnowsOfRoleHolders
. SERVER A passed test KnowsOfRoleHolders
Starting test: RidManager
. SERVER A passed test RidManager
Starting test: MachineAccount
* The current DC is not in the domain controller's OU
. SERVER A failed test MachineAccount
Starting test: Services
. SERVER A passed test Services
Starting test: ObjectsReplicated
. SERVER A passed test ObjectsReplicated
Starting test: frssysvol
. SERVER A passed test frssysvol
Starting test: frsevent
There are warning or error events within the last 24 hours after the
SYSVOL has been shared. Failing SYSVOL replication problems may
cause
Group Policy problems.
. SERVER A failed test frsevent
Starting test: kccevent
. SERVER A passed test kccevent
Starting test: systemlog
An Error Event occured. EventID: 0x00000457
Time Generated: 09/21/2007 13:51:33
(Event String could not be retrieved)
An Error Event occured. EventID: 0x00000457
Time Generated: 09/21/2007 13:51:36
(Event String could not be retrieved)

. SERVER A failed test systemlog
Starting test: VerifyReferences
. SERVER A passed test VerifyReferences

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

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

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

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

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

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




SERVER C (controlador de dominio adicional)



Domain Controller Diagnosis

Performing initial setup:
Done gathering initial info.

Doing initial required tests

Testing server: VAL\SERVER C
Starting test: Connectivity
. SERVER C passed test Connectivity

Doing primary tests

Testing server: VAL\SERVER C
Starting test: Replications
[Replications Check,SERVER C] A recent replication attempt failed:
From SERVER A to SERVER C
Naming Context: DC=DomainDnsZones,DC=DOMINIO,DC=com,DC=ve
The replication generated an error (1256):
The remote system is not available. For information about
network troubleshooting, see Windows Help.
The failure occurred at 2007-09-21 11:57:22.
The last success occurred at 2007-07-03 17:43:28.
633 failures have occurred since the last success.

[Replications Check,SERVER C] A recent replication attempt failed:
From SERVER A to SERVER C
Naming Context: DC=ForestDnsZones,DC=DOMINIO,DC=com,DC=ve
The replication generated an error (1256):
The remote system is not available. For information about
network troubleshooting, see Windows Help.
The failure occurred at 2007-09-21 11:57:22.
The last success occurred at 2007-07-03 17:43:28.
633 failures have occurred since the last success.

[Replications Check,SERVER C] A recent replication attempt failed:
From SERVER A to SERVER C
Naming Context: CN=Schema,CN=Configuration,DC=DOMINIO,DC=com,DC=ve
The replication generated an error (-2146893022):
The target principal name is incorrect.
The failure occurred at 2007-09-21 11:57:24.
The last success occurred at 2007-07-03 17:43:28.
633 failures have occurred since the last success.

[Replications Check,SERVER C] A recent replication attempt failed:
From SERVER A to SERVER C
Naming Context: CN=Configuration,DC=DOMINIO,DC=com,DC=ve
The replication generated an error (-2146893022):
The target principal name is incorrect.
The failure occurred at 2007-09-21 11:57:23.
The last success occurred at 2007-07-03 17:43:28.
633 failures have occurred since the last success.

[Replications Check,SERVER C] A recent replication attempt failed:
From SERVER A to SERVER C
Naming Context: DC=DOMINIO,DC=com,DC=ve
The replication generated an error (-2146893022):
The target principal name is incorrect.
The failure occurred at 2007-09-21 11:57:22.
The last success occurred at 2007-07-03 17:43:28.
633 failures have occurred since the last success.

REPLICATION-RECEIVED LATENCY WARNING
SERVER C: Current time is 2007-09-21 12:13:00.
DC=DomainDnsZones,DC=DOMINIO,DC=com,DC=ve
Last replication recieved from SERVER A at 2007-07-03 17:43:28.
Last replication recieved from SERVER A2 at 2007-07-03
17:42:47.
DC=ForestDnsZones,DC=DOMINIO,DC=com,DC=ve
Last replication recieved from SERVER A at 2007-07-03 17:43:28.
Last replication recieved from SERVER A2 at 2007-07-03
16:55:44.
CN=Schema,CN=Configuration,DC=DOMINIO,DC=com,DC=ve
Last replication recieved from SERVER A at 2007-07-03 17:43:28.
Last replication recieved from SERVER A4 at 2007-01-22
11:56:00.
WARNING: This latency is over the Tombstone Lifetime of 180
days!
Last replication recieved from SERVER A3 at 2007-07-03
17:40:44.
Last replication recieved from SERVER A2 at 2007-07-03
16:59:34.
CN=Configuration,DC=DOMINIO,DC=com,DC=ve
Last replication recieved from SERVER A at 2007-07-03 17:43:28.
Last replication recieved from SERVER A4 at 2007-01-22
16:24:54.
WARNING: This latency is over the Tombstone Lifetime of 180
days!
Last replication recieved from SERVER A3 at 2007-07-03
17:40:44.
Last replication recieved from SERVER A2 at 2007-07-03
17:39:44.
DC=DOMINIO,DC=com,DC=ve
Last replication recieved from SERVER A at 2007-07-03 17:43:28.
Last replication recieved from SERVER A4 at 2007-01-22
16:26:00.
WARNING: This latency is over the Tombstone Lifetime of 180
days!
Last replication recieved from SERVER A3 at 2007-07-03
17:40:44.
Last replication recieved from SERVER A2 at 2007-07-03
17:40:14.

REPLICATION-RECEIVED LATENCY WARNING

Source site:

CN=NTDS Site
Settings,CNÌS,CN=Sites,CN=Configuration,DC=DOMINIO,DC=com,DC=ve

Current time: 2007-09-21 12:13:00

Last update time: 2007-07-03 17:20:11

Check if source site has an elected ISTG running.

Check replication from source site to this server.
. SERVER C passed test Replications
Starting test: NCSecDesc
. SERVER C passed test NCSecDesc
Starting test: NetLogons
. SERVER C passed test NetLogons
Starting test: Advertising
. SERVER C passed test Advertising
Starting test: KnowsOfRoleHolders
[SERVER A] DsBindWithSpnEx() failed with error -2146893022,
The target principal name is incorrect..
Warning: SERVER A is the Schema Owner, but is not responding to DS
RPC Bind.
[SERVER A] LDAP bind failed with error 8341,
A directory service error has occurred..
Warning: SERVER A is the Schema Owner, but is not responding to
LDAP Bind.
Warning: SERVER A is the Domain Owner, but is not responding to DS
RPC Bind.
Warning: SERVER A is the Domain Owner, but is not responding to
LDAP Bind.
Warning: SERVER A is the PDC Owner, but is not responding to DS RPC
Bind.
Warning: SERVER A is the PDC Owner, but is not responding to LDAP
Bind.
Warning: SERVER A is the Rid Owner, but is not responding to DS RPC
Bind.
Warning: SERVER A is the Rid Owner, but is not responding to LDAP
Bind.
Warning: SERVER A is the Infrastructure Update Owner, but is not
responding to DS RPC Bind.
Warning: SERVER A is the Infrastructure Update Owner, but is not
responding to LDAP Bind.

. SERVER C failed test KnowsOfRoleHolders
Starting test: RidManager
. SERVER C failed test RidManager
Starting test: MachineAccount
. SERVER C passed test MachineAccount
Starting test: Services
. SERVER C passed test Services
Starting test: ObjectsReplicated
. SERVER C passed test ObjectsReplicated
Starting test: frssysvol
. SERVER C passed test frssysvol
Starting test: frsevent

There are warning or error events within the last 24 hours after the

SYSVOL has been shared. Failing SYSVOL replication problems may
cause

Group Policy problems.
. SERVER C failed test frsevent
Starting test: kccevent
An Warning Event occured. EventID: 0x8000061E
Time Generated: 09/21/2007 12:02:21
Event String: All domain controllers in the following site that

An Error Event occured. EventID: 0xC000051F
Time Generated: 09/21/2007 12:02:21
Event String: The Knowledge Consistency Checker (KCC) has

An Warning Event occured. EventID: 0x80000749
Time Generated: 09/21/2007 12:02:21
Event String: The Knowledge Consistency Checker (KCC) was

An Warning Event occured. EventID: 0x8000061E
Time Generated: 09/21/2007 12:02:21
Event String: All domain controllers in the following site that

An Error Event occured. EventID: 0xC000051F
Time Generated: 09/21/2007 12:02:21
Event String: The Knowledge Consistency Checker (KCC) has

An Warning Event occured. EventID: 0x80000749
Time Generated: 09/21/2007 12:02:21
Event String: The Knowledge Consistency Checker (KCC) was

An Warning Event occured. EventID: 0x8000061E
Time Generated: 09/21/2007 12:02:21
Event String: All domain controllers in the following site that

An Error Event occured. EventID: 0xC000051F
Time Generated: 09/21/2007 12:02:21
Event String: The Knowledge Consistency Checker (KCC) has

An Warning Event occured. EventID: 0x80000749
Time Generated: 09/21/2007 12:02:21
Event String: The Knowledge Consistency Checker (KCC) was

An Warning Event occured. EventID: 0x8000061E
Time Generated: 09/21/2007 12:02:21
Event String: All domain controllers in the following site that

An Error Event occured. EventID: 0xC000051F
Time Generated: 09/21/2007 12:02:21
Event String: The Knowledge Consistency Checker (KCC) has

An Warning Event occured. EventID: 0x80000749
Time Generated: 09/21/2007 12:02:21
Event String: The Knowledge Consistency Checker (KCC) was

. SERVER C failed test kccevent
Starting test: systemlog
An Error Event occured. EventID: 0x40000004
Time Generated: 09/21/2007 11:57:22
Event String: The kerberos client received a

An Error Event occured. EventID: 0x40000004
Time Generated: 09/21/2007 12:06:17
Event String: The kerberos client received a

An Error Event occured. EventID: 0x40000004
Time Generated: 09/21/2007 12:12:05
Event String: The kerberos client received a

An Error Event occured. EventID: 0x40000004
Time Generated: 09/21/2007 12:12:07
Event String: The kerberos client received a

. SERVER C failed test systemlog
Starting test: VerifyReferences
. SERVER C passed test VerifyReferences

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

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

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

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

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

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



Lo que pude observar es lo siguiente:

Que en el SERVER A se genera el siguiente error:

The replication operation failed because of a schema mismatch between the
servers involved

Y en el SERVER C se genera este:

The target principal name is incorrect

Como puedo resolver esto? de antemano muchas gracias por la ayuda

Saludos

A ver si te sirve:

"Schema mismatch" error message occurs when you try to run the Active Directory Installation Wizard (Dcpromo.exe) in Windows Server 2003 or in Windows 2000
http://support.microsoft.com/kb/838179

Active Directory replication delayed when indexed attributes rebuilt during schema upgrade
http://support.microsoft.com/kb/307323

También veo este error

" Starting test: MachineAccount
* The current DC is not in the domain controller's OU"

"The current DC is not in the domain controller's OU" error message when you run the Dcdiag tool
http://support.microsoft.com/kb/833436

Qué más dice el Visor de sucesos?


Saludos,

Marc
MVP Windows Server System - Directory Services
MCSA Windows Server 2003
Citrix CCA
Oracle9i Certified Associate (OCA)

Este mensaje se proporciona "como está" sin garantías de ninguna clase, y no otorga ningún derecho.

This posting is provided "AS IS" with no warranties, and confers no rights. You assume all risk for your use.

"Carlos" escribió en el mensaje news:
> Buenas tardes,
>
> Tengo un controlador de dominio principal (SERVER A) en una CIUDAD A y otro
> controlador de dominio adicional (SERVER B) en una CIUDAD B, ambos estan
> conectados a traves de enlaces frame-relay de 64K, (los sitios estan creados
> y las subredes respectivas tambien), la replicacion entre estos servidores
> funciona perfectamente.
>
> Recientemente se configuro un controlador de dominio adicional (SERVER C)
> para instalarlo en una CIUDAD C, este proceso de configuracion se hizo en la
> misma ciudad (CIUDAD A) para que no hubiesen problemas de ancho de banda
> debido a la primera replicacion cuando se instala el dcpromo, despues se
> llevo el (SERVER C) a la localidad remota (CIUDAD C) y se conecto con la
> (CIUDAD A) a traves de un enlace frame-relay de 64K. (se creo el sitio y la
> subred respectiva). El SERVER C estuvo desconectado del SERVER A
> aproximadamente 50 dias.
>
> El problema es el siguiente:
>
> El SERVER A no replica ahora con el SERVER C a pesar de que existe
> conectividad
> y no hay ningun firewall filtrando la comunicacion entre estos dos servidores.
>
> S.O Instalado: Windows Server 2003 SP1 (en todos los servers)
>
> Corri el comando DCDIAG y NETDIAG en ambos servidores y el resultado es el
> siguiente:
>
>
> SERVER A: (Controlador de Dominio principal, tiene todos los roles)
>
>
>
> Domain Controller Diagnosis
>
> Performing initial setup:
> Done gathering initial info.
>
> Doing initial required tests
>
> Testing server: CCS\SERVER A
> Starting test: Connectivity
> . SERVER A passed test Connectivity
>
> Doing primary tests
>
> Testing server: CCS\SERVER A
> Starting test: Replications
> [Replications Check,SERVER A] A recent replication attempt failed:
> From SERVER C to SERVER A
> Naming Context: DC=ForestDnsZones,DC=dominio,DC=com,DC=ve
> The replication generated an error (8418):
> The replication operation failed because of a schema mismatch
> between the servers involved.
> The failure occurred at 2007-09-21 11:50:46.
> The last success occurred at 2007-07-03 17:45:37.
> 597 failures have occurred since the last success.
>
> [Replications Check,SERVER A] A recent replication attempt failed:
> From SERVER C to SERVER A
> Naming Context: DC=DomainDnsZones,DC=dominio,DC=com,DC=ve
> The replication generated an error (8418):
> The replication operation failed because of a schema mismatch
> between the servers involved.
> The failure occurred at 2007-09-21 11:50:45.
> The last success occurred at 2007-07-03 17:45:37.
> 597 failures have occurred since the last success.
>
> [Replications Check,SERVER A] A recent replication attempt failed:
> From SERVER C to SERVER A
> Naming Context: CN=Configuration,DC=dominio,DC=com,DC=ve
> The replication generated an error (8418):
> The replication operation failed because of a schema mismatch
> between the servers involved.
> The failure occurred at 2007-09-21 11:50:41.
> The last success occurred at 2007-07-03 17:45:36.
> 597 failures have occurred since the last success.
>
> [Replications Check,SERVER A] A recent replication attempt failed:
> From SERVER C to SERVER A
> Naming Context: DC=dominio,DC=com,DC=ve
> The replication generated an error (8418):
> The replication operation failed because of a schema mismatch
> between the servers involved.
> The failure occurred at 2007-09-21 11:50:40.
> The last success occurred at 2007-07-03 17:45:36.
> 597 failures have occurred since the last success.
>
> REPLICATION-RECEIVED LATENCY WARNING
> SERVER A: Current time is 2007-09-21 13:52:15.
> DC=ForestDnsZones,DC=dominio,DC=com,DC=ve
> Last replication recieved from SERVER C at 2007-07-03 17:45:37.
> DC=DomainDnsZones,DC=dominio,DC=com,DC=ve
> Last replication recieved from SERVER C at 2007-07-03 17:45:37.
> CN=Configuration,DC=dominio,DC=com,DC=ve
> Last replication recieved from SERVER C at 2007-07-03 17:45:36.
> DC=dominio,DC=com,DC=ve
> Last replication recieved from SERVER C at 2007-07-03 17:45:36.
> REPLICATION-RECEIVED LATENCY WARNING
> Source site:
> CN=NTDS Site
> Settings,CN=VAL,CN=Sites,CN=Configuration,DC=dominio,DC=com,DC=ve
> Current time: 2007-09-21 13:52:15
> Last update time: 2007-07-03 17:41:04
> Check if source site has an elected ISTG running.
> Check replication from source site to this server.
>
> . SERVER A passed test Replications
> Starting test: NCSecDesc
> . SERVER A passed test NCSecDesc
> Starting test: NetLogons
> . SERVER A passed test NetLogons
> Starting test: Advertising
> . SERVER A passed test Advertising
> Starting test: KnowsOfRoleHolders
> . SERVER A passed test KnowsOfRoleHolders
> Starting test: RidManager
> . SERVER A passed test RidManager
> Starting test: MachineAccount
> * The current DC is not in the domain controller's OU
> . SERVER A failed test MachineAccount
> Starting test: Services
> . SERVER A passed test Services
> Starting test: ObjectsReplicated
> . SERVER A passed test ObjectsReplicated
> Starting test: frssysvol
> . SERVER A passed test frssysvol
> Starting test: frsevent
> There are warning or error events within the last 24 hours after the
> SYSVOL has been shared. Failing SYSVOL replication problems may
> cause
> Group Policy problems.
> . SERVER A failed test frsevent
> Starting test: kccevent
> . SERVER A passed test kccevent
> Starting test: systemlog
> An Error Event occured. EventID: 0x00000457
> Time Generated: 09/21/2007 13:51:33
> (Event String could not be retrieved)
> An Error Event occured. EventID: 0x00000457
> Time Generated: 09/21/2007 13:51:36
> (Event String could not be retrieved)
>
> . SERVER A failed test systemlog
> Starting test: VerifyReferences
> . SERVER A passed test VerifyReferences
>
> Running partition tests on : ForestDnsZones
> Starting test: CrossRefValidation
> . ForestDnsZones passed test
> CrossRefValidation
> Starting test: CheckSDRefDom
> . ForestDnsZones passed test CheckSDRefDom
>
> Running partition tests on : DomainDnsZones
> Starting test: CrossRefValidation
> . DomainDnsZones passed test
> CrossRefValidation
> Starting test: CheckSDRefDom
> . DomainDnsZones passed test CheckSDRefDom
>
> Running partition tests on : Schema
> Starting test: CrossRefValidation
> . Schema passed test CrossRefValidation
> Starting test: CheckSDRefDom
> . Schema passed test CheckSDRefDom
>
> Running partition tests on : Configuration
> Starting test: CrossRefValidation
> . Configuration passed test
> CrossRefValidation
> Starting test: CheckSDRefDom
> . Configuration passed test CheckSDRefDom
>
> Running partition tests on : dominio
> Starting test: CrossRefValidation
> . dominio passed test CrossRefValidation
> Starting test: CheckSDRefDom
> . dominio passed test CheckSDRefDom
>
> Running enterprise tests on : dominio.com.ve
> Starting test: Intersite
> . dominio.com.ve passed test Intersite
> Starting test: FsmoCheck
> . dominio.com.ve passed test FsmoCheck
>
>
>
>
> SERVER C (controlador de dominio adicional)
>
>
>
> Domain Controller Diagnosis
>
> Performing initial setup:
> Done gathering initial info.
>
> Doing initial required tests
>
> Testing server: VAL\SERVER C
> Starting test: Connectivity
> . SERVER C passed test Connectivity
>
> Doing primary tests
>
> Testing server: VAL\SERVER C
> Starting test: Replications
> [Replications Check,SERVER C] A recent replication attempt failed:
> From SERVER A to SERVER C
> Naming Context: DC=DomainDnsZones,DC=DOMINIO,DC=com,DC=ve
> The replication generated an error (1256):
> The remote system is not available. For information about
> network troubleshooting, see Windows Help.
> The failure occurred at 2007-09-21 11:57:22.
> The last success occurred at 2007-07-03 17:43:28.
> 633 failures have occurred since the last success.
>
> [Replications Check,SERVER C] A recent replication attempt failed:
> From SERVER A to SERVER C
> Naming Context: DC=ForestDnsZones,DC=DOMINIO,DC=com,DC=ve
> The replication generated an error (1256):
> The remote system is not available. For information about
> network troubleshooting, see Windows Help.
> The failure occurred at 2007-09-21 11:57:22.
> The last success occurred at 2007-07-03 17:43:28.
> 633 failures have occurred since the last success.
>
> [Replications Check,SERVER C] A recent replication attempt failed:
> From SERVER A to SERVER C
> Naming Context: CN=Schema,CN=Configuration,DC=DOMINIO,DC=com,DC=ve
> The replication generated an error (-2146893022):
> The target principal name is incorrect.
> The failure occurred at 2007-09-21 11:57:24.
> The last success occurred at 2007-07-03 17:43:28.
> 633 failures have occurred since the last success.
>
> [Replications Check,SERVER C] A recent replication attempt failed:
> From SERVER A to SERVER C
> Naming Context: CN=Configuration,DC=DOMINIO,DC=com,DC=ve
> The replication generated an error (-2146893022):
> The target principal name is incorrect.
> The failure occurred at 2007-09-21 11:57:23.
> The last success occurred at 2007-07-03 17:43:28.
> 633 failures have occurred since the last success.
>
> [Replications Check,SERVER C] A recent replication attempt failed:
> From SERVER A to SERVER C
> Naming Context: DC=DOMINIO,DC=com,DC=ve
> The replication generated an error (-2146893022):
> The target principal name is incorrect.
> The failure occurred at 2007-09-21 11:57:22.
> The last success occurred at 2007-07-03 17:43:28.
> 633 failures have occurred since the last success.
>
> REPLICATION-RECEIVED LATENCY WARNING
> SERVER C: Current time is 2007-09-21 12:13:00.
> DC=DomainDnsZones,DC=DOMINIO,DC=com,DC=ve
> Last replication recieved from SERVER A at 2007-07-03 17:43:28.
> Last replication recieved from SERVER A2 at 2007-07-03
> 17:42:47.
> DC=ForestDnsZones,DC=DOMINIO,DC=com,DC=ve
> Last replication recieved from SERVER A at 2007-07-03 17:43:28.
> Last replication recieved from SERVER A2 at 2007-07-03
> 16:55:44.
> CN=Schema,CN=Configuration,DC=DOMINIO,DC=com,DC=ve
> Last replication recieved from SERVER A at 2007-07-03 17:43:28.

SERVER A (Principal) Event Viewer

Event Type: Error
Event Source: NTDS Replication
Event Category: Replication
Event ID: 1864
Date: 9/23/2007
Time: 7:20:12 PM
User: NT AUTHORITY\ANONYMOUS LOGON
Computer: SERVER A
Description:
This is the replication status for the following directory partition on the
local domain controller.

Directory partition:
DC=ForestDnsZones,DC=DOMINIO,DC=com,DC=ve

The local domain controller has not recently received replication
information from a number of domain controllers. The count of domain
controllers is shown, divided into the following intervals.

More than 24 hours:
1
More than a week:
1
More than one month:
1
More than two months:
1
More than a tombstone lifetime:
0
Tombstone lifetime (days):
180
Domain controllers that do not replicate in a timely manner may encounter
errors. It may miss password changes and be unable to authenticate. A DC that
has not replicated in a tombstone lifetime may have missed the deletion of
some objects, and may be automatically blocked from future replication until
it is reconciled.

To identify the domain controllers by name, install the support tools
included on the installation CD and run dcdiag.exe.
You can also use the support tool repadmin.exe to display the replication
latencies of the domain controllers in the forest.
The command is "repadmin /showvector /latency <partition-dn>".

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.


Una Advertencia


Event Type: Warning
Event Source: NtFrs
Event Category: None
Event ID: 13508
Date: 9/21/2007
Time: 5:07:30 PM
User: N/A
Computer: SERVER A
Description:
The File Replication Service is having trouble enabling replication from
SERVER C to SERVER A
for c:\windows\sysvol\domain using the DNS name SERVER C.DOMINIO.com.ve. FRS
will keep retrying.
Following are some of the reasons you would see this warning.

[1] FRS can not correctly resolve the DNS name SERVER C.DOMINIO.com.ve from
this computer.
[2] FRS is not running on SERVER C.DOMINIO.com.ve.
[3] The topology information in the Active Directory for this replica has
not yet replicated to all the Domain Controllers.

This event log message will appear once per connection, After the problem
is fixed you will see another event log message indicating that the
connection has been established.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data: 0000: 00 00 00 00


*******EN LA LOCALIDAD REMOTA SERVER C*********

Event Type: Error
Event Source: NTDS KCC
Event Category: Knowledge Consistency Checker
Event ID: 1311
Date: 9/24/2007
Time: 2:04:53 PM
User: NT AUTHORITY\ANONYMOUS LOGON
Computer: SERVER C
Description:
The Knowledge Consistency Checker (KCC) has detected problems with the
following directory partition.

Directory partition:
CN=Configuration,DC=DOMINIO,DC=com,DC=ve

There is insufficient site connectivity information in Active Directory
Sites and Services for the KCC to create a spanning tree replication
topology. Or, one or more domain controllers with this directory partition
are unable to replicate the directory partition information. This is probably
due to inaccessible domain controllers.

User Action
Use Active Directory Sites and Services to perform one of the following
actions:
- Publish sufficient site connectivity information so that the KCC can
determine a route by which this directory partition can reach this site. This
is the preferred option.
- Add a Connection object to a domain controller that contains the directory
partition in this site from a domain controller that contains the same
directory partition in another site.

If neither of the Active Directory Sites and Services tasks correct this
condition, see previous events logged by the KCC that
identify the inaccessible domain controllers.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.


Event Type: Warning
Event Source: NTDS KCC
Event Category: Knowledge Consistency Checker
Event ID: 1865
Date: 9/24/2007
Time: 2:04:53 PM
User: NT AUTHORITY\ANONYMOUS LOGON
Computer: SERVER C
Description:
The Knowledge Consistency Checker (KCC) was unable to form a complete
spanning tree network topology. As a result, the following list of sites
cannot be reached from the local site.

Sites:
CNÌS,CN=Sites,CN=Configuration,DC=redbancamiga,DC=com,DC=ve


For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.


Ya estoy verificando con lo que me enviaste, tan pronto aviso tan pronto
pueda.

Saludos


"Marc [MVP Windows]" wrote:

A ver si te sirve:

"Schema mismatch" error message occurs when you try to run the Active Directory Installation Wizard (Dcpromo.exe) in Windows Server 2003 or in Windows 2000
http://support.microsoft.com/kb/838179

Active Directory replication delayed when indexed attributes rebuilt during schema upgrade
http://support.microsoft.com/kb/307323

También veo este error

" Starting test: MachineAccount
* The current DC is not in the domain controller's OU"

"The current DC is not in the domain controller's OU" error message when you run the Dcdiag tool
http://support.microsoft.com/kb/833436

Qué más dice el Visor de sucesos?


Saludos,

Marc
MVP Windows Server System - Directory Services
MCSA Windows Server 2003
Citrix CCA
Oracle9i Certified Associate (OCA)

Este mensaje se proporciona "como está" sin garantías de ninguna clase, y no otorga ningún derecho.

This posting is provided "AS IS" with no warranties, and confers no rights. You assume all risk for your use.

"Carlos" escribió en el mensaje news:
> Buenas tardes,
>
> Tengo un controlador de dominio principal (SERVER A) en una CIUDAD A y otro
> controlador de dominio adicional (SERVER B) en una CIUDAD B, ambos estan
> conectados a traves de enlaces frame-relay de 64K, (los sitios estan creados
> y las subredes respectivas tambien), la replicacion entre estos servidores
> funciona perfectamente.
>
> Recientemente se configuro un controlador de dominio adicional (SERVER C)
> para instalarlo en una CIUDAD C, este proceso de configuracion se hizo en la
> misma ciudad (CIUDAD A) para que no hubiesen problemas de ancho de banda
> debido a la primera replicacion cuando se instala el dcpromo, despues se
> llevo el (SERVER C) a la localidad remota (CIUDAD C) y se conecto con la
> (CIUDAD A) a traves de un enlace frame-relay de 64K. (se creo el sitio y la
> subred respectiva). El SERVER C estuvo desconectado del SERVER A
> aproximadamente 50 dias.
>
> El problema es el siguiente:
>
> El SERVER A no replica ahora con el SERVER C a pesar de que existe
> conectividad
> y no hay ningun firewall filtrando la comunicacion entre estos dos servidores.
>
> S.O Instalado: Windows Server 2003 SP1 (en todos los servers)
>
> Corri el comando DCDIAG y NETDIAG en ambos servidores y el resultado es el
> siguiente:
>
>
> SERVER A: (Controlador de Dominio principal, tiene todos los roles)
>
>
>
> Domain Controller Diagnosis
>
> Performing initial setup:
> Done gathering initial info.
>
> Doing initial required tests
>
> Testing server: CCS\SERVER A
> Starting test: Connectivity
> . SERVER A passed test Connectivity
>
> Doing primary tests
>
> Testing server: CCS\SERVER A
> Starting test: Replications
> [Replications Check,SERVER A] A recent replication attempt failed:
> From SERVER C to SERVER A
> Naming Context: DC=ForestDnsZones,DC=dominio,DC=com,DC=ve
> The replication generated an error (8418):
> The replication operation failed because of a schema mismatch
> between the servers involved.
> The failure occurred at 2007-09-21 11:50:46.
> The last success occurred at 2007-07-03 17:45:37.
> 597 failures have occurred since the last success.
>
> [Replications Check,SERVER A] A recent replication attempt failed:
> From SERVER C to SERVER A
> Naming Context: DC=DomainDnsZones,DC=dominio,DC=com,DC=ve
> The replication generated an error (8418):
> The replication operation failed because of a schema mismatch
> between the servers involved.
> The failure occurred at 2007-09-21 11:50:45.
> The last success occurred at 2007-07-03 17:45:37.
> 597 failures have occurred since the last success.
>
> [Replications Check,SERVER A] A recent replication attempt failed:
> From SERVER C to SERVER A
> Naming Context: CN=Configuration,DC=dominio,DC=com,DC=ve
> The replication generated an error (8418):
> The replication operation failed because of a schema mismatch
> between the servers involved.
> The failure occurred at 2007-09-21 11:50:41.
> The last success occurred at 2007-07-03 17:45:36.
> 597 failures have occurred since the last success.
>
> [Replications Check,SERVER A] A recent replication attempt failed:
> From SERVER C to SERVER A
> Naming Context: DC=dominio,DC=com,DC=ve
> The replication generated an error (8418):
> The replication operation failed because of a schema mismatch
> between the servers involved.
> The failure occurred at 2007-09-21 11:50:40.
> The last success occurred at 2007-07-03 17:45:36.
> 597 failures have occurred since the last success.
>
> REPLICATION-RECEIVED LATENCY WARNING
> SERVER A: Current time is 2007-09-21 13:52:15.
> DC=ForestDnsZones,DC=dominio,DC=com,DC=ve
> Last replication recieved from SERVER C at 2007-07-03 17:45:37.
> DC=DomainDnsZones,DC=dominio,DC=com,DC=ve
> Last replication recieved from SERVER C at 2007-07-03 17:45:37.
> CN=Configuration,DC=dominio,DC=com,DC=ve
> Last replication recieved from SERVER C at 2007-07-03 17:45:36.
> DC=dominio,DC=com,DC=ve
> Last replication recieved from SERVER C at 2007-07-03 17:45:36.
> REPLICATION-RECEIVED LATENCY WARNING
> Source site:
> CN=NTDS Site
> Settings,CN=VAL,CN=Sites,CN=Configuration,DC=dominio,DC=com,DC=ve
> Current time: 2007-09-21 13:52:15
> Last update time: 2007-07-03 17:41:04
> Check if source site has an elected ISTG running.
> Check replication from source site to this server.
>
> . SERVER A passed test Replications
> Starting test: NCSecDesc
> . SERVER A passed test NCSecDesc
> Starting test: NetLogons
> . SERVER A passed test NetLogons
> Starting test: Advertising
> . SERVER A passed test Advertising
> Starting test: KnowsOfRoleHolders
> . SERVER A passed test KnowsOfRoleHolders
> Starting test: RidManager
> . SERVER A passed test RidManager
> Starting test: MachineAccount
> * The current DC is not in the domain controller's OU
> . SERVER A failed test MachineAccount
> Starting test: Services
> . SERVER A passed test Services
> Starting test: ObjectsReplicated
> . SERVER A passed test ObjectsReplicated
> Starting test: frssysvol
> . SERVER A passed test frssysvol
> Starting test: frsevent
> There are warning or error events within the last 24 hours after the
> SYSVOL has been shared. Failing SYSVOL replication problems may
> cause
> Group Policy problems.
> . SERVER A failed test frsevent
> Starting test: kccevent
> . SERVER A passed test kccevent
> Starting test: systemlog
> An Error Event occured. EventID: 0x00000457
> Time Generated: 09/21/2007 13:51:33
> (Event String could not be retrieved)
> An Error Event occured. EventID: 0x00000457
> Time Generated: 09/21/2007 13:51:36
> (Event String could not be retrieved)
>
> . SERVER A failed test systemlog
> Starting test: VerifyReferences
> . SERVER A passed test VerifyReferences
>
> Running partition tests on : ForestDnsZones
> Starting test: CrossRefValidation
> . ForestDnsZones passed test
> CrossRefValidation
> Starting test: CheckSDRefDom
> . ForestDnsZones passed test CheckSDRefDom
>
> Running partition tests on : DomainDnsZones
> Starting test: CrossRefValidation
> . DomainDnsZones passed test
> CrossRefValidation
> Starting test: CheckSDRefDom
> . DomainDnsZones passed test CheckSDRefDom
>
> Running partition tests on : Schema
> Starting test: CrossRefValidation
> . Schema passed test CrossRefValidation
> Starting test: CheckSDRefDom
> . Schema passed test CheckSDRefDom
>
> Running partition tests on : Configuration
> Starting test: CrossRefValidation
> . Configuration passed test
> CrossRefValidation
> Starting test: CheckSDRefDom
> . Configuration passed test CheckSDRefDom
>
> Running partition tests on : dominio
> Starting test: CrossRefValidation
> . dominio passed test CrossRefValidation
> Starting test: CheckSDRefDom
> . dominio passed test CheckSDRefDom
>
> Running enterprise tests on : dominio.com.ve
> Starting test: Intersite
> . dominio.com.ve passed test Intersite
> Starting test: FsmoCheck
> . dominio.com.ve passed test FsmoCheck
>
>
>
>
> SERVER C (controlador de dominio adicional)
>
>
>
> Domain Controller Diagnosis
>
> Performing initial setup:
> Done gathering initial info.
>
> Doing initial required tests
>
> Testing server: VAL\SERVER C
> Starting test: Connectivity
> . SERVER C passed test Connectivity
>
> Doing primary tests
>
> Testing server: VAL\SERVER C
> Starting test: Replications
> [Replications Check,SERVER C] A recent replication attempt failed:
> From SERVER A to SERVER C
> Naming Context: DC=DomainDnsZones,DC=DOMINIO,DC=com,DC=ve
> The replication generated an error (1256):
> The remote system is not available. For information about
> network troubleshooting, see Windows Help.
> The failure occurred at 2007-09-21 11:57:22.
> The last success occurred at 2007-07-03 17:43:28.
> 633 failures have occurred since the last success.
>
> [Replications Check,SERVER C] A recent replication attempt failed:
> From SERVER A to SERVER C
> Naming Context: DC=ForestDnsZones,DC=DOMINIO,DC=com,DC=ve
> The replication generated an error (1256):
> The remote system is not available. For information about
> network troubleshooting, see Windows Help.
> The failure occurred at 2007-09-21 11:57:22.
> The last success occurred at 2007-07-03 17:43:28.
> 633 failures have occurred since the last success.
>
> [Replications Check,SERVER C] A recent replication attempt failed:
> From SERVER A to SERVER C
> Naming Context: CN=Schema,CN=Configuration,DC=DOMINIO,DC=com,DC=ve
> The replication generated an error (-2146893022):
> The target principal name is incorrect.
> The failure occurred at 2007-09-21 11:57:24.
> The last success occurred at 2007-07-03 17:43:28.
> 633 failures have occurred since the last success.
>
> [Replications Check,SERVER C] A recent replication attempt failed:
> From SERVER A to SERVER C
> Naming Context: CN=Configuration,DC=DOMINIO,DC=com,DC=ve
> The replication generated an error (-2146893022):
> The target principal name is incorrect.
> The failure occurred at 2007-09-21 11:57:23.
> The last success occurred at 2007-07-03 17:43:28.
> 633 failures have occurred since the last success.
>
> [Replications Check,SERVER C] A recent replication attempt failed:
> From SERVER A to SERVER C
> Naming Context: DC=DOMINIO,DC=com,DC=ve
> The replication generated an error (-2146893022):
> The target principal name is incorrect.
> The failure occurred at 2007-09-21 11:57:22.
> The last success occurred at 2007-07-03 17:43:28.
> 633 failures have occurred since the last success.
>
> REPLICATION-RECEIVED LATENCY WARNING
> SERVER C: Current time is 2007-09-21 12:13:00.
> DC=DomainDnsZones,DC=DOMINIO,DC=com,DC=ve
> Last replication recieved from SERVER A at 2007-07-03 17:43:28.
> Last replication recieved from SERVER A2 at 2007-07-03
> 17:42:47.
> DC=ForestDnsZones,DC=DOMINIO,DC=com,DC=ve
> Last replication recieved from SERVER A at 2007-07-03 17:43:28.
> Last replication recieved from SERVER A2 at 2007-07-03
> 16:55:44.
> CN=Schema,CN=Configuration,DC=DOMINIO,DC=com,DC=ve
> Last replication recieved from SERVER A at 2007-07-03 17:43:28.

Una pregunta, los servidores se llaman "Server A", con espacios en blanco en el medio de los nombres?


Saludos,

Marc
MVP Windows Server System - Directory Services
MCSA Windows Server 2003
Citrix CCA
Oracle9i Certified Associate (OCA)

Este mensaje se proporciona "como está" sin garantías de ninguna clase, y no otorga ningún derecho.

This posting is provided "AS IS" with no warranties, and confers no rights. You assume all risk for your use.

"Carlos" escribió en el mensaje news:
> SERVER A (Principal) Event Viewer
>
> Event Type: Error
> Event Source: NTDS Replication
> Event Category: Replication
> Event ID: 1864
> Date: 9/23/2007
> Time: 7:20:12 PM
> User: NT AUTHORITY\ANONYMOUS LOGON
> Computer: SERVER A
> Description:
> This is the replication status for the following directory partition on the
> local domain controller.
>
> Directory partition:
> DC=ForestDnsZones,DC=DOMINIO,DC=com,DC=ve
>
> The local domain controller has not recently received replication
> information from a number of domain controllers. The count of domain
> controllers is shown, divided into the following intervals.
>
> More than 24 hours:
> 1
> More than a week:
> 1
> More than one month:
> 1
> More than two months:
> 1
> More than a tombstone lifetime:
> 0
> Tombstone lifetime (days):
> 180
> Domain controllers that do not replicate in a timely manner may encounter
> errors. It may miss password changes and be unable to authenticate. A DC that
> has not replicated in a tombstone lifetime may have missed the deletion of
> some objects, and may be automatically blocked from future replication until
> it is reconciled.
>
> To identify the domain controllers by name, install the support tools
> included on the installation CD and run dcdiag.exe.
> You can also use the support tool repadmin.exe to display the replication
> latencies of the domain controllers in the forest.
> The command is "repadmin /showvector /latency <partition-dn>".
>
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
>
>
> Una Advertencia
>
>
> Event Type: Warning
> Event Source: NtFrs
> Event Category: None
> Event ID: 13508
> Date: 9/21/2007
> Time: 5:07:30 PM
> User: N/A
> Computer: SERVER A
> Description:
> The File Replication Service is having trouble enabling replication from
> SERVER C to SERVER A
> for c:\windows\sysvol\domain using the DNS name SERVER C.DOMINIO.com.ve. FRS
> will keep retrying.
> Following are some of the reasons you would see this warning.
>
> [1] FRS can not correctly resolve the DNS name SERVER C.DOMINIO.com.ve from
> this computer.
> [2] FRS is not running on SERVER C.DOMINIO.com.ve.
> [3] The topology information in the Active Directory for this replica has
> not yet replicated to all the Domain Controllers.
>
> This event log message will appear once per connection, After the problem
> is fixed you will see another event log message indicating that the
> connection has been established.
>
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
> Data: 0000: 00 00 00 00
>
>
> *******EN LA LOCALIDAD REMOTA SERVER C*********
>
> Event Type: Error
> Event Source: NTDS KCC
> Event Category: Knowledge Consistency Checker
> Event ID: 1311
> Date: 9/24/2007
> Time: 2:04:53 PM
> User: NT AUTHORITY\ANONYMOUS LOGON
> Computer: SERVER C
> Description:
> The Knowledge Consistency Checker (KCC) has detected problems with the
> following directory partition.
>
> Directory partition:
> CN=Configuration,DC=DOMINIO,DC=com,DC=ve
>
> There is insufficient site connectivity information in Active Directory
> Sites and Services for the KCC to create a spanning tree replication
> topology. Or, one or more domain controllers with this directory partition
> are unable to replicate the directory partition information. This is probably
> due to inaccessible domain controllers.
>
> User Action
> Use Active Directory Sites and Services to perform one of the following
> actions:
> - Publish sufficient site connectivity information so that the KCC can
> determine a route by which this directory partition can reach this site. This
> is the preferred option.
> - Add a Connection object to a domain controller that contains the directory
> partition in this site from a domain controller that contains the same
> directory partition in another site.
>
> If neither of the Active Directory Sites and Services tasks correct this
> condition, see previous events logged by the KCC that
> identify the inaccessible domain controllers.
>
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
>
>
> Event Type: Warning
> Event Source: NTDS KCC
> Event Category: Knowledge Consistency Checker
> Event ID: 1865
> Date: 9/24/2007
> Time: 2:04:53 PM
> User: NT AUTHORITY\ANONYMOUS LOGON
> Computer: SERVER C
> Description:
> The Knowledge Consistency Checker (KCC) was unable to form a complete
> spanning tree network topology. As a result, the following list of sites
> cannot be reached from the local site.
>
> Sites:
> CNÌS,CN=Sites,CN=Configuration,DC=redbancamiga,DC=com,DC=ve
>
>
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
>
>
> Ya estoy verificando con lo que me enviaste, tan pronto aviso tan pronto
> pueda.
>
> Saludos
>
>
> "Marc [MVP Windows]" wrote:
>
>> A ver si te sirve:
>>
>> "Schema mismatch" error message occurs when you try to run the Active Directory Installation Wizard (Dcpromo.exe) in Windows Server 2003 or in Windows 2000
>> http://support.microsoft.com/kb/838179
>>
>> Active Directory replication delayed when indexed attributes rebuilt during schema upgrade
>> http://support.microsoft.com/kb/307323
>>
>> También veo este error
>>
>> " Starting test: MachineAccount
>> * The current DC is not in the domain controller's OU"
>>
>> "The current DC is not in the domain controller's OU" error message when you run the Dcdiag tool
>> http://support.microsoft.com/kb/833436
>>
>> Qué más dice el Visor de sucesos?
>>
>>
>> Saludos,
>>
>> Marc
>> MVP Windows Server System - Directory Services
>> MCSA Windows Server 2003
>> Citrix CCA
>> Oracle9i Certified Associate (OCA)
>>
>> Este mensaje se proporciona "como está" sin garantías de ninguna clase, y no otorga ningún derecho.
>>
>> This posting is provided "AS IS" with no warranties, and confers no rights. You assume all risk for your use.
>>
>> "Carlos" escribió en el mensaje news:
>> > Buenas tardes,
>> >
>> > Tengo un controlador de dominio principal (SERVER A) en una CIUDAD A y otro
>> > controlador de dominio adicional (SERVER B) en una CIUDAD B, ambos estan
>> > conectados a traves de enlaces frame-relay de 64K, (los sitios estan creados
>> > y las subredes respectivas tambien), la replicacion entre estos servidores
>> > funciona perfectamente.
>> >
>> > Recientemente se configuro un controlador de dominio adicional (SERVER C)
>> > para instalarlo en una CIUDAD C, este proceso de configuracion se hizo en la
>> > misma ciudad (CIUDAD A) para que no hubiesen problemas de ancho de banda
>> > debido a la primera replicacion cuando se instala el dcpromo, despues se
>> > llevo el (SERVER C) a la localidad remota (CIUDAD C) y se conecto con la
>> > (CIUDAD A) a traves de un enlace frame-relay de 64K. (se creo el sitio y la
>> > subred respectiva). El SERVER C estuvo desconectado del SERVER A
>> > aproximadamente 50 dias.
>> >
>> > El problema es el siguiente:
>> >
>> > El SERVER A no replica ahora con el SERVER C a pesar de que existe
>> > conectividad
>> > y no hay ningun firewall filtrando la comunicacion entre estos dos servidores.
>> >
>> > S.O Instalado: Windows Server 2003 SP1 (en todos los servers)
>> >
>> > Corri el comando DCDIAG y NETDIAG en ambos servidores y el resultado es el
>> > siguiente:
>> >
>> >
>> > SERVER A: (Controlador de Dominio principal, tiene todos los roles)
>> >
>> >
>> >
>> > Domain Controller Diagnosis
>> >
>> > Performing initial setup:
>> > Done gathering initial info.
>> >
>> > Doing initial required tests
>> >
>> > Testing server: CCS\SERVER A
>> > Starting test: Connectivity
>> > . SERVER A passed test Connectivity
>> >
>> > Doing primary tests
>> >
>> > Testing server: CCS\SERVER A
>> > Starting test: Replications
>> > [Replications Check,SERVER A] A recent replication attempt failed:
>> > From SERVER C to SERVER A
>> > Naming Context: DC=ForestDnsZones,DC=dominio,DC=com,DC=ve
>> > The replication generated an error (8418):
>> > The replication operation failed because of a schema mismatch
>> > between the servers involved.
>> > The failure occurred at 2007-09-21 11:50:46.
>> > The last success occurred at 2007-07-03 17:45:37.
>> > 597 failures have occurred since the last success.
>> >
>> > [Replications Check,SERVER A] A recent replication attempt failed:
>> > From SERVER C to SERVER A
>> > Naming Context: DC=DomainDnsZones,DC=dominio,DC=com,DC=ve
>> > The replication generated an error (8418):
>> > The replication operation failed because of a schema mismatch
>> > between the servers involved.
>> > The failure occurred at 2007-09-21 11:50:45.
>> > The last success occurred at 2007-07-03 17:45:37.
>> > 597 failures have occurred since the last success.
>> >
>> > [Replications Check,SERVER A] A recent replication attempt failed:
>> > From SERVER C to SERVER A
>> > Naming Context: CN=Configuration,DC=dominio,DC=com,DC=ve
>> > The replication generated an error (8418):
>> > The replication operation failed because of a schema mismatch
>> > between the servers involved.
>> > The failure occurred at 2007-09-21 11:50:41.
>> > The last success occurred at 2007-07-03 17:45:36.
>> > 597 failures have occurred since the last success.
>> >
>> > [Replications Check,SERVER A] A recent replication attempt failed:
>> > From SERVER C to SERVER A
>> > Naming Context: DC=dominio,DC=com,DC=ve
>> > The replication generated an error (8418):
>> > The replication operation failed because of a schema mismatch
>> > between the servers involved.
>> > The failure occurred at 2007-09-21 11:50:40.
>> > The last success occurred at 2007-07-03 17:45:36.
>> > 597 failures have occurred since the last success.
>> >
>> > REPLICATION-RECEIVED LATENCY WARNING
>> > SERVER A: Current time is 2007-09-21 13:52:15.
>> > DC=ForestDnsZones,DC=dominio,DC=com,DC=ve
>> > Last replication recieved from SERVER C at 2007-07-03 17:45:37.
>> > DC=DomainDnsZones,DC=dominio,DC=com,DC=ve
>> > Last replication recieved from SERVER C at 2007-07-03 17:45:37.
>> > CN=Configuration,DC=dominio,DC=com,DC=ve
>> > Last replication recieved from SERVER C at 2007-07-03 17:45:36.
>> > DC=dominio,DC=com,DC=ve
>> > Last replication recieved from SERVER C at 2007-07-03 17:45:36.

No los servidores se llaman w03veccsdc01 y w03vevalag01, los nombres que
coloque fue para hacerlo mas descriptivo

"Marc [MVP Windows]" wrote:

> Una pregunta, los servidores se llaman "Server A", con espacios en blanco en el medio de los nombres?
>
>
> Saludos,
>
> Marc
> MVP Windows Server System - Directory Services
> MCSA Windows Server 2003
> Citrix CCA
> Oracle9i Certified Associate (OCA)
>
> Este mensaje se proporciona "como está" sin garantías de ninguna clase, y no otorga ningún derecho.
>
> This posting is provided "AS IS" with no warranties, and confers no rights. You assume all risk for your use.
>
> "Carlos" escribió en el mensaje news:
> > SERVER A (Principal) Event Viewer
> >
> > Event Type: Error
> > Event Source: NTDS Replication
> > Event Category: Replication
> > Event ID: 1864
> > Date: 9/23/2007
> > Time: 7:20:12 PM
> > User: NT AUTHORITY\ANONYMOUS LOGON
> > Computer: SERVER A
> > Description:
> > This is the replication status for the following directory partition on the
> > local domain controller.
> >
> > Directory partition:
> > DC=ForestDnsZones,DC=DOMINIO,DC=com,DC=ve
> >
> > The local domain controller has not recently received replication
> > information from a number of domain controllers. The count of domain
> > controllers is shown, divided into the following intervals.
> >
> > More than 24 hours:
> > 1
> > More than a week:
> > 1
> > More than one month:
> > 1
> > More than two months:
> > 1
> > More than a tombstone lifetime:
> > 0
> > Tombstone lifetime (days):
> > 180
> > Domain controllers that do not replicate in a timely manner may encounter
> > errors. It may miss password changes and be unable to authenticate. A DC that
> > has not replicated in a tombstone lifetime may have missed the deletion of
> > some objects, and may be automatically blocked from future replication until
> > it is reconciled.
> >
> > To identify the domain controllers by name, install the support tools
> > included on the installation CD and run dcdiag.exe.
> > You can also use the support tool repadmin.exe to display the replication
> > latencies of the domain controllers in the forest.
> > The command is "repadmin /showvector /latency <partition-dn>".
> >
> > For more information, see Help and Support Center at
> > http://go.microsoft.com/fwlink/events.asp.
> >
> >
> > Una Advertencia
> >
> >
> > Event Type: Warning
> > Event Source: NtFrs
> > Event Category: None
> > Event ID: 13508
> > Date: 9/21/2007
> > Time: 5:07:30 PM
> > User: N/A
> > Computer: SERVER A
> > Description:
> > The File Replication Service is having trouble enabling replication from
> > SERVER C to SERVER A
> > for c:\windows\sysvol\domain using the DNS name SERVER C.DOMINIO.com.ve. FRS
> > will keep retrying.
> > Following are some of the reasons you would see this warning.
> >
> > [1] FRS can not correctly resolve the DNS name SERVER C.DOMINIO.com.ve from
> > this computer.
> > [2] FRS is not running on SERVER C.DOMINIO.com.ve.
> > [3] The topology information in the Active Directory for this replica has
> > not yet replicated to all the Domain Controllers.
> >
> > This event log message will appear once per connection, After the problem
> > is fixed you will see another event log message indicating that the
> > connection has been established.
> >
> > For more information, see Help and Support Center at
> > http://go.microsoft.com/fwlink/events.asp.
> > Data: 0000: 00 00 00 00
> >
> >
> > *******EN LA LOCALIDAD REMOTA SERVER C*********
> >
> > Event Type: Error
> > Event Source: NTDS KCC
> > Event Category: Knowledge Consistency Checker
> > Event ID: 1311
> > Date: 9/24/2007
> > Time: 2:04:53 PM
> > User: NT AUTHORITY\ANONYMOUS LOGON
> > Computer: SERVER C
> > Description:
> > The Knowledge Consistency Checker (KCC) has detected problems with the
> > following directory partition.
> >
> > Directory partition:
> > CN=Configuration,DC=DOMINIO,DC=com,DC=ve
> >
> > There is insufficient site connectivity information in Active Directory
> > Sites and Services for the KCC to create a spanning tree replication
> > topology. Or, one or more domain controllers with this directory partition
> > are unable to replicate the directory partition information. This is probably
> > due to inaccessible domain controllers.
> >
> > User Action
> > Use Active Directory Sites and Services to perform one of the following
> > actions:
> > - Publish sufficient site connectivity information so that the KCC can
> > determine a route by which this directory partition can reach this site. This
> > is the preferred option.
> > - Add a Connection object to a domain controller that contains the directory
> > partition in this site from a domain controller that contains the same
> > directory partition in another site.
> >
> > If neither of the Active Directory Sites and Services tasks correct this
> > condition, see previous events logged by the KCC that
> > identify the inaccessible domain controllers.
> >
> > For more information, see Help and Support Center at
> > http://go.microsoft.com/fwlink/events.asp.
> >
> >
> > Event Type: Warning
> > Event Source: NTDS KCC
> > Event Category: Knowledge Consistency Checker
> > Event ID: 1865
> > Date: 9/24/2007
> > Time: 2:04:53 PM
> > User: NT AUTHORITY\ANONYMOUS LOGON
> > Computer: SERVER C
> > Description:
> > The Knowledge Consistency Checker (KCC) was unable to form a complete
> > spanning tree network topology. As a result, the following list of sites
> > cannot be reached from the local site.
> >
> > Sites:
> > CNÌS,CN=Sites,CN=Configuration,DC=redbancamiga,DC=com,DC=ve
> >
> >
> > For more information, see Help and Support Center at
> > http://go.microsoft.com/fwlink/events.asp.
> >
> >
> > Ya estoy verificando con lo que me enviaste, tan pronto aviso tan pronto
> > pueda.
> >
> > Saludos
> >
> >
> > "Marc [MVP Windows]" wrote:
> >
> >> A ver si te sirve:
> >>
> >> "Schema mismatch" error message occurs when you try to run the Active Directory Installation Wizard (Dcpromo.exe) in Windows Server 2003 or in Windows 2000
> >> http://support.microsoft.com/kb/838179
> >>
> >> Active Directory replication delayed when indexed attributes rebuilt during schema upgrade
> >> http://support.microsoft.com/kb/307323
> >>
> >> También veo este error
> >>
> >> " Starting test: MachineAccount
> >> * The current DC is not in the domain controller's OU"
> >>
> >> "The current DC is not in the domain controller's OU" error message when you run the Dcdiag tool
> >> http://support.microsoft.com/kb/833436
> >>
> >> Qué más dice el Visor de sucesos?
> >>
> >>
> >> Saludos,
> >>
> >> Marc
> >> MVP Windows Server System - Directory Services
> >> MCSA Windows Server 2003
> >> Citrix CCA
> >> Oracle9i Certified Associate (OCA)
> >>
> >> Este mensaje se proporciona "como está" sin garantías de ninguna clase, y no otorga ningún derecho.
> >>
> >> This posting is provided "AS IS" with no warranties, and confers no rights. You assume all risk for your use.
> >>
> >> "Carlos" escribió en el mensaje news:
> >> > Buenas tardes,
> >> >
> >> > Tengo un controlador de dominio principal (SERVER A) en una CIUDAD A y otro
> >> > controlador de dominio adicional (SERVER B) en una CIUDAD B, ambos estan
> >> > conectados a traves de enlaces frame-relay de 64K, (los sitios estan creados
> >> > y las subredes respectivas tambien), la replicacion entre estos servidores
> >> > funciona perfectamente.
> >> >
> >> > Recientemente se configuro un controlador de dominio adicional (SERVER C)
> >> > para instalarlo en una CIUDAD C, este proceso de configuracion se hizo en la
> >> > misma ciudad (CIUDAD A) para que no hubiesen problemas de ancho de banda
> >> > debido a la primera replicacion cuando se instala el dcpromo, despues se
> >> > llevo el (SERVER C) a la localidad remota (CIUDAD C) y se conecto con la
> >> > (CIUDAD A) a traves de un enlace frame-relay de 64K. (se creo el sitio y la
> >> > subred respectiva). El SERVER C estuvo desconectado del SERVER A
> >> > aproximadamente 50 dias.
> >> >
> >> > El problema es el siguiente:
> >> >
> >> > El SERVER A no replica ahora con el SERVER C a pesar de que existe
> >> > conectividad
> >> > y no hay ningun firewall filtrando la comunicacion entre estos dos servidores.
> >> >
> >> > S.O Instalado: Windows Server 2003 SP1 (en todos los servers)
> >> >
> >> > Corri el comando DCDIAG y NETDIAG en ambos servidores y el resultado es el
> >> > siguiente:
> >> >
> >> >
> >> > SERVER A: (Controlador de Dominio principal, tiene todos los roles)
> >> >
> >> >
> >> >
> >> > Domain Controller Diagnosis
> >> >
> >> > Performing initial setup:
> >> > Done gathering initial info.
> >> >
> >> > Doing initial required tests
> >> >
> >> > Testing server: CCS\SERVER A
> >> > Starting test: Connectivity
> >> > . SERVER A passed test Connectivity
> >> >
> >> > Doing primary tests
> >> >
> >> > Testing server: CCS\SERVER A
> >> > Starting test: Replications
> >> > [Replications Check,SERVER A] A recent replication attempt failed:
> >> > From SERVER C to SERVER A
> >> > Naming Context: DC=ForestDnsZones,DC=dominio,DC=com,DC=ve
> >> > The replication generated an error (8418):
> >> > The replication operation failed because of a schema mismatch
> >> > between the servers involved.
> >> > The failure occurred at 2007-09-21 11:50:46.
> >> > The last success occurred at 2007-07-03 17:45:37.
> >> > 597 failures have occurred since the last success.
> >> >
> >> > [Replications Check,SERVER A] A recent replication attempt failed:
> >> > From SERVER C to SERVER A
> >> > Naming Context: DC=DomainDnsZones,DC=dominio,DC=com,DC=ve
> >> > The replication generated an error (8418):
> >> > The replication operation failed because of a schema mismatch
> >> > between the servers involved.
> >> > The failure occurred at 2007-09-21 11:50:45.
> >> > The last success occurred at 2007-07-03 17:45:37.
> >> > 597 failures have occurred since the last success.
> >> >
> >> > [Replications Check,SERVER A] A recent replication attempt failed:
> >> > From SERVER C to SERVER A
> >> > Naming Context: CN=Configuration,DC=dominio,DC=com,DC=ve
> >> > The replication generated an error (8418):
> >> > The replication operation failed because of a schema mismatch
> >> > between the servers involved.
> >> > The failure occurred at 2007-09-21 11:50:41.
> >> > The last success occurred at 2007-07-03 17:45:36.
> >> > 597 failures have occurred since the last success.
> >> >
> >> > [Replications Check,SERVER A] A recent replication attempt failed:
> >> > From SERVER C to SERVER A
> >> > Naming Context: DC=dominio,DC=com,DC=ve
> >> > The replication generated an error (8418):
> >> > The replication operation failed because of a schema mismatch
> >> > between the servers involved.
> >> > The failure occurred at 2007-09-21 11:50:40.
> >> > The last success occurred at 2007-07-03 17:45:36.
> >> > 597 failures have occurred since the last success.
> >> >
> >> > REPLICATION-RECEIVED LATENCY WARNING
> >> > SERVER A: Current time is 2007-09-21 13:52:15.
> >> > DC=ForestDnsZones,DC=dominio,DC=com,DC=ve
> >> > Last replication recieved from SERVER C at 2007-07-03 17:45:37.
> >> > DC=DomainDnsZones,DC=dominio,DC=com,DC=ve