Error en AD con 3 controladores de dominio

Buenas a todos,

os explico mi situación: Tengo 1 controlador de dominio y 2 secundarios.
Bien, el caso es que tengo muchos problemas con las políticas. Le he pasado
un dcdiag, y el resultado es el siguiente: (A ver si alguien me da alguna
solución, ya que estoy buscando y no encuentro nada. Muchas gracias)


Domain Controller Diagnosis

Performing initial setup:
Done gathering initial info.

Doing initial required tests

Testing server: Nombre-predeterminado-primer-sitio\SERVER1
Starting test: Connectivity
. SERVER1 passed test Connectivity

Testing server: Nombre-predeterminado-primer-sitio\SERVER2
Starting test: Connectivity
. SERVER2 passed test Connectivity

Testing server: Nombre-predeterminado-primer-sitio\SERVER3
Starting test: Connectivity
. SERVER3 passed test Connectivity

Doing primary tests

Testing server: Nombre-predeterminado-primer-sitio\SERVER1
Starting test: Replications
. SERVER1 passed test Replications
Starting test: NCSecDesc
. SERVER1 passed test NCSecDesc
Starting test: NetLogons
. SERVER1 passed test NetLogons
Starting test: Advertising
Warning: SERVER1 is not advertising as a time server.
. SERVER1 failed test Advertising
Starting test: KnowsOfRoleHolders
. SERVER1 passed test KnowsOfRoleHolders
Starting test: RidManager
. SERVER1 passed test RidManager
Starting test: MachineAccount
. SERVER1 passed test MachineAccount
Starting test: Services
. SERVER1 passed test Services
Starting test: ObjectsReplicated
. SERVER1 passed test ObjectsReplicated
Starting test: frssysvol
. SERVER1 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.
. SERVER1 failed test frsevent
Starting test: kccevent
. SERVER1 passed test kccevent
Starting test: systemlog
. SERVER1 passed test systemlog
Starting test: VerifyReferences
. SERVER1 passed test VerifyReferences

Testing server: Nombre-predeterminado-primer-sitio\SERVER2
Starting test: Replications
REPLICATION LATENCY WARNING
ERROR: Expected notification link is missing.
Source SERVER1
Replication of new changes along this path will be delayed.
This problem should self-correct on the next periodic sync.
. SERVER2 passed test Replications
Starting test: NCSecDesc
. SERVER2 passed test NCSecDesc
Starting test: NetLogons
. SERVER2 passed test NetLogons
Starting test: Advertising
. SERVER2 passed test Advertising
Starting test: KnowsOfRoleHolders
. SERVER2 passed test KnowsOfRoleHolders
Starting test: RidManager
. SERVER2 passed test RidManager
Starting test: MachineAccount
. SERVER2 passed test MachineAccount
Starting test: Services
. SERVER2 passed test Services
Starting test: ObjectsReplicated
. SERVER2 passed test ObjectsReplicated
Starting test: frssysvol
. SERVER2 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.
. SERVER2 failed test frsevent
Starting test: kccevent
. SERVER2 passed test kccevent
Starting test: systemlog
. SERVER2 passed test systemlog
Starting test: VerifyReferences
. SERVER2 passed test VerifyReferences

Testing server: Nombre-predeterminado-primer-sitio\SERVER3
Starting test: Replications
. SERVER3 passed test Replications
Starting test: NCSecDesc
. SERVER3 passed test NCSecDesc
Starting test: NetLogons
. SERVER3 passed test NetLogons
Starting test: Advertising
. SERVER3 passed test Advertising
Starting test: KnowsOfRoleHolders
. SERVER3 passed test KnowsOfRoleHolders
Starting test: RidManager
. SERVER3 passed test RidManager
Starting test: MachineAccount
. SERVER3 passed test MachineAccount
Starting test: Services
. SERVER3 passed test Services
Starting test: ObjectsReplicated
. SERVER3 passed test ObjectsReplicated
Starting test: frssysvol
. SERVER3 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.
. SERVER3 failed test frsevent
Starting test: kccevent
. SERVER3 passed test kccevent
Starting test: systemlog
. SERVER3 passed test systemlog
Starting test: VerifyReferences
. SERVER3 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 : midominio
Starting test: CrossRefValidation
. midominio passed test CrossRefValidation
Starting test: CheckSDRefDom
. midominio passed test CheckSDRefDom

Running enterprise tests on : midominio.es
Starting test: Intersite
. midominio.es passed test Intersite
Starting test: FsmoCheck
. midominio.es passed test FsmoCheck

Buenas a todos,

os explico mi situación: Tengo 1 controlador de dominio y 2 secundarios.
Bien, el caso es que tengo muchos problemas con las políticas. Le he

un dcdiag, y el resultado es el siguiente: (A ver si alguien me da

solución, ya que estoy buscando y no encuentro nada. Muchas gracias)


Domain Controller Diagnosis

Performing initial setup:
Done gathering initial info.

Doing initial required tests

Testing server: Nombre-predeterminado-primer-sitio\SERVER1
Starting test: Connectivity
. SERVER1 passed test Connectivity

Testing server: Nombre-predeterminado-primer-sitio\SERVER2
Starting test: Connectivity
. SERVER2 passed test Connectivity

Testing server: Nombre-predeterminado-primer-sitio\SERVER3
Starting test: Connectivity
. SERVER3 passed test Connectivity

Doing primary tests

Testing server: Nombre-predeterminado-primer-sitio\SERVER1
Starting test: Replications
. SERVER1 passed test Replications
Starting test: NCSecDesc
. SERVER1 passed test NCSecDesc
Starting test: NetLogons
. SERVER1 passed test NetLogons
Starting test: Advertising
Warning: SERVER1 is not advertising as a time server.
. SERVER1 failed test Advertising
Starting test: KnowsOfRoleHolders
. SERVER1 passed test KnowsOfRoleHolders
Starting test: RidManager
. SERVER1 passed test RidManager
Starting test: MachineAccount
. SERVER1 passed test MachineAccount
Starting test: Services
. SERVER1 passed test Services
Starting test: ObjectsReplicated
. SERVER1 passed test ObjectsReplicated
Starting test: frssysvol
. SERVER1 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

cause Group Policy problems.
. SERVER1 failed test frsevent
Starting test: kccevent
. SERVER1 passed test kccevent
Starting test: systemlog
. SERVER1 passed test systemlog
Starting test: VerifyReferences
. SERVER1 passed test VerifyReferences

Testing server: Nombre-predeterminado-primer-sitio\SERVER2
Starting test: Replications
REPLICATION LATENCY WARNING
ERROR: Expected notification link is missing.
Source SERVER1
Replication of new changes along this path will be delayed.
This problem should self-correct on the next periodic sync.
. SERVER2 passed test Replications
Starting test: NCSecDesc
. SERVER2 passed test NCSecDesc
Starting test: NetLogons
. SERVER2 passed test NetLogons
Starting test: Advertising
. SERVER2 passed test Advertising
Starting test: KnowsOfRoleHolders
. SERVER2 passed test KnowsOfRoleHolders
Starting test: RidManager
. SERVER2 passed test RidManager
Starting test: MachineAccount
. SERVER2 passed test MachineAccount
Starting test: Services
. SERVER2 passed test Services
Starting test: ObjectsReplicated
. SERVER2 passed test ObjectsReplicated
Starting test: frssysvol
. SERVER2 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

cause Group Policy problems.
. SERVER2 failed test frsevent
Starting test: kccevent
. SERVER2 passed test kccevent
Starting test: systemlog
. SERVER2 passed test systemlog
Starting test: VerifyReferences
. SERVER2 passed test VerifyReferences

Testing server: Nombre-predeterminado-primer-sitio\SERVER3
Starting test: Replications
. SERVER3 passed test Replications
Starting test: NCSecDesc
. SERVER3 passed test NCSecDesc
Starting test: NetLogons
. SERVER3 passed test NetLogons
Starting test: Advertising
. SERVER3 passed test Advertising
Starting test: KnowsOfRoleHolders
. SERVER3 passed test KnowsOfRoleHolders
Starting test: RidManager
. SERVER3 passed test RidManager
Starting test: MachineAccount
. SERVER3 passed test MachineAccount
Starting test: Services
. SERVER3 passed test Services
Starting test: ObjectsReplicated
. SERVER3 passed test ObjectsReplicated
Starting test: frssysvol
. SERVER3 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

cause Group Policy problems.
. SERVER3 failed test frsevent
Starting test: kccevent
. SERVER3 passed test kccevent
Starting test: systemlog
. SERVER3 passed test systemlog
Starting test: VerifyReferences
. SERVER3 passed test VerifyReferences

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

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

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

Running partition tests on : midominio
Starting test: CrossRefValidation
. midominio passed test

Starting test: CheckSDRefDom
. midominio passed test CheckSDRefDom

Running enterprise tests on : midominio.es
Starting test: Intersite
. midominio.es passed test Intersite
Starting test: FsmoCheck
. midominio.es passed test FsmoCheck

Buenas,

me sale el siguiente error:

NS test . . . . . . . . . . . . . : Failed
[WARNING] Cannot find a primary authoritative DNS server for the
name
'SERVER2.midominio.es'. [WSAENOPROTOOPT ]
The name 'SERVER2.midominio.es' may not be registered in DNS.
[WARNING] The DNS entries for this DC are not registered correctly on
DNS server '192.168.1.7'. Please wait for 30 minutes for DNS server
replication.
[WARNING] The DNS entries for this DC are not registered correctly on
DNS server '192.168.1.4'. Please wait for 30 minutes for DNS server
replication.
[FATAL] No DNS servers have the DNS records for this DC registered.

No lo entiendo, ya que esl SERVER2 creo que esta correctamente integrado en
el DNS.


"Marc [MVP Windows]" escribió en el mensaje
news:
Qué dicen el "dcdiag" y el "netdiag"?

Y de paso revisa esto: http://support.microsoft.com/kb/312862/en-us


Saludos,

Marc
MVP Windows Server System - Directory Services
MCSA/MCSE Windows Server 2003
MCTS Exchange 2007 - Configuring
Citrix CCA PS 4.0
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.

"David" escribió en el mensaje
news:
Buenas,

Tengo el siguiente error:

Tipo de suceso: Advertencia

Origen del suceso: NtFrs

Categoría del suceso: Ninguno

Id. suceso: 13508

Fecha: 11/09/2008

Hora: 3:07:20

Usuario: No disponible

Equipo: SERVER3

Descripción:

El Servicio de replicación de archivos tiene problemas habilitando la
replicación desde SERVER1 a SERVER3 para c:\windows\sysvol\domain utilizando
el nombre DNS SERVER1.midominio.es. FRS continuará reintentando.

A continuación observará algunas de las razones por las que aparecerá esta
advertencia.


[1] FRS no puede resolver correctamente el nombre DNS SERVER1.midominio.es
desde este equipo.

[2] FRS no se está ejecutando en SERVER1.midominio.es.

[3] La información de topología de esta replicación en Active Directory aún
no ha sido replicada a todos los controladores de dominio.

"Roberto Di Lello" escribió en el mensaje
news:ejW6i%
David, no tenes algun evento de replicacion???



El dcdiag dice :

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.


si tienes eventos sumalos tambien asi vemos cual puede ser la causa.



Saludos.

Roberto Di'Lello | MCSE 2008 / 2003 - MCSA Messaging 2003 - MCTS |
www.radians.com.ar

Este mensaje se proporciona "como está" sin garantías de ninguna clase,y
no otorga ningún derecho. Ud. asume los riesgos
This posting is provided "AS IS" with no warranties, and confer no rights.
You assume all risk for your use.




"David" escribió en el mensaje de
noticias:
> Buenas a todos,
>
> os explico mi situación: Tengo 1 controlador de dominio y 2 secundarios.
> Bien, el caso es que tengo muchos problemas con las políticas. Le he
pasado
> un dcdiag, y el resultado es el siguiente: (A ver si alguien me da
alguna
> solución, ya que estoy buscando y no encuentro nada. Muchas gracias)
>
>
> Domain Controller Diagnosis
>
> Performing initial setup:
> Done gathering initial info.
>
> Doing initial required tests
>
> Testing server: Nombre-predeterminado-primer-sitio\SERVER1
> Starting test: Connectivity
> . SERVER1 passed test Connectivity
>
> Testing server: Nombre-predeterminado-primer-sitio\SERVER2
> Starting test: Connectivity
> . SERVER2 passed test Connectivity
>
> Testing server: Nombre-predeterminado-primer-sitio\SERVER3
> Starting test: Connectivity
> . SERVER3 passed test Connectivity
>
> Doing primary tests
>
> Testing server: Nombre-predeterminado-primer-sitio\SERVER1
> Starting test: Replications
> . SERVER1 passed test Replications
> Starting test: NCSecDesc
> . SERVER1 passed test NCSecDesc
> Starting test: NetLogons
> . SERVER1 passed test NetLogons
> Starting test: Advertising
> Warning: SERVER1 is not advertising as a time server.
> . SERVER1 failed test Advertising
> Starting test: KnowsOfRoleHolders
> . SERVER1 passed test KnowsOfRoleHolders
> Starting test: RidManager
> . SERVER1 passed test RidManager
> Starting test: MachineAccount
> . SERVER1 passed test MachineAccount
> Starting test: Services
> . SERVER1 passed test Services
> Starting test: ObjectsReplicated
> . SERVER1 passed test ObjectsReplicated
> Starting test: frssysvol
> . SERVER1 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.
> . SERVER1 failed test frsevent
> Starting test: kccevent
> . SERVER1 passed test kccevent
> Starting test: systemlog
> . SERVER1 passed test systemlog
> Starting test: VerifyReferences
> . SERVER1 passed test VerifyReferences
>
> Testing server: Nombre-predeterminado-primer-sitio\SERVER2
> Starting test: Replications
> REPLICATION LATENCY WARNING
> ERROR: Expected notification link is missing.
> Source SERVER1
> Replication of new changes along this path will be delayed.
> This problem should self-correct on the next periodic sync.
> . SERVER2 passed test Replications
> Starting test: NCSecDesc
> . SERVER2 passed test NCSecDesc
> Starting test: NetLogons
> . SERVER2 passed test NetLogons
> Starting test: Advertising
> . SERVER2 passed test Advertising
> Starting test: KnowsOfRoleHolders
> . SERVER2 passed test KnowsOfRoleHolders
> Starting test: RidManager
> . SERVER2 passed test RidManager
> Starting test: MachineAccount
> . SERVER2 passed test MachineAccount
> Starting test: Services
> . SERVER2 passed test Services
> Starting test: ObjectsReplicated
> . SERVER2 passed test ObjectsReplicated
> Starting test: frssysvol
> . SERVER2 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.
> . SERVER2 failed test frsevent
> Starting test: kccevent
> . SERVER2 passed test kccevent
> Starting test: systemlog
> . SERVER2 passed test systemlog
> Starting test: VerifyReferences
> . SERVER2 passed test VerifyReferences
>
> Testing server: Nombre-predeterminado-primer-sitio\SERVER3
> Starting test: Replications
> . SERVER3 passed test Replications
> Starting test: NCSecDesc
> . SERVER3 passed test NCSecDesc
> Starting test: NetLogons
> . SERVER3 passed test NetLogons
> Starting test: Advertising
> . SERVER3 passed test Advertising
> Starting test: KnowsOfRoleHolders
> . SERVER3 passed test KnowsOfRoleHolders
> Starting test: RidManager
> . SERVER3 passed test RidManager
> Starting test: MachineAccount
> . SERVER3 passed test MachineAccount
> Starting test: Services
> . SERVER3 passed test Services
> Starting test: ObjectsReplicated
> . SERVER3 passed test ObjectsReplicated
> Starting test: frssysvol
> . SERVER3 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.
> . SERVER3 failed test frsevent
> Starting test: kccevent
> . SERVER3 passed test kccevent
> Starting test: systemlog
> . SERVER3 passed test systemlog
> Starting test: VerifyReferences
> . SERVER3 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 : midominio
> Starting test: CrossRefValidation
> . midominio passed test
CrossRefValidation
> Starting test: CheckSDRefDom
> . midominio passed test CheckSDRefDom
>
> Running enterprise tests on : midominio.es
> Starting test: Intersite
> . midominio.es passed test Intersite
> Starting test: FsmoCheck
> . midominio.es passed test FsmoCheck
>
>

Buenas,

me sale el siguiente error:

NS test . . . . . . . . . . . . . : Failed
[WARNING] Cannot find a primary authoritative DNS server for the
name
'SERVER2.midominio.es'. [WSAENOPROTOOPT ]
The name 'SERVER2.midominio.es' may not be registered in DNS.
[WARNING] The DNS entries for this DC are not registered correctly on
DNS server '192.168.1.7'. Please wait for 30 minutes for DNS server
replication.
[WARNING] The DNS entries for this DC are not registered correctly on
DNS server '192.168.1.4'. Please wait for 30 minutes for DNS server
replication.
[FATAL] No DNS servers have the DNS records for this DC registered.

No lo entiendo, ya que esl SERVER2 creo que esta correctamente integrado
en
el DNS.


"Marc [MVP Windows]" escribió en el mensaje
news:
Qué dicen el "dcdiag" y el "netdiag"?

Y de paso revisa esto: http://support.microsoft.com/kb/312862/en-us


Saludos,

Marc
MVP Windows Server System - Directory Services
MCSA/MCSE Windows Server 2003
MCTS Exchange 2007 - Configuring
Citrix CCA PS 4.0
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.

"David" escribió en el mensaje
news:
Buenas,

Tengo el siguiente error:

Tipo de suceso: Advertencia

Origen del suceso: NtFrs

Categoría del suceso: Ninguno

Id. suceso: 13508

Fecha: 11/09/2008

Hora: 3:07:20

Usuario: No disponible

Equipo: SERVER3

Descripción:

El Servicio de replicación de archivos tiene problemas habilitando la
replicación desde SERVER1 a SERVER3 para c:\windows\sysvol\domain
utilizando
el nombre DNS SERVER1.midominio.es. FRS continuará reintentando.

A continuación observará algunas de las razones por las que aparecerá esta
advertencia.


[1] FRS no puede resolver correctamente el nombre DNS SERVER1.midominio.es
desde este equipo.

[2] FRS no se está ejecutando en SERVER1.midominio.es.

[3] La información de topología de esta replicación en Active Directory
aún
no ha sido replicada a todos los controladores de dominio.

"Roberto Di Lello" escribió en el mensaje
news:ejW6i%
David, no tenes algun evento de replicacion???



El dcdiag dice :

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.


si tienes eventos sumalos tambien asi vemos cual puede ser la causa.



Saludos.

Roberto Di'Lello | MCSE 2008 / 2003 - MCSA Messaging 2003 - MCTS |
www.radians.com.ar

Este mensaje se proporciona "como está" sin garantías de ninguna clase,y
no otorga ningún derecho. Ud. asume los riesgos
This posting is provided "AS IS" with no warranties, and confer no
rights.
You assume all risk for your use.




"David" escribió en el mensaje de
noticias:
> Buenas a todos,
>
> os explico mi situación: Tengo 1 controlador de dominio y 2
secundarios.
> Bien, el caso es que tengo muchos problemas con las políticas. Le he
pasado
> un dcdiag, y el resultado es el siguiente: (A ver si alguien me da
alguna
> solución, ya que estoy buscando y no encuentro nada. Muchas gracias)
>
>
> Domain Controller Diagnosis
>
> Performing initial setup:
> Done gathering initial info.
>
> Doing initial required tests
>
> Testing server: Nombre-predeterminado-primer-sitio\SERVER1
> Starting test: Connectivity
> . SERVER1 passed test Connectivity
>
> Testing server: Nombre-predeterminado-primer-sitio\SERVER2
> Starting test: Connectivity
> . SERVER2 passed test Connectivity
>
> Testing server: Nombre-predeterminado-primer-sitio\SERVER3
> Starting test: Connectivity
> . SERVER3 passed test Connectivity
>
> Doing primary tests
>
> Testing server: Nombre-predeterminado-primer-sitio\SERVER1
> Starting test: Replications
> . SERVER1 passed test Replications
> Starting test: NCSecDesc
> . SERVER1 passed test NCSecDesc
> Starting test: NetLogons
> . SERVER1 passed test NetLogons
> Starting test: Advertising
> Warning: SERVER1 is not advertising as a time server.
> . SERVER1 failed test Advertising
> Starting test: KnowsOfRoleHolders
> . SERVER1 passed test
KnowsOfRoleHolders
> Starting test: RidManager
> . SERVER1 passed test RidManager
> Starting test: MachineAccount
> . SERVER1 passed test MachineAccount
> Starting test: Services
> . SERVER1 passed test Services
> Starting test: ObjectsReplicated
> . SERVER1 passed test ObjectsReplicated
> Starting test: frssysvol
> . SERVER1 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.
> . SERVER1 failed test frsevent
> Starting test: kccevent
> . SERVER1 passed test kccevent
> Starting test: systemlog
> . SERVER1 passed test systemlog
> Starting test: VerifyReferences
> . SERVER1 passed test VerifyReferences
>
> Testing server: Nombre-predeterminado-primer-sitio\SERVER2
> Starting test: Replications
> REPLICATION LATENCY WARNING
> ERROR: Expected notification link is missing.
> Source SERVER1
> Replication of new changes along this path will be delayed.
> This problem should self-correct on the next periodic sync.
> . SERVER2 passed test Replications
> Starting test: NCSecDesc
> . SERVER2 passed test NCSecDesc
> Starting test: NetLogons
> . SERVER2 passed test NetLogons
> Starting test: Advertising
> . SERVER2 passed test Advertising
> Starting test: KnowsOfRoleHolders
> . SERVER2 passed test
KnowsOfRoleHolders
> Starting test: RidManager
> . SERVER2 passed test RidManager
> Starting test: MachineAccount
> . SERVER2 passed test MachineAccount
> Starting test: Services
> . SERVER2 passed test Services
> Starting test: ObjectsReplicated
> . SERVER2 passed test ObjectsReplicated
> Starting test: frssysvol
> . SERVER2 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.
> . SERVER2 failed test frsevent
> Starting test: kccevent
> . SERVER2 passed test kccevent
> Starting test: systemlog
> . SERVER2 passed test systemlog
> Starting test: VerifyReferences
> . SERVER2 passed test VerifyReferences
>
> Testing server: Nombre-predeterminado-primer-sitio\SERVER3
> Starting test: Replications
> . SERVER3 passed test Replications
> Starting test: NCSecDesc
> . SERVER3 passed test NCSecDesc
> Starting test: NetLogons
> . SERVER3 passed test NetLogons
> Starting test: Advertising
> . SERVER3 passed test Advertising
> Starting test: KnowsOfRoleHolders
> . SERVER3 passed test
KnowsOfRoleHolders
> Starting test: RidManager
> . SERVER3 passed test RidManager
> Starting test: MachineAccount
> . SERVER3 passed test MachineAccount
> Starting test: Services
> . SERVER3 passed test Services
> Starting test: ObjectsReplicated
> . SERVER3 passed test ObjectsReplicated
> Starting test: frssysvol
> . SERVER3 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.
> . SERVER3 failed test frsevent
> Starting test: kccevent
> . SERVER3 passed test kccevent
> Starting test: systemlog
> . SERVER3 passed test systemlog
> Starting test: VerifyReferences
> . SERVER3 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 : midominio
> Starting test: CrossRefValidation
> . midominio passed test
CrossRefValidation
> Starting test: CheckSDRefDom
> . midominio passed test CheckSDRefDom
>
> Running enterprise tests on : midominio.es
> Starting test: Intersite
> . midominio.es passed test Intersite
> Starting test: FsmoCheck
> . midominio.es passed test FsmoCheck
>
>