none
Auxilio. Error replicación NTDS. Sobrepasado periodo de desecho RRS feed

  • Pregunta

  •  

     

    Buenas a todos. Tengo un fuego que me tiene muy preocupado y no doy con la solución acertada.

     

                El escenario es el siguiente, hemos tenido una oficina remota fuera de la red global durante bastante tiempo (se solapo un cambio de residencia junto con un problema con el operador) y por tanto la vpn ha estado sin funcionar mucho tiempo, para acceder a internet y demás ha sido a base de apaños muy rebuscados.

     

                El caso es q sin vpn no se replicaba el controlador de dominio de esa oficina con el resto y ahora al volver todo a la normalidad salta la perdiz con un problema de expiración de replicas. Y después de probar comandos como se aconseja en los mismos errores y mira run poco en google estoy perdido no se que hacer, tengo en el registro activada una nueva clave para permitir replicas inexactas y desactivado el forzar exigencia de integridad pero me parece que sigue fallando.

     

     

    os pegos los errores.

     

     

    Tipo de suceso:            Advertencia

    Origen del suceso:        NTDS Replication

    Categoría del suceso:    Replicación

    Id. suceso:        1586

    Fecha:              25/06/2008

    Hora:                4:48:22

    Usuario:                        NT AUTHORITY\ANONYMOUS LOGON

    Equipo:            SRV-PT

    Descripción:

    El control de replicación de Windows NT 4.0 o anterior con el maestro emulador PDC no ha tenido éxito.

     

    Podría producirse una sincronización completa de la base de datos del Administrador de cuentas de seguridad (SAM) en los controladores de dominio que utilizan Windows NT 4.0 y anterior si la función del maestro emulador PDC se transfiere al controlador de dominio local antes del próximo control con éxito.

     

    Se intentará el proceso de control de nuevo dentro de cuatro horas.

     

    Datos adicionales

    Valor de error:

    8614 Active Directory no puede hacer réplicas con el servidor porque el intervalo desde la última replicación con este servidor ha superado el período de vida de objetos de desecho.

     

    Para obtener más información, vea el Centro de ayuda y soporte técnico en http://go.microsoft.com/fwlink/events.asp.

     

     

     

     

     

     

     

    Tipo de suceso:            Error

    Origen del suceso:        NTDS Replication

    Categoría del suceso:    Replicación

    Id. suceso:        2042

    Fecha:              25/06/2008

    Hora:                4:48:22

    Usuario:                        NT AUTHORITY\ANONYMOUS LOGON

    Equipo:            SRV-PT

    Descripción:

    Ha transcurrido mucho tiempo desde que este equipo se replicó por última vez con el equipo de origen indicado. El tiempo entre replicaciones con este origen ha excedido el período de vida de objetos de desecho. La replicación con este origen se ha detenido.

    El motivo de que la replicación no pueda continuar es que las vistas de objetos eliminados de ambos equipos posiblemente son diferentes. Es posible que el equipo de origen siga teniendo copias de objetos que se han eliminado (y enviado a la recolección de elementos no utilizados) en este equipo. Si se les permitiera replicarse, el equipo de origen devolvería objetos ya eliminados.

    Hora de la última replicación correcta:

    2008-04-19 08:34:14

    Id. de invocación del origen:

    0587f6c8-f6b8-0587-0100-000000000000

    Nombre del origen:

    04b42c32-6481-47e0-a2ee-fe067d96d6c1._msdcs.aaesa-madrid.local

    Período de vida de objetos de desecho (días):

    60

     

    Error en la operación de replicación.

     

    Acción del usuario:

     

    Determine cuál de los equipos se desconectó del bosque y no está actualizado. Tiene tres opciones:

     

    1. Disminuya el nivel del equipo o equipos que se desconectaron o vuelva a instalarlos.

    2. Utilice la herramienta "repadmin /removelingeringobjects" para quitar los objetos eliminados incoherentes y reanude la replicación.

    3. Reanude la replicación. Es posible que se introduzcan objetos eliminados incoherentes. Puede continuar la replicación si usa la siguiente clave del Registro. Cuando los sistemas se hayan replicado una vez, es recomendable que quite la clave para restablecer la protección.

     Clave del Registro:

    HKLM\System\CurrentControlSet\Services\NTDS\Parameters\Allow Replication With Divergent and Corrupt Partner

     

     

    Para obtener más información, vea el Centro de ayuda y soporte técnico en http://go.microsoft.com/fwlink/events.asp.

     

     

     

    Tipo de suceso:            Error

    Origen del suceso:        NTDS Replication

    Categoría del suceso:    Replicación

    Id. suceso:        1864

    Fecha:              23/06/2008

    Hora:                4:13:23

    Usuario:                        NT AUTHORITY\ANONYMOUS LOGON

    Equipo:            SRV-PT

    Descripción:

    Éste es el estado de replicación para la siguiente partición del directorio en el controlador de dominio local.

     

    Partición del directorio:

    DC=ForestDnsZones,DC=aaesa-madrid,DC=local

     

    El controlador de dominio local no recibió recientemente información de replicación de varios controladores de dominio.   A continuación puede ver el número de controladores de dominio, separados en los siguientes intervalos.

     

    Más de 24 horas:

    4

    Más de una semana:

    4

    Más de un mes:

    4

    Más de dos meses:

    4

    Más de un período de vida de desecho:

    4

    Período de vida de desecho (días):

    60

     Los controladores de dominio que no replican a tiempo pueden encontrar errores. Pueden perder cambios de contraseña y no podrían realizar la autenticación. Un DC que no se replica en el período de vida de desecho puede perder la información de eliminación de algunos objetos y bloquear automáticamente  su futura replicación hasta que se reconcilie.

     

    Para identificar los controladores de dominio por el nombre, instale las herramientas de soporte incluidas en el CD  de instalación y ejecute dcdiag.exe.

    También puede utilizar la herramienta de soporte repadmin.exe para mostrar las latencias de replicación de los controladores de dominio del bosque. El comando es "repadmin /showvector /latency <partition-dn>".

     

    Para obtener más información, vea el Centro de ayuda y soporte técnico en http://go.microsoft.com/fwlink/events.asp.

     

    Estoy en madrid y estoy dispuesto a pagar unas cañas! Esto es broma pero vamos que necesito un poco de help!

     

    Muchas Gracias!!!

     

     


    jueves, 26 de junio de 2008 9:24

Todas las respuestas

  • un dcdiag genera este reporte

     


    Domain Controller Diagnosis

    Performing initial setup:
       Done gathering initial info.

    Doing initial required tests
      
       Testing server: Nombre-predeterminado-primer-sitio\SRV-PT
          Starting test: Connectivity
             ......................... SRV-PT passed test Connectivity

    Doing primary tests
      
       Testing server: Nombre-predeterminado-primer-sitio\SRV-PT
          Starting test: Replications
             [Replications Check,SRV-PT] A recent replication attempt failed:
                From SRV-BCN to SRV-PT
                Naming Context: DC=ForestDnsZones,DC=aaesa-madrid,DC=local
                The replication generated an error (1256):
                El sistema remoto no est disponible. Para obtener ms informacin sobre cmo solucionar problemas en la red, vea la Ayuda de Windows.
                The failure occurred at 2008-06-29 19:49:26.
                The last success occurred at 2008-04-16 22:57:20.
                1730 failures have occurred since the last success.
             [SRV-BCN] DsBindWithSpnEx() failed with error -2146893022,
             El nombre principal de destino es incorrecto..
             [Replications Check,SRV-PT] A recent replication attempt failed:
                From SRV to SRV-PT
                Naming Context: DC=ForestDnsZones,DC=aaesa-madrid,DC=local
                The replication generated an error (1256):
                El sistema remoto no est disponible. Para obtener ms informacin sobre cmo solucionar problemas en la red, vea la Ayuda de Windows.
                The failure occurred at 2008-06-29 19:49:28.
                The last success occurred at 2008-04-19 07:49:19.
                1673 failures have occurred since the last success.
             [SRV] DsBindWithSpnEx() failed with error -2146893022,
             El nombre principal de destino es incorrecto..
             [Replications Check,SRV-PT] A recent replication attempt failed:
                From SRV-BCK to SRV-PT
                Naming Context: DC=ForestDnsZones,DC=aaesa-madrid,DC=local
                The replication generated an error (1256):
                El sistema remoto no est disponible. Para obtener ms informacin sobre cmo solucionar problemas en la red, vea la Ayuda de Windows.
                The failure occurred at 2008-06-29 19:49:31.
                The last success occurred at 2008-04-19 07:49:20.
                1671 failures have occurred since the last success.
             [SRV-BCK] DsBindWithSpnEx() failed with error -2146893022,
             El nombre principal de destino es incorrecto..
             [Replications Check,SRV-PT] A recent replication attempt failed:
                From SRV-BIL to SRV-PT
                Naming Context: DC=ForestDnsZones,DC=aaesa-madrid,DC=local
                The replication generated an error (1256):
                El sistema remoto no est disponible. Para obtener ms informacin sobre cmo solucionar problemas en la red, vea la Ayuda de Windows.
                The failure occurred at 2008-06-29 19:49:32.
                The last success occurred at 2008-04-19 08:34:18.
                6638 failures have occurred since the last success.
             [SRV-BIL] DsBindWithSpnEx() failed with error -2146893022,
             El nombre principal de destino es incorrecto..
             [Replications Check,SRV-PT] A recent replication attempt failed:
                From SRV-BCN to SRV-PT
                Naming Context: DC=DomainDnsZones,DC=aaesa-madrid,DC=local
                The replication generated an error (1256):
                El sistema remoto no est disponible. Para obtener ms informacin sobre cmo solucionar problemas en la red, vea la Ayuda de Windows.
                The failure occurred at 2008-06-29 19:49:26.
                The last success occurred at 2008-04-16 22:57:18.
                1730 failures have occurred since the last success.
             [Replications Check,SRV-PT] A recent replication attempt failed:
                From SRV to SRV-PT
                Naming Context: DC=DomainDnsZones,DC=aaesa-madrid,DC=local
                The replication generated an error (1256):
                El sistema remoto no est disponible. Para obtener ms informacin sobre cmo solucionar problemas en la red, vea la Ayuda de Windows.
                The failure occurred at 2008-06-29 19:49:28.
                The last success occurred at 2008-04-19 07:49:18.
                1673 failures have occurred since the last success.
             [Replications Check,SRV-PT] A recent replication attempt failed:
                From SRV-BCK to SRV-PT
                Naming Context: DC=DomainDnsZones,DC=aaesa-madrid,DC=local
                The replication generated an error (1256):
                El sistema remoto no est disponible. Para obtener ms informacin sobre cmo solucionar problemas en la red, vea la Ayuda de Windows.
                The failure occurred at 2008-06-29 19:49:31.
                The last success occurred at 2008-04-19 07:49:18.
                1671 failures have occurred since the last success.
             [Replications Check,SRV-PT] A recent replication attempt failed:
                From SRV-BIL to SRV-PT
                Naming Context: DC=DomainDnsZones,DC=aaesa-madrid,DC=local
                The replication generated an error (1256):
                El sistema remoto no est disponible. Para obtener ms informacin sobre cmo solucionar problemas en la red, vea la Ayuda de Windows.
                The failure occurred at 2008-06-29 19:49:32.
                The last success occurred at 2008-04-19 08:34:17.
                6638 failures have occurred since the last success.
             [Replications Check,SRV-PT] A recent replication attempt failed:
                From SRV to SRV-PT
                Naming Context: CN=Schema,CN=Configuration,DC=aaesa-madrid,DC=local
                The replication generated an error (-2146893022):
                El nombre principal de destino es incorrecto.
                The failure occurred at 2008-06-29 19:49:34.
                The last success occurred at 2008-04-19 07:49:15.
                1672 failures have occurred since the last success.
             [Replications Check,SRV-PT] A recent replication attempt failed:
                From SRV-BCK to SRV-PT
                Naming Context: CN=Schema,CN=Configuration,DC=aaesa-madrid,DC=local
                The replication generated an error (-2146893022):
                El nombre principal de destino es incorrecto.
                The failure occurred at 2008-06-29 19:49:35.
                The last success occurred at 2008-04-19 07:49:15.
                1673 failures have occurred since the last success.
             [Replications Check,SRV-PT] A recent replication attempt failed:
                From SRV-BCN to SRV-PT
                Naming Context: CN=Schema,CN=Configuration,DC=aaesa-madrid,DC=local
                The replication generated an error (-2146893022):
                El nombre principal de destino es incorrecto.
                The failure occurred at 2008-06-29 19:49:36.
                The last success occurred at 2008-04-16 22:57:15.
                1730 failures have occurred since the last success.
             [Replications Check,SRV-PT] A recent replication attempt failed:
                From SRV-BIL to SRV-PT
                Naming Context: CN=Schema,CN=Configuration,DC=aaesa-madrid,DC=local
                The replication generated an error (-2146893022):
                El nombre principal de destino es incorrecto.
                The failure occurred at 2008-06-29 19:49:37.
                The last success occurred at 2008-04-19 08:34:17.
                6639 failures have occurred since the last success.
             [Replications Check,SRV-PT] A recent replication attempt failed:
                From SRV to SRV-PT
                Naming Context: CN=Configuration,DC=aaesa-madrid,DC=local
                The replication generated an error (-2146893022):
                El nombre principal de destino es incorrecto.
                The failure occurred at 2008-06-29 19:49:28.
                The last success occurred at 2008-04-19 08:31:42.
                1851 failures have occurred since the last success.
             [Replications Check,SRV-PT] A recent replication attempt failed:
                From SRV-BCN to SRV-PT
                Naming Context: CN=Configuration,DC=aaesa-madrid,DC=local
                The replication generated an error (-2146893022):
                El nombre principal de destino es incorrecto.
                The failure occurred at 2008-06-29 19:49:29.
                The last success occurred at 2008-04-16 23:02:04.
                1907 failures have occurred since the last success.
             [Replications Check,SRV-PT] A recent replication attempt failed:
                From SRV-BCK to SRV-PT
                Naming Context: CN=Configuration,DC=aaesa-madrid,DC=local
                The replication generated an error (-2146893022):
                El nombre principal de destino es incorrecto.
                The failure occurred at 2008-06-29 19:49:31.
                The last success occurred at 2008-04-19 08:31:51.
                1850 failures have occurred since the last success.
             [Replications Check,SRV-PT] A recent replication attempt failed:
                From SRV-BIL to SRV-PT
                Naming Context: CN=Configuration,DC=aaesa-madrid,DC=local
                The replication generated an error (-2146893022):
                El nombre principal de destino es incorrecto.
                The failure occurred at 2008-06-29 19:49:32.
                The last success occurred at 2008-04-19 08:34:16.
                6814 failures have occurred since the last success.
             [Replications Check,SRV-PT] A recent replication attempt failed:
                From SRV-BCN to SRV-PT
                Naming Context: DC=aaesa-madrid,DC=local
                The replication generated an error (-2146893022):
                El nombre principal de destino es incorrecto.
                The failure occurred at 2008-06-29 19:49:26.
                The last success occurred at 2008-04-16 23:26:06.
                2611 failures have occurred since the last success.
             [Replications Check,SRV-PT] A recent replication attempt failed:
                From SRV-BIL to SRV-PT
                Naming Context: DC=aaesa-madrid,DC=local
                The replication generated an error (-2146893022):
                El nombre principal de destino es incorrecto.
                The failure occurred at 2008-06-29 19:49:40.
                The last success occurred at 2008-04-19 08:34:16.
                7654 failures have occurred since the last success.
             [Replications Check,SRV-PT] A recent replication attempt failed:
                From SRV to SRV-PT
                Naming Context: DC=aaesa-madrid,DC=local
                The replication generated an error (-2146893022):
                El nombre principal de destino es incorrecto.
                The failure occurred at 2008-06-29 19:49:41.
                The last success occurred at 2008-04-19 08:34:15.
                5509 failures have occurred since the last success.
             [Replications Check,SRV-PT] A recent replication attempt failed:
                From SRV-BCK to SRV-PT
                Naming Context: DC=aaesa-madrid,DC=local
                The replication generated an error (-2146893022):
                El nombre principal de destino es incorrecto.
                The failure occurred at 2008-06-29 19:50:24.
                The last success occurred at 2008-04-19 08:32:24.
                2702 failures have occurred since the last success.
             REPLICATION-RECEIVED LATENCY WARNING
             SRV-PT:  Current time is 2008-06-29 19:51:54.
                DC=ForestDnsZones,DC=aaesa-madrid,DC=local
                   Last replication recieved from SRV at 2008-04-19 07:58:42.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from SRV-BIL at 2008-04-19 08:34:18.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from SRV-BCK at 2008-04-19 08:20:00.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from SRV-BCN at 2008-04-16 23:42:42.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                DC=DomainDnsZones,DC=aaesa-madrid,DC=local
                   Last replication recieved from SRV at 2008-04-19 07:58:41.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from SRV-BIL at 2008-04-19 08:34:17.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from SRV-BCK at 2008-04-19 08:19:59.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from SRV-BCN at 2008-04-16 23:42:41.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                CN=Schema,CN=Configuration,DC=aaesa-madrid,DC=local
                   Last replication recieved from SRV at 2008-04-19 07:58:21.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from SRV-BIL at 2008-04-19 08:34:17.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from SRV-BCK at 2008-04-19 08:19:58.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from SRV-BCN at 2008-04-16 23:42:40.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                CN=Configuration,DC=aaesa-madrid,DC=local
                   Last replication recieved from SRV at 2008-04-19 08:31:42.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from SRV-BIL at 2008-04-19 08:34:16.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from SRV-BCK at 2008-04-19 08:31:58.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from SRV-BCN at 2008-04-16 23:42:39.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                DC=aaesa-madrid,DC=local
                   Last replication recieved from SRV at 2008-04-19 08:34:14.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from SRV-BIL at 2008-04-19 08:34:16.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from SRV-BCK at 2008-04-19 08:32:30.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from SRV-BCN at 2008-04-16 23:42:37.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
             ......................... SRV-PT passed test Replications
          Starting test: NCSecDesc
             ......................... SRV-PT passed test NCSecDesc
          Starting test: NetLogons
             ......................... SRV-PT passed test NetLogons
          Starting test: Advertising
             ......................... SRV-PT passed test Advertising
          Starting test: KnowsOfRoleHolders
             Warning: SRV is the Schema Owner, but is not responding to DS RPC Bind.
             [SRV] LDAP bind failed with error 8341,
             Error del servicio de directorios..
             Warning: SRV is the Schema Owner, but is not responding to LDAP Bind.
             Warning: SRV is the Domain Owner, but is not responding to DS RPC Bind.
             Warning: SRV is the Domain Owner, but is not responding to LDAP Bind.
             Warning: SRV is the PDC Owner, but is not responding to DS RPC Bind.
             Warning: SRV is the PDC Owner, but is not responding to LDAP Bind.
             Warning: SRV is the Rid Owner, but is not responding to DS RPC Bind.
             Warning: SRV is the Rid Owner, but is not responding to LDAP Bind.
             Warning: SRV is the Infrastructure Update Owner, but is not responding to DS RPC Bind.
             Warning: SRV is the Infrastructure Update Owner, but is not responding to LDAP Bind.
             ......................... SRV-PT failed test KnowsOfRoleHolders
          Starting test: RidManager
             ......................... SRV-PT failed test RidManager
          Starting test: MachineAccount
             ......................... SRV-PT passed test MachineAccount
          Starting test: Services
             ......................... SRV-PT passed test Services
          Starting test: ObjectsReplicated
             ......................... SRV-PT passed test ObjectsReplicated
          Starting test: frssysvol
             ......................... SRV-PT passed test frssysvol
          Starting test: frsevent
             ......................... SRV-PT passed test frsevent
          Starting test: kccevent
             ......................... SRV-PT passed test kccevent
          Starting test: systemlog
             An Error Event occured.  EventID: 0x40011006
                Time Generated: 06/29/2008   19:01:29
                (Event String could not be retrieved)
             An Error Event occured.  EventID: 0x40011006
                Time Generated: 06/29/2008   19:01:30
                (Event String could not be retrieved)
             An Error Event occured.  EventID: 0x40000004
                Time Generated: 06/29/2008   19:05:22
                (Event String could not be retrieved)
             An Error Event occured.  EventID: 0x40000004
                Time Generated: 06/29/2008   19:17:32
                (Event String could not be retrieved)
             An Error Event occured.  EventID: 0x40000004
                Time Generated: 06/29/2008   19:30:22
                (Event String could not be retrieved)
             An Error Event occured.  EventID: 0x40011006
                Time Generated: 06/29/2008   19:31:29
                (Event String could not be retrieved)
             An Error Event occured.  EventID: 0x40000004
                Time Generated: 06/29/2008   19:32:34
                (Event String could not be retrieved)
             An Error Event occured.  EventID: 0x40000004
                Time Generated: 06/29/2008   19:34:26
                (Event String could not be retrieved)
             An Error Event occured.  EventID: 0x40000004
                Time Generated: 06/29/2008   19:38:22
                (Event String could not be retrieved)
             An Error Event occured.  EventID: 0x40000004
                Time Generated: 06/29/2008   19:38:27
                (Event String could not be retrieved)
             An Error Event occured.  EventID: 0x40000004
                Time Generated: 06/29/2008   19:38:39
                (Event String could not be retrieved)
             An Error Event occured.  EventID: 0x40000004
                Time Generated: 06/29/2008   19:38:44
                (Event String could not be retrieved)
             An Error Event occured.  EventID: 0x40000004
                Time Generated: 06/29/2008   19:38:49
                (Event String could not be retrieved)
             An Error Event occured.  EventID: 0x40000004
                Time Generated: 06/29/2008   19:38:54
                (Event String could not be retrieved)
             An Error Event occured.  EventID: 0x40000004
                Time Generated: 06/29/2008   19:45:49
                (Event String could not be retrieved)
             An Error Event occured.  EventID: 0x40000004
                Time Generated: 06/29/2008   19:45:50
                (Event String could not be retrieved)
             An Error Event occured.  EventID: 0x40000004
                Time Generated: 06/29/2008   19:45:52
                (Event String could not be retrieved)
             An Error Event occured.  EventID: 0x40000004
                Time Generated: 06/29/2008   19:45:54
                (Event String could not be retrieved)
             An Error Event occured.  EventID: 0x40000004
                Time Generated: 06/29/2008   19:45:56
                (Event String could not be retrieved)
             An Error Event occured.  EventID: 0x40000004
                Time Generated: 06/29/2008   19:45:58
                (Event String could not be retrieved)
             An Error Event occured.  EventID: 0x40011006
                Time Generated: 06/29/2008   19:46:29
                (Event String could not be retrieved)
             An Error Event occured.  EventID: 0x40000004
                Time Generated: 06/29/2008   19:49:34
                (Event String could not be retrieved)
             An Error Event occured.  EventID: 0x40000004
                Time Generated: 06/29/2008   19:49:35
                (Event String could not be retrieved)
             An Error Event occured.  EventID: 0x40000004
                Time Generated: 06/29/2008   19:49:36
                (Event String could not be retrieved)
             ......................... SRV-PT failed test systemlog
          Starting test: VerifyReferences
             ......................... SRV-PT 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 : aaesa-madrid
          Starting test: CrossRefValidation
             ......................... aaesa-madrid passed test CrossRefValidation
          Starting test: CheckSDRefDom
             ......................... aaesa-madrid passed test CheckSDRefDom
      
       Running enterprise tests on : aaesa-madrid.local
          Starting test: Intersite
             ......................... aaesa-madrid.local passed test Intersite
          Starting test: FsmoCheck
             [SRV-BCK] LDAP bind failed with error 8341,
             Error del servicio de directorios..
             ......................... aaesa-madrid.local passed test FsmoCheck

     

    A ver si alguien puede echarme un cable!!!!

     

    domingo, 29 de junio de 2008 18:49