Replicacion del DA

Sin embargo, el servidor1, que esta en la misma red, me refiero a que esta en
el mismo sitio,con el mismo switch, tiene el mismo problema.
Puede ser por algo que falte hacer en el esquema? Porque antes de elevar los
2003 a Controladores de Dominio, ejecutamos el domainprep para preparar el DA
de 2000 a los 2003.
En lo que es resolucion de nombres y ver unidades de un lado u otro de la
VPN,va todo bien.
Algo mas que pueda probar? Desmontar los DC 2003 y crealos de nuevo?
Cualquier ayuda mas te la agradeceria.
Un saludo

"Marc [MVP Windows]" escribió:

Ok. Y revisa que las réplicas por la VPN funcionen correctamente.


Saludos,

Marc
MVP Windows Shell / User
MCSA Windows Server 2003
Oracle9i Certified Associate (OCA)

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

"Claudio" escribió en el mensaje news:
> De los tres servidores 2 estan en la misma red, 10.0.0.0, Servidor o
> Serivdor1. El servidor2 esta en una 192.168.10.0 y estan conectadas ambas
> redes por una VPN.
> El 10.0.0.50(Servidor) es el W2k, Es el de referencia. Los otros el
> Servidor1(10.0.0.202) y Servidor2 (192.168.10.50).Hay un servidor DNS en cada
> uno, y los objetos alli si estan replicandose bien.
> Modificare el DNS Preferido para que apunte a si mismo,OK?
>
>
>
> "Marc [MVP Windows]" escribió:
>
>> Bien, así por encima (y empezando por abajo):
>>
>> El netdiag en servidor2.main.local muestra que tienes 3 DNS en tres rangos de IPs diferentes, y entiendo que el 213.172.33.34 es del ISP, y por tanto, NO ha de estar aquí, así que fuera que no pinta nada.
>>
>> El 10.0.0.50, de quien es? De "Servidor1"? Si es de este server, cómo están enlazados?
>>
>> "Servidor1", qué configuración DNS tiene? Y "Servidor"?
>>
>> Respecto al DCDiag, te dice que "Servidor" no puede replicarse con "Servidor2". Están en el mismo rango de red? En otra red? Cómo están configurados los "Sites"? Tiene cada Site asociada una "Subnet"?
>>
>> Es más, te dice que la última replicación correcta fue en The last success occurred at 2006-06-08 12:55:23. Si pasan más de 60 días desde la última buena (o sea, que te quedan 30 dias) no podrás volver a sincronizarlos si no es "matándolo" con DCPromo y empezando otra vez.
>>
>>
>> Saludos,
>>
>> Marc
>> MVP Windows Shell/User
>> MCSA Windows Server 2003
>> 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.
>>
>> "Claudio" escribió en el mensaje news:
>> > Gracias, por la respuesta
>> > El resultado del DCDiag es este:
>> >
>> > Domain Controller Diagnosis
>> >
>> > Performing initial setup:
>> > * Verifying that the local machine servidor2, is a DC.
>> > * Connecting to directory service on server servidor2.
>> > * Collecting site info.
>> > * Identifying all servers.
>> > * Identifying all NC cross-refs.
>> > * Found 3 DC(s). Testing 1 of them.
>> > Done gathering initial info.
>> >
>> > Doing initial required tests
>> >
>> > Testing server: Nombre-predeterminado-primer-sitio\SERVIDOR2
>> > Starting test: Connectivity
>> > * Active Directory LDAP Services Check
>> > * Active Directory RPC Services Check
>> > . SERVIDOR2 passed test Connectivity
>> >
>> > Doing primary tests
>> >
>> > Testing server: Nombre-predeterminado-primer-sitio\SERVIDOR2
>> > Starting test: Replications
>> > * Replications Check
>> > [Replications Check,SERVIDOR2] A recent replication attempt failed:
>> > From SERVIDOR to SERVIDOR2
>> > Naming Context: CN=Schema,CN=Configuration,DC=MAIN,DC=local
>> > The replication generated an error (5):
>> > Acceso denegado.
>> > The failure occurred at 2006-07-04 17:53:24.
>> > The last success occurred at 2006-06-08 12:55:23.
>> > 655 failures have occurred since the last success.
>> > [Replications Check,SERVIDOR2] A recent replication attempt failed:
>> > From SERVIDOR to SERVIDOR2
>> > Naming Context: CN=Configuration,DC=MAIN,DC=local
>> > The replication generated an error (5):
>> > Acceso denegado.
>> > The failure occurred at 2006-07-04 18:16:21.
>> > The last success occurred at 2006-06-08 12:55:43.
>> > 3514 failures have occurred since the last success.
>> > [Replications Check,SERVIDOR2] A recent replication attempt failed:
>> > From SERVIDOR to SERVIDOR2
>> > Naming Context: DC=MAIN,DC=local
>> > The replication generated an error (5):
>> > Acceso denegado.
>> > The failure occurred at 2006-07-04 18:18:50.
>> > The last success occurred at 2006-06-08 12:56:54.
>> > 5199 failures have occurred since the last success.
>> > * Replication Latency Check
>> > REPLICATION-RECEIVED LATENCY WARNING
>> > SERVIDOR2: Current time is 2006-07-04 18:19:30.
>> > CN=Schema,CN=Configuration,DC=MAIN,DC=local
>> > Last replication recieved from SERVIDOR at 2006-06-08 12:55:23.
>> > Latency information for 1 entries in the vector were ignored.
>> > 1 were retired Invocations. 0 were either: read-only
>> > replicas and are not verifiably latent, or dc's no longer replicating this
>> > nc. 0 had no latency information (Win2K DC).
>> > CN=Configuration,DC=MAIN,DC=local
>> > Last replication recieved from SERVIDOR at 2006-06-08 12:55:43.
>> > Latency information for 1 entries in the vector were ignored.
>> > 1 were retired Invocations. 0 were either: read-only
>> > replicas and are not verifiably latent, or dc's no longer replicating this
>> > nc. 0 had no latency information (Win2K DC).
>> > DC=MAIN,DC=local
>> > Last replication recieved from SERVIDOR at 2006-06-08 12:56:54.
>> > Latency information for 1 entries in the vector were ignored.
>> > 1 were retired Invocations. 0 were either: read-only
>> > replicas and are not verifiably latent, or dc's no longer replicating this
>> > nc. 0 had no latency information (Win2K DC).
>> > * Replication Site Latency Check
>> > . SERVIDOR2 passed test Replications
>> > Starting test: Topology
>> > * Configuration Topology Integrity Check
>> > * Analyzing the connection topology for
>> > CN=Schema,CN=Configuration,DC=MAIN,DC=local.
>> > * Performing upstream (of target) analysis.
>> > * Performing downstream (of target) analysis.
>> > Downstream topology is disconnected for
>> > CN=Schema,CN=Configuration,DC=MAIN,DC=local.
>> > These servers can't get changes from home server SERVIDOR2:
>> > Nombre-predeterminado-primer-sitio/SERVIDOR
>> > Nombre-predeterminado-primer-sitio/SERVIDOR1
>> > * Analyzing the connection topology for
>> > CN=Configuration,DC=MAIN,DC=local.
>> > * Performing upstream (of target) analysis.
>> > * Performing downstream (of target) analysis.
>> > Downstream topology is disconnected for
>> > CN=Configuration,DC=MAIN,DC=local.
>> > These servers can't get changes from home server SERVIDOR2:
>> > Nombre-predeterminado-primer-sitio/SERVIDOR
>> > Nombre-predeterminado-primer-sitio/SERVIDOR1
>> > * Analyzing the connection topology for DC=MAIN,DC=local.
>> > * Performing upstream (of target) analysis.
>> > * Performing downstream (of target) analysis.
>> > Downstream topology is disconnected for DC=MAIN,DC=local.
>> > These servers can't get changes from home server SERVIDOR2:
>> > Nombre-predeterminado-primer-sitio/SERVIDOR
>> > Nombre-predeterminado-primer-sitio/SERVIDOR1
>> > . SERVIDOR2 failed test Topology
>> > Starting test: CutoffServers
>> > * Configuration Topology Aliveness Check
>> > * Analyzing the alive system replication topology for
>> > CN=Schema,CN=Configuration,DC=MAIN,DC=local.
>> > * Performing upstream (of target) analysis.
>> > * Performing downstream (of target) analysis.
>> > Downstream topology is disconnected for
>> > CN=Schema,CN=Configuration,DC=MAIN,DC=local.
>> > These servers can't get changes from home server SERVIDOR2:
>> > Nombre-predeterminado-primer-sitio/SERVIDOR
>> > Nombre-predeterminado-primer-sitio/SERVIDOR1
>> > * Analyzing the alive system replication topology for
>> > CN=Configuration,DC=MAIN,DC=local.
>> > * Performing upstream (of target) analysis.
>> > * Performing downstream (of target) analysis.
>> > Downstream topology is disconnected for
>> > CN=Configuration,DC=MAIN,DC=local.
>> > These servers can't get changes from home server SERVIDOR2:
>> > Nombre-predeterminado-primer-sitio/SERVIDOR
>> > Nombre-predeterminado-primer-sitio/SERVIDOR1
>> > * Analyzing the alive system replication topology for
>> > DC=MAIN,DC=local.
>> > * Performing upstream (of target) analysis.
>> > * Performing downstream (of target) analysis.
>> > Downstream topology is disconnected for DC=MAIN,DC=local.
>> > These servers can't get changes from home server SERVIDOR2:
>> > Nombre-predeterminado-primer-sitio/SERVIDOR
>> > Nombre-predeterminado-primer-sitio/SERVIDOR1
>> > . SERVIDOR2 failed test CutoffServers
>> > Starting test: NCSecDesc
>> > * Security Permissions Check for
>> > CN=Schema,CN=Configuration,DC=MAIN,DC=local
>> > (Schema,Version 2)
>> > * Security Permissions Check for
>> > CN=Configuration,DC=MAIN,DC=local
>> > (Configuration,Version 2)
>> > * Security Permissions Check for
>> > DC=MAIN,DC=local
>> > (Domain,Version 2)
>> > . SERVIDOR2 passed test NCSecDesc
>> > Starting test: NetLogons
>> > * Network Logons Privileges Check
>> > . SERVIDOR2 passed test NetLogons
>> > Starting test: Advertising
>> > Warning: DsGetDcName returned information for
>> > \\servidor.MAIN.local, when we were trying to reach SERVIDOR2.
>> > Server is not responding or is not considered suitable.
>> > The DC SERVIDOR2 is advertising itself as a DC and having a DS.
>> > The DC SERVIDOR2 is advertising as an LDAP server
>> > The DC SERVIDOR2 is advertising as having a writeable directory
>> > The DC SERVIDOR2 is advertising as a Key Distribution Center
>> > The DC SERVIDOR2 is advertising as a time server
>> > . SERVIDOR2 failed test Advertising
>> > Starting test: KnowsOfRoleHolders
>> > Role Schema Owner = CN=NTDS
>> > Settings,CN=SERVIDOR,CN=Servers,CN=Nombre-predeterminado-primer-sitio,CN=Sites,CN=Configuration,DC=MAIN,DC=local
>> > Role Domain Owner = CN=NTDS
>> > Settings,CN=SERVIDOR,CN=Servers,CN=Nombre-predeterminado-primer-sitio,CN=Sites,CN=Configuration,DC=MAIN,DC=local
>> > Role PDC Owner = CN=NTDS
>> > Settings,CN=SERVIDOR,CN=Servers,CN=Nombre-predeterminado-primer-sitio,CN=Sites,CN=Configuration,DC=MAIN,DC=local
>> > Role Rid Owner = CN=NTDS
>> > Settings,CN=SERVIDOR,CN=Servers,CN=Nombre-predeterminado-primer-sitio,CN=Sites,CN=Configuration,DC=MAIN,DC=local
>> > Role Infrastructure Update Owner = CN=NTDS
>> > Settings,CN=SERVIDOR,CN=Servers,CN=Nombre-predeterminado-primer-sitio,CN=Sites,CN=Configuration,DC=MAIN,DC=local
>> > . SERVIDOR2 passed test KnowsOfRoleHolders
>> > Starting test: RidManager
>> > * Available RID Pool for the Domain is 1604 to 1073741823
>> > * servidor.MAIN.local is the RID Master
>> > * DsBind with RID Master was successful
>> > Warning: attribute rIdSetReferences missing from
>> > CN=SERVIDOR2,OU=Domain Controllers,DC=MAIN,DC=local
>> > Could not get Rid set Reference :failed with 8481: La b£squeda no
>> > pudo obtener atributos de la base de datos.
>> > . SERVIDOR2 failed test RidManager
>> > Starting test: MachineAccount
>> > * SPN found :LDAP/servidor2.MAIN.local/MAIN.local
>> > * SPN found :LDAP/servidor2.MAIN.local
>> > * SPN found :LDAP/SERVIDOR2
>> > * SPN found :LDAP/servidor2.MAIN.local/MAIN
>> > * SPN found
>> > :LDAP/ef52da95-7c94-4b61-bb24-2ea632d696cd._msdcs.MAIN.local
>> > * SPN found
>> > :E3514235-4B06-11D1-AB04-00C04FC2DCD2/ef52da95-7c94-4b61-bb24-2ea632d696cd/MAIN.local
>> > * SPN found :HOST/servidor2.MAIN.local/MAIN.local
>> > * SPN found :HOST/servidor2.MAIN.local
>> > * SPN found :HOST/SERVIDOR2
>> > * SPN found :HOST/servidor2.MAIN.local/MAIN
>> > * SPN found :GC/servidor2.MAIN.local/MAIN.local
>> > . SERVIDOR2 passed test MachineAccount
>> > Starting test: Services
>> > * Checking Service: Dnscache
>> > * Checking Service: NtFrs
>> > * Checking Service: IsmServ
>> > * Checking Service: kdc
>> > * Checking Service: SamSs
>> > * Checking Service: LanmanServer
>> > * Checking Service: LanmanWorkstation
>> > * Checking Service: RpcSs
>> > * Checking Service: w32time
>> > * Checking Service: NETLOGON
>> > . SERVIDOR2 passed test Services
>> > Starting test: OutboundSecureChannels
>> > * The Outbound Secure Channels test
>> > ** Did not run Outbound Secure Channels test
>> > because /testdomain: was not entered
>> > . SERVIDOR2 passed test
>> > OutboundSecureChannels
>> > Starting test: ObjectsReplicated
>> > SERVIDOR2 is in domain DC=MAIN,DC=local
>> > Checking for CN=SERVIDOR2,OU=Domain Controllers,DC=MAIN,DC=local in
>> > domain DC=MAIN,DC=local on 1 servers
>> > Object is up-to-date on all servers.
>> > Checking for CN=NTDS
>> > Settings,CN=SERVIDOR2,CN=Servers,CN=Nombre-predeterminado-primer-sitio,CN=Sites,CN=Configuration,DC=MAIN,DC=local
>> > in domain CN=Configuration,DC=MAIN,DC=local on 1 servers
>> > Object is up-to-date on all servers.
>> > . SERVIDOR2 passed test ObjectsReplicated
>> > Starting test: frssysvol
>> > * The File Replication Service SYSVOL ready test
>> > The registry lookup failed to determine the state of the SYSVOL. The
>> >
>> > error returned was 0 (La operaci¢n se ha completado correctamente.).
>> >
>> > Check the FRS event log to see if the SYSVOL has successfully been
>> >
>> > shared.
>> > . SERVIDOR2 passed test frssysvol
>> > Starting test: frsevent
>> > * The File Replication Service Event log test
>> > There are warning or error events within the last 24 hours after the
>> >
>> > SYSVOL has been shared. Failing SYSVOL replication problems may
>> > cause
>> >
>> > Group Policy problems.
>> > An Warning Event occured. EventID: 0x800034FD
>> > Time Generated: 07/04/2006 16:59:21
>> > (Event String could not be retrieved)
>> > An Warning Event occured. EventID: 0x800034C4
>> > Time Generated: 07/04/2006 17:01:06
>> > (Event String could not be retrieved)
>> > . SERVIDOR2 failed test frsevent
>> > Starting test: kccevent
>> > * The KCC Event log test
>> > Found no KCC errors in Directory Service Event log in the last 15
>> > minutes.

Si dos servidores en la misma red (mismo rango de IPs) no se ven entre ellos, la causa o es mala configuración de la red o es hardware en sí mismo.

Por las IPs, DNS, máscaras, etc. de esos dos DCs que están en la misma red, por favor.


Saludos,

Marc
MVP Windows Shell / User
MCSA Windows Server 2003
Oracle9i Certified Associate (OCA)

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

"Claudio" escribió en el mensaje news:

Sin embargo, el servidor1, que esta en la misma red, me refiero a que esta en
el mismo sitio,con el mismo switch, tiene el mismo problema.
Puede ser por algo que falte hacer en el esquema? Porque antes de elevar los
2003 a Controladores de Dominio, ejecutamos el domainprep para preparar el DA
de 2000 a los 2003.
En lo que es resolucion de nombres y ver unidades de un lado u otro de la
VPN,va todo bien.
Algo mas que pueda probar? Desmontar los DC 2003 y crealos de nuevo?
Cualquier ayuda mas te la agradeceria.
Un saludo

"Marc [MVP Windows]" escribió:

Ok. Y revisa que las réplicas por la VPN funcionen correctamente.


Saludos,

Marc
MVP Windows Shell / User
MCSA Windows Server 2003
Oracle9i Certified Associate (OCA)

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

"Claudio" escribió en el mensaje news:
> De los tres servidores 2 estan en la misma red, 10.0.0.0, Servidor o
> Serivdor1. El servidor2 esta en una 192.168.10.0 y estan conectadas ambas
> redes por una VPN.
> El 10.0.0.50(Servidor) es el W2k, Es el de referencia. Los otros el
> Servidor1(10.0.0.202) y Servidor2 (192.168.10.50).Hay un servidor DNS en cada
> uno, y los objetos alli si estan replicandose bien.
> Modificare el DNS Preferido para que apunte a si mismo,OK?
>
>
>
> "Marc [MVP Windows]" escribió:
>
>> Bien, así por encima (y empezando por abajo):
>>
>> El netdiag en servidor2.main.local muestra que tienes 3 DNS en tres rangos de IPs diferentes, y entiendo que el 213.172.33.34 es del ISP, y por tanto, NO ha de estar aquí, así que fuera que no pinta nada.
>>
>> El 10.0.0.50, de quien es? De "Servidor1"? Si es de este server, cómo están enlazados?
>>
>> "Servidor1", qué configuración DNS tiene? Y "Servidor"?
>>
>> Respecto al DCDiag, te dice que "Servidor" no puede replicarse con "Servidor2". Están en el mismo rango de red? En otra red? Cómo están configurados los "Sites"? Tiene cada Site asociada una "Subnet"?
>>
>> Es más, te dice que la última replicación correcta fue en The last success occurred at 2006-06-08 12:55:23. Si pasan más de 60 días desde la última buena (o sea, que te quedan 30 dias) no podrás volver a sincronizarlos si no es "matándolo" con DCPromo y empezando otra vez.
>>
>>
>> Saludos,
>>
>> Marc
>> MVP Windows Shell/User
>> MCSA Windows Server 2003
>> 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.
>>
>> "Claudio" escribió en el mensaje news:
>> > Gracias, por la respuesta
>> > El resultado del DCDiag es este:
>> >
>> > Domain Controller Diagnosis
>> >
>> > Performing initial setup:
>> > * Verifying that the local machine servidor2, is a DC.
>> > * Connecting to directory service on server servidor2.
>> > * Collecting site info.
>> > * Identifying all servers.
>> > * Identifying all NC cross-refs.
>> > * Found 3 DC(s). Testing 1 of them.
>> > Done gathering initial info.
>> >
>> > Doing initial required tests
>> >
>> > Testing server: Nombre-predeterminado-primer-sitio\SERVIDOR2
>> > Starting test: Connectivity
>> > * Active Directory LDAP Services Check
>> > * Active Directory RPC Services Check
>> > . SERVIDOR2 passed test Connectivity
>> >
>> > Doing primary tests
>> >
>> > Testing server: Nombre-predeterminado-primer-sitio\SERVIDOR2
>> > Starting test: Replications
>> > * Replications Check
>> > [Replications Check,SERVIDOR2] A recent replication attempt failed:
>> > From SERVIDOR to SERVIDOR2
>> > Naming Context: CN=Schema,CN=Configuration,DC=MAIN,DC=local
>> > The replication generated an error (5):
>> > Acceso denegado.
>> > The failure occurred at 2006-07-04 17:53:24.
>> > The last success occurred at 2006-06-08 12:55:23.
>> > 655 failures have occurred since the last success.
>> > [Replications Check,SERVIDOR2] A recent replication attempt failed:
>> > From SERVIDOR to SERVIDOR2
>> > Naming Context: CN=Configuration,DC=MAIN,DC=local
>> > The replication generated an error (5):
>> > Acceso denegado.
>> > The failure occurred at 2006-07-04 18:16:21.
>> > The last success occurred at 2006-06-08 12:55:43.
>> > 3514 failures have occurred since the last success.
>> > [Replications Check,SERVIDOR2] A recent replication attempt failed:
>> > From SERVIDOR to SERVIDOR2
>> > Naming Context: DC=MAIN,DC=local
>> > The replication generated an error (5):
>> > Acceso denegado.
>> > The failure occurred at 2006-07-04 18:18:50.
>> > The last success occurred at 2006-06-08 12:56:54.
>> > 5199 failures have occurred since the last success.
>> > * Replication Latency Check
>> > REPLICATION-RECEIVED LATENCY WARNING
>> > SERVIDOR2: Current time is 2006-07-04 18:19:30.
>> > CN=Schema,CN=Configuration,DC=MAIN,DC=local
>> > Last replication recieved from SERVIDOR at 2006-06-08 12:55:23.
>> > Latency information for 1 entries in the vector were ignored.
>> > 1 were retired Invocations. 0 were either: read-only
>> > replicas and are not verifiably latent, or dc's no longer replicating this
>> > nc. 0 had no latency information (Win2K DC).
>> > CN=Configuration,DC=MAIN,DC=local
>> > Last replication recieved from SERVIDOR at 2006-06-08 12:55:43.
>> > Latency information for 1 entries in the vector were ignored.
>> > 1 were retired Invocations. 0 were either: read-only
>> > replicas and are not verifiably latent, or dc's no longer replicating this
>> > nc. 0 had no latency information (Win2K DC).
>> > DC=MAIN,DC=local
>> > Last replication recieved from SERVIDOR at 2006-06-08 12:56:54.
>> > Latency information for 1 entries in the vector were ignored.
>> > 1 were retired Invocations. 0 were either: read-only
>> > replicas and are not verifiably latent, or dc's no longer replicating this
>> > nc. 0 had no latency information (Win2K DC).
>> > * Replication Site Latency Check
>> > . SERVIDOR2 passed test Replications
>> > Starting test: Topology
>> > * Configuration Topology Integrity Check
>> > * Analyzing the connection topology for
>> > CN=Schema,CN=Configuration,DC=MAIN,DC=local.
>> > * Performing upstream (of target) analysis.
>> > * Performing downstream (of target) analysis.
>> > Downstream topology is disconnected for
>> > CN=Schema,CN=Configuration,DC=MAIN,DC=local.
>> > These servers can't get changes from home server SERVIDOR2:
>> > Nombre-predeterminado-primer-sitio/SERVIDOR
>> > Nombre-predeterminado-primer-sitio/SERVIDOR1
>> > * Analyzing the connection topology for
>> > CN=Configuration,DC=MAIN,DC=local.
>> > * Performing upstream (of target) analysis.
>> > * Performing downstream (of target) analysis.
>> > Downstream topology is disconnected for
>> > CN=Configuration,DC=MAIN,DC=local.
>> > These servers can't get changes from home server SERVIDOR2:
>> > Nombre-predeterminado-primer-sitio/SERVIDOR
>> > Nombre-predeterminado-primer-sitio/SERVIDOR1
>> > * Analyzing the connection topology for DC=MAIN,DC=local.
>> > * Performing upstream (of target) analysis.
>> > * Performing downstream (of target) analysis.
>> > Downstream topology is disconnected for DC=MAIN,DC=local.
>> > These servers can't get changes from home server SERVIDOR2:
>> > Nombre-predeterminado-primer-sitio/SERVIDOR
>> > Nombre-predeterminado-primer-sitio/SERVIDOR1
>> > . SERVIDOR2 failed test Topology
>> > Starting test: CutoffServers
>> > * Configuration Topology Aliveness Check
>> > * Analyzing the alive system replication topology for
>> > CN=Schema,CN=Configuration,DC=MAIN,DC=local.
>> > * Performing upstream (of target) analysis.
>> > * Performing downstream (of target) analysis.
>> > Downstream topology is disconnected for
>> > CN=Schema,CN=Configuration,DC=MAIN,DC=local.
>> > These servers can't get changes from home server SERVIDOR2:
>> > Nombre-predeterminado-primer-sitio/SERVIDOR
>> > Nombre-predeterminado-primer-sitio/SERVIDOR1
>> > * Analyzing the alive system replication topology for
>> > CN=Configuration,DC=MAIN,DC=local.
>> > * Performing upstream (of target) analysis.
>> > * Performing downstream (of target) analysis.
>> > Downstream topology is disconnected for
>> > CN=Configuration,DC=MAIN,DC=local.
>> > These servers can't get changes from home server SERVIDOR2:
>> > Nombre-predeterminado-primer-sitio/SERVIDOR
>> > Nombre-predeterminado-primer-sitio/SERVIDOR1
>> > * Analyzing the alive system replication topology for
>> > DC=MAIN,DC=local.
>> > * Performing upstream (of target) analysis.
>> > * Performing downstream (of target) analysis.
>> > Downstream topology is disconnected for DC=MAIN,DC=local.
>> > These servers can't get changes from home server SERVIDOR2:
>> > Nombre-predeterminado-primer-sitio/SERVIDOR
>> > Nombre-predeterminado-primer-sitio/SERVIDOR1
>> > . SERVIDOR2 failed test CutoffServers
>> > Starting test: NCSecDesc
>> > * Security Permissions Check for
>> > CN=Schema,CN=Configuration,DC=MAIN,DC=local
>> > (Schema,Version 2)
>> > * Security Permissions Check for
>> > CN=Configuration,DC=MAIN,DC=local
>> > (Configuration,Version 2)
>> > * Security Permissions Check for
>> > DC=MAIN,DC=local
>> > (Domain,Version 2)
>> > . SERVIDOR2 passed test NCSecDesc
>> > Starting test: NetLogons
>> > * Network Logons Privileges Check
>> > . SERVIDOR2 passed test NetLogons
>> > Starting test: Advertising
>> > Warning: DsGetDcName returned information for
>> > \\servidor.MAIN.local, when we were trying to reach SERVIDOR2.
>> > Server is not responding or is not considered suitable.
>> > The DC SERVIDOR2 is advertising itself as a DC and having a DS.
>> > The DC SERVIDOR2 is advertising as an LDAP server
>> > The DC SERVIDOR2 is advertising as having a writeable directory
>> > The DC SERVIDOR2 is advertising as a Key Distribution Center
>> > The DC SERVIDOR2 is advertising as a time server
>> > . SERVIDOR2 failed test Advertising
>> > Starting test: KnowsOfRoleHolders
>> > Role Schema Owner = CN=NTDS
>> > Settings,CN=SERVIDOR,CN=Servers,CN=Nombre-predeterminado-primer-sitio,CN=Sites,CN=Configuration,DC=MAIN,DC=local
>> > Role Domain Owner = CN=NTDS
>> > Settings,CN=SERVIDOR,CN=Servers,CN=Nombre-predeterminado-primer-sitio,CN=Sites,CN=Configuration,DC=MAIN,DC=local
>> > Role PDC Owner = CN=NTDS
>> > Settings,CN=SERVIDOR,CN=Servers,CN=Nombre-predeterminado-primer-sitio,CN=Sites,CN=Configuration,DC=MAIN,DC=local
>> > Role Rid Owner = CN=NTDS
>> > Settings,CN=SERVIDOR,CN=Servers,CN=Nombre-predeterminado-primer-sitio,CN=Sites,CN=Configuration,DC=MAIN,DC=local
>> > Role Infrastructure Update Owner = CN=NTDS
>> > Settings,CN=SERVIDOR,CN=Servers,CN=Nombre-predeterminado-primer-sitio,CN=Sites,CN=Configuration,DC=MAIN,DC=local
>> > . SERVIDOR2 passed test KnowsOfRoleHolders
>> > Starting test: RidManager
>> > * Available RID Pool for the Domain is 1604 to 1073741823
>> > * servidor.MAIN.local is the RID Master
>> > * DsBind with RID Master was successful
>> > Warning: attribute rIdSetReferences missing from
>> > CN=SERVIDOR2,OU=Domain Controllers,DC=MAIN,DC=local
>> > Could not get Rid set Reference :failed with 8481: La b£squeda no
>> > pudo obtener atributos de la base de datos.
>> > . SERVIDOR2 failed test RidManager
>> > Starting test: MachineAccount
>> > * SPN found :LDAP/servidor2.MAIN.local/MAIN.local
>> > * SPN found :LDAP/servidor2.MAIN.local
>> > * SPN found :LDAP/SERVIDOR2
>> > * SPN found :LDAP/servidor2.MAIN.local/MAIN
>> > * SPN found
>> > :LDAP/ef52da95-7c94-4b61-bb24-2ea632d696cd._msdcs.MAIN.local
>> > * SPN found
>> > :E3514235-4B06-11D1-AB04-00C04FC2DCD2/ef52da95-7c94-4b61-bb24-2ea632d696cd/MAIN.local
>> > * SPN found :HOST/servidor2.MAIN.local/MAIN.local
>> > * SPN found :HOST/servidor2.MAIN.local
>> > * SPN found :HOST/SERVIDOR2
>> > * SPN found :HOST/servidor2.MAIN.local/MAIN
>> > * SPN found :GC/servidor2.MAIN.local/MAIN.local
>> > . SERVIDOR2 passed test MachineAccount
>> > Starting test: Services
>> > * Checking Service: Dnscache
>> > * Checking Service: NtFrs
>> > * Checking Service: IsmServ
>> > * Checking Service: kdc
>> > * Checking Service: SamSs
>> > * Checking Service: LanmanServer
>> > * Checking Service: LanmanWorkstation
>> > * Checking Service: RpcSs
>> > * Checking Service: w32time
>> > * Checking Service: NETLOGON
>> > . SERVIDOR2 passed test Services
>> > Starting test: OutboundSecureChannels
>> > * The Outbound Secure Channels test
>> > ** Did not run Outbound Secure Channels test
>> > because /testdomain: was not entered
>> > . SERVIDOR2 passed test
>> > OutboundSecureChannels
>> > Starting test: ObjectsReplicated
>> > SERVIDOR2 is in domain DC=MAIN,DC=local
>> > Checking for CN=SERVIDOR2,OU=Domain Controllers,DC=MAIN,DC=local in
>> > domain DC=MAIN,DC=local on 1 servers
>> > Object is up-to-date on all servers.
>> > Checking for CN=NTDS
>> > Settings,CN=SERVIDOR2,CN=Servers,CN=Nombre-predeterminado-primer-sitio,CN=Sites,CN=Configuration,DC=MAIN,DC=local
>> > in domain CN=Configuration,DC=MAIN,DC=local on 1 servers
>> > Object is up-to-date on all servers.
>> > . SERVIDOR2 passed test ObjectsReplicated
>> > Starting test: frssysvol
>> > * The File Replication Service SYSVOL ready test
>> > The registry lookup failed to determine the state of the SYSVOL. The
>> >
>> > error returned was 0 (La operaci¢n se ha completado correctamente.).
>> >
>> > Check the FRS event log to see if the SYSVOL has successfully been
>> >
>> > shared.
>> > . SERVIDOR2 passed test frssysvol
>> > Starting test: frsevent
>> > * The File Replication Service Event log test
>> > There are warning or error events within the last 24 hours after the
>> >
>> > SYSVOL has been shared. Failing SYSVOL replication problems may
>> > cause
>> >
>> > Group Policy problems.
>> > An Warning Event occured. EventID: 0x800034FD
>> > Time Generated: 07/04/2006 16:59:21
>> > (Event String could not be retrieved)
>> > An Warning Event occured. EventID: 0x800034C4
>> > Time Generated: 07/04/2006 17:01:06
>> > (Event String could not be retrieved)
>> > . SERVIDOR2 failed test frsevent
>> > Starting test: kccevent
>> > * The KCC Event log test
>> > Found no KCC errors in Directory Service Event log in the last 15
>> > minutes.

Disculpa, solo te quisiera hacer una ultima pregunta.
Es posible, que aun despues de hacer el adprep, para montar los dominios de
W2k3 R2, haya alguna actualizacion mas del sistema que me faltara hacer al
esquema?
Gracias, disculpa la molestia

"Marc [MVP Windows]" escribió:

Si dos servidores en la misma red (mismo rango de IPs) no se ven entre ellos, la causa o es mala configuración de la red o es hardware en sí mismo.

Por las IPs, DNS, máscaras, etc. de esos dos DCs que están en la misma red, por favor.


Saludos,

Marc
MVP Windows Shell / User
MCSA Windows Server 2003
Oracle9i Certified Associate (OCA)

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

"Claudio" escribió en el mensaje news:
> Sin embargo, el servidor1, que esta en la misma red, me refiero a que esta en
> el mismo sitio,con el mismo switch, tiene el mismo problema.
> Puede ser por algo que falte hacer en el esquema? Porque antes de elevar los
> 2003 a Controladores de Dominio, ejecutamos el domainprep para preparar el DA
> de 2000 a los 2003.
> En lo que es resolucion de nombres y ver unidades de un lado u otro de la
> VPN,va todo bien.
> Algo mas que pueda probar? Desmontar los DC 2003 y crealos de nuevo?
> Cualquier ayuda mas te la agradeceria.
> Un saludo
>
> "Marc [MVP Windows]" escribió:
>
>> Ok. Y revisa que las réplicas por la VPN funcionen correctamente.
>>
>>
>> Saludos,
>>
>> Marc
>> MVP Windows Shell / User
>> MCSA Windows Server 2003
>> Oracle9i Certified Associate (OCA)
>>
>> Este mensaje se proporciona "como está" sin garantías de ninguna clase, y no otorga ningún derecho.
>>
>> "Claudio" escribió en el mensaje news:
>> > De los tres servidores 2 estan en la misma red, 10.0.0.0, Servidor o
>> > Serivdor1. El servidor2 esta en una 192.168.10.0 y estan conectadas ambas
>> > redes por una VPN.
>> > El 10.0.0.50(Servidor) es el W2k, Es el de referencia. Los otros el
>> > Servidor1(10.0.0.202) y Servidor2 (192.168.10.50).Hay un servidor DNS en cada
>> > uno, y los objetos alli si estan replicandose bien.
>> > Modificare el DNS Preferido para que apunte a si mismo,OK?
>> >
>> >
>> >
>> > "Marc [MVP Windows]" escribió:
>> >
>> >> Bien, así por encima (y empezando por abajo):
>> >>
>> >> El netdiag en servidor2.main.local muestra que tienes 3 DNS en tres rangos de IPs diferentes, y entiendo que el 213.172.33.34 es del ISP, y por tanto, NO ha de estar aquí, así que fuera que no pinta nada.
>> >>
>> >> El 10.0.0.50, de quien es? De "Servidor1"? Si es de este server, cómo están enlazados?
>> >>
>> >> "Servidor1", qué configuración DNS tiene? Y "Servidor"?
>> >>
>> >> Respecto al DCDiag, te dice que "Servidor" no puede replicarse con "Servidor2". Están en el mismo rango de red? En otra red? Cómo están configurados los "Sites"? Tiene cada Site asociada una "Subnet"?
>> >>
>> >> Es más, te dice que la última replicación correcta fue en The last success occurred at 2006-06-08 12:55:23. Si pasan más de 60 días desde la última buena (o sea, que te quedan 30 dias) no podrás volver a sincronizarlos si no es "matándolo" con DCPromo y empezando otra vez.
>> >>
>> >>
>> >> Saludos,
>> >>
>> >> Marc
>> >> MVP Windows Shell/User
>> >> MCSA Windows Server 2003
>> >> 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.
>> >>
>> >> "Claudio" escribió en el mensaje news:
>> >> > Gracias, por la respuesta
>> >> > El resultado del DCDiag es este:
>> >> >
>> >> > Domain Controller Diagnosis
>> >> >
>> >> > Performing initial setup:
>> >> > * Verifying that the local machine servidor2, is a DC.
>> >> > * Connecting to directory service on server servidor2.
>> >> > * Collecting site info.
>> >> > * Identifying all servers.
>> >> > * Identifying all NC cross-refs.
>> >> > * Found 3 DC(s). Testing 1 of them.
>> >> > Done gathering initial info.
>> >> >
>> >> > Doing initial required tests
>> >> >
>> >> > Testing server: Nombre-predeterminado-primer-sitio\SERVIDOR2
>> >> > Starting test: Connectivity
>> >> > * Active Directory LDAP Services Check
>> >> > * Active Directory RPC Services Check
>> >> > . SERVIDOR2 passed test Connectivity
>> >> >
>> >> > Doing primary tests
>> >> >
>> >> > Testing server: Nombre-predeterminado-primer-sitio\SERVIDOR2
>> >> > Starting test: Replications
>> >> > * Replications Check
>> >> > [Replications Check,SERVIDOR2] A recent replication attempt failed:
>> >> > From SERVIDOR to SERVIDOR2
>> >> > Naming Context: CN=Schema,CN=Configuration,DC=MAIN,DC=local
>> >> > The replication generated an error (5):
>> >> > Acceso denegado.
>> >> > The failure occurred at 2006-07-04 17:53:24.
>> >> > The last success occurred at 2006-06-08 12:55:23.
>> >> > 655 failures have occurred since the last success.
>> >> > [Replications Check,SERVIDOR2] A recent replication attempt failed:
>> >> > From SERVIDOR to SERVIDOR2
>> >> > Naming Context: CN=Configuration,DC=MAIN,DC=local
>> >> > The replication generated an error (5):
>> >> > Acceso denegado.
>> >> > The failure occurred at 2006-07-04 18:16:21.
>> >> > The last success occurred at 2006-06-08 12:55:43.
>> >> > 3514 failures have occurred since the last success.
>> >> > [Replications Check,SERVIDOR2] A recent replication attempt failed:
>> >> > From SERVIDOR to SERVIDOR2
>> >> > Naming Context: DC=MAIN,DC=local
>> >> > The replication generated an error (5):
>> >> > Acceso denegado.
>> >> > The failure occurred at 2006-07-04 18:18:50.
>> >> > The last success occurred at 2006-06-08 12:56:54.
>> >> > 5199 failures have occurred since the last success.
>> >> > * Replication Latency Check
>> >> > REPLICATION-RECEIVED LATENCY WARNING
>> >> > SERVIDOR2: Current time is 2006-07-04 18:19:30.
>> >> > CN=Schema,CN=Configuration,DC=MAIN,DC=local
>> >> > Last replication recieved from SERVIDOR at 2006-06-08 12:55:23.
>> >> > Latency information for 1 entries in the vector were ignored.
>> >> > 1 were retired Invocations. 0 were either: read-only
>> >> > replicas and are not verifiably latent, or dc's no longer replicating this
>> >> > nc. 0 had no latency information (Win2K DC).
>> >> > CN=Configuration,DC=MAIN,DC=local
>> >> > Last replication recieved from SERVIDOR at 2006-06-08 12:55:43.
>> >> > Latency information for 1 entries in the vector were ignored.
>> >> > 1 were retired Invocations. 0 were either: read-only
>> >> > replicas and are not verifiably latent, or dc's no longer replicating this
>> >> > nc. 0 had no latency information (Win2K DC).
>> >> > DC=MAIN,DC=local
>> >> > Last replication recieved from SERVIDOR at 2006-06-08 12:56:54.
>> >> > Latency information for 1 entries in the vector were ignored.
>> >> > 1 were retired Invocations. 0 were either: read-only
>> >> > replicas and are not verifiably latent, or dc's no longer replicating this
>> >> > nc. 0 had no latency information (Win2K DC).
>> >> > * Replication Site Latency Check
>> >> > . SERVIDOR2 passed test Replications
>> >> > Starting test: Topology
>> >> > * Configuration Topology Integrity Check
>> >> > * Analyzing the connection topology for
>> >> > CN=Schema,CN=Configuration,DC=MAIN,DC=local.
>> >> > * Performing upstream (of target) analysis.
>> >> > * Performing downstream (of target) analysis.
>> >> > Downstream topology is disconnected for
>> >> > CN=Schema,CN=Configuration,DC=MAIN,DC=local.
>> >> > These servers can't get changes from home server SERVIDOR2:
>> >> > Nombre-predeterminado-primer-sitio/SERVIDOR
>> >> > Nombre-predeterminado-primer-sitio/SERVIDOR1
>> >> > * Analyzing the connection topology for
>> >> > CN=Configuration,DC=MAIN,DC=local.
>> >> > * Performing upstream (of target) analysis.
>> >> > * Performing downstream (of target) analysis.
>> >> > Downstream topology is disconnected for
>> >> > CN=Configuration,DC=MAIN,DC=local.
>> >> > These servers can't get changes from home server SERVIDOR2:
>> >> > Nombre-predeterminado-primer-sitio/SERVIDOR
>> >> > Nombre-predeterminado-primer-sitio/SERVIDOR1
>> >> > * Analyzing the connection topology for DC=MAIN,DC=local.
>> >> > * Performing upstream (of target) analysis.
>> >> > * Performing downstream (of target) analysis.
>> >> > Downstream topology is disconnected for DC=MAIN,DC=local.
>> >> > These servers can't get changes from home server SERVIDOR2:
>> >> > Nombre-predeterminado-primer-sitio/SERVIDOR
>> >> > Nombre-predeterminado-primer-sitio/SERVIDOR1
>> >> > . SERVIDOR2 failed test Topology
>> >> > Starting test: CutoffServers
>> >> > * Configuration Topology Aliveness Check
>> >> > * Analyzing the alive system replication topology for
>> >> > CN=Schema,CN=Configuration,DC=MAIN,DC=local.
>> >> > * Performing upstream (of target) analysis.
>> >> > * Performing downstream (of target) analysis.
>> >> > Downstream topology is disconnected for
>> >> > CN=Schema,CN=Configuration,DC=MAIN,DC=local.
>> >> > These servers can't get changes from home server SERVIDOR2:
>> >> > Nombre-predeterminado-primer-sitio/SERVIDOR
>> >> > Nombre-predeterminado-primer-sitio/SERVIDOR1
>> >> > * Analyzing the alive system replication topology for
>> >> > CN=Configuration,DC=MAIN,DC=local.
>> >> > * Performing upstream (of target) analysis.
>> >> > * Performing downstream (of target) analysis.
>> >> > Downstream topology is disconnected for
>> >> > CN=Configuration,DC=MAIN,DC=local.
>> >> > These servers can't get changes from home server SERVIDOR2:
>> >> > Nombre-predeterminado-primer-sitio/SERVIDOR
>> >> > Nombre-predeterminado-primer-sitio/SERVIDOR1
>> >> > * Analyzing the alive system replication topology for
>> >> > DC=MAIN,DC=local.
>> >> > * Performing upstream (of target) analysis.
>> >> > * Performing downstream (of target) analysis.
>> >> > Downstream topology is disconnected for DC=MAIN,DC=local.
>> >> > These servers can't get changes from home server SERVIDOR2:
>> >> > Nombre-predeterminado-primer-sitio/SERVIDOR
>> >> > Nombre-predeterminado-primer-sitio/SERVIDOR1
>> >> > . SERVIDOR2 failed test CutoffServers
>> >> > Starting test: NCSecDesc
>> >> > * Security Permissions Check for
>> >> > CN=Schema,CN=Configuration,DC=MAIN,DC=local
>> >> > (Schema,Version 2)
>> >> > * Security Permissions Check for
>> >> > CN=Configuration,DC=MAIN,DC=local
>> >> > (Configuration,Version 2)
>> >> > * Security Permissions Check for
>> >> > DC=MAIN,DC=local
>> >> > (Domain,Version 2)
>> >> > . SERVIDOR2 passed test NCSecDesc
>> >> > Starting test: NetLogons
>> >> > * Network Logons Privileges Check
>> >> > . SERVIDOR2 passed test NetLogons
>> >> > Starting test: Advertising
>> >> > Warning: DsGetDcName returned information for
>> >> > \\servidor.MAIN.local, when we were trying to reach SERVIDOR2.
>> >> > Server is not responding or is not considered suitable.
>> >> > The DC SERVIDOR2 is advertising itself as a DC and having a DS.
>> >> > The DC SERVIDOR2 is advertising as an LDAP server
>> >> > The DC SERVIDOR2 is advertising as having a writeable directory
>> >> > The DC SERVIDOR2 is advertising as a Key Distribution Center
>> >> > The DC SERVIDOR2 is advertising as a time server
>> >> > . SERVIDOR2 failed test Advertising
>> >> > Starting test: KnowsOfRoleHolders
>> >> > Role Schema Owner = CN=NTDS
>> >> > Settings,CN=SERVIDOR,CN=Servers,CN=Nombre-predeterminado-primer-sitio,CN=Sites,CN=Configuration,DC=MAIN,DC=local
>> >> > Role Domain Owner = CN=NTDS
>> >> > Settings,CN=SERVIDOR,CN=Servers,CN=Nombre-predeterminado-primer-sitio,CN=Sites,CN=Configuration,DC=MAIN,DC=local
>> >> > Role PDC Owner = CN=NTDS
>> >> > Settings,CN=SERVIDOR,CN=Servers,CN=Nombre-predeterminado-primer-sitio,CN=Sites,CN=Configuration,DC=MAIN,DC=local
>> >> > Role Rid Owner = CN=NTDS
>> >> > Settings,CN=SERVIDOR,CN=Servers,CN=Nombre-predeterminado-primer-sitio,CN=Sites,CN=Configuration,DC=MAIN,DC=local
>> >> > Role Infrastructure Update Owner = CN=NTDS
>> >> > Settings,CN=SERVIDOR,CN=Servers,CN=Nombre-predeterminado-primer-sitio,CN=Sites,CN=Configuration,DC=MAIN,DC=local
>> >> > . SERVIDOR2 passed test KnowsOfRoleHolders
>> >> > Starting test: RidManager
>> >> > * Available RID Pool for the Domain is 1604 to 1073741823
>> >> > * servidor.MAIN.local is the RID Master
>> >> > * DsBind with RID Master was successful
>> >> > Warning: attribute rIdSetReferences missing from
>> >> > CN=SERVIDOR2,OU=Domain Controllers,DC=MAIN,DC=local
>> >> > Could not get Rid set Reference :failed with 8481: La b£squeda no
>> >> > pudo obtener atributos de la base de datos.
>> >> > . SERVIDOR2 failed test RidManager
>> >> > Starting test: MachineAccount
>> >> > * SPN found :LDAP/servidor2.MAIN.local/MAIN.local
>> >> > * SPN found :LDAP/servidor2.MAIN.local
>> >> > * SPN found :LDAP/SERVIDOR2
>> >> > * SPN found :LDAP/servidor2.MAIN.local/MAIN
>> >> > * SPN found
>> >> > :LDAP/ef52da95-7c94-4b61-bb24-2ea632d696cd._msdcs.MAIN.local
>> >> > * SPN found
>> >> > :E3514235-4B06-11D1-AB04-00C04FC2DCD2/ef52da95-7c94-4b61-bb24-2ea632d696cd/MAIN.local
>> >> > * SPN found :HOST/servidor2.MAIN.local/MAIN.local
>> >> > * SPN found :HOST/servidor2.MAIN.local
>> >> > * SPN found :HOST/SERVIDOR2
>> >> > * SPN found :HOST/servidor2.MAIN.local/MAIN
>> >> > * SPN found :GC/servidor2.MAIN.local/MAIN.local
>> >> > . SERVIDOR2 passed test MachineAccount
>> >> > Starting test: Services
>> >> > * Checking Service: Dnscache
>> >> > * Checking Service: NtFrs
>> >> > * Checking Service: IsmServ
>> >> > * Checking Service: kdc
>> >> > * Checking Service: SamSs
>> >> > * Checking Service: LanmanServer
>> >> > * Checking Service: LanmanWorkstation
>> >> > * Checking Service: RpcSs
>> >> > * Checking Service: w32time
>> >> > * Checking Service: NETLOGON
>> >> > . SERVIDOR2 passed test Services
>> >> > Starting test: OutboundSecureChannels
>> >> > * The Outbound Secure Channels test
>> >> > ** Did not run Outbound Secure Channels test
>> >> > because /testdomain: was not entered
>> >> > . SERVIDOR2 passed test
>> >> > OutboundSecureChannels
>> >> > Starting test: ObjectsReplicated
>> >> > SERVIDOR2 is in domain DC=MAIN,DC=local
>> >> > Checking for CN=SERVIDOR2,OU=Domain Controllers,DC=MAIN,DC=local in
>> >> > domain DC=MAIN,DC=local on 1 servers
>> >> > Object is up-to-date on all servers.
>> >> > Checking for CN=NTDS
>> >> > Settings,CN=SERVIDOR2,CN=Servers,CN=Nombre-predeterminado-primer-sitio,CN=Sites,CN=Configuration,DC=MAIN,DC=local
>> >> > in domain CN=Configuration,DC=MAIN,DC=local on 1 servers
>> >> > Object is up-to-date on all servers.
>> >> > . SERVIDOR2 passed test ObjectsReplicated

No, o no hubieras podido hacer DC al R2.


Saludos,

Marc
MVP Windows Shell / User
MCSA Windows Server 2003
Oracle9i Certified Associate (OCA)

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

"Claudio" escribió en el mensaje news:

Disculpa, solo te quisiera hacer una ultima pregunta.
Es posible, que aun despues de hacer el adprep, para montar los dominios de
W2k3 R2, haya alguna actualizacion mas del sistema que me faltara hacer al
esquema?
Gracias, disculpa la molestia

"Marc [MVP Windows]" escribió:

Si dos servidores en la misma red (mismo rango de IPs) no se ven entre ellos, la causa o es mala configuración de la red o es hardware en sí mismo.

Por las IPs, DNS, máscaras, etc. de esos dos DCs que están en la misma red, por favor.


Saludos,

Marc
MVP Windows Shell / User
MCSA Windows Server 2003
Oracle9i Certified Associate (OCA)

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

"Claudio" escribió en el mensaje news:
> Sin embargo, el servidor1, que esta en la misma red, me refiero a que esta en
> el mismo sitio,con el mismo switch, tiene el mismo problema.
> Puede ser por algo que falte hacer en el esquema? Porque antes de elevar los
> 2003 a Controladores de Dominio, ejecutamos el domainprep para preparar el DA
> de 2000 a los 2003.
> En lo que es resolucion de nombres y ver unidades de un lado u otro de la
> VPN,va todo bien.
> Algo mas que pueda probar? Desmontar los DC 2003 y crealos de nuevo?
> Cualquier ayuda mas te la agradeceria.
> Un saludo
>
> "Marc [MVP Windows]" escribió:
>
>> Ok. Y revisa que las réplicas por la VPN funcionen correctamente.
>>
>>
>> Saludos,
>>
>> Marc
>> MVP Windows Shell / User
>> MCSA Windows Server 2003
>> Oracle9i Certified Associate (OCA)
>>
>> Este mensaje se proporciona "como está" sin garantías de ninguna clase, y no otorga ningún derecho.
>>
>> "Claudio" escribió en el mensaje news:
>> > De los tres servidores 2 estan en la misma red, 10.0.0.0, Servidor o
>> > Serivdor1. El servidor2 esta en una 192.168.10.0 y estan conectadas ambas
>> > redes por una VPN.
>> > El 10.0.0.50(Servidor) es el W2k, Es el de referencia. Los otros el
>> > Servidor1(10.0.0.202) y Servidor2 (192.168.10.50).Hay un servidor DNS en cada
>> > uno, y los objetos alli si estan replicandose bien.
>> > Modificare el DNS Preferido para que apunte a si mismo,OK?
>> >
>> >
>> >
>> > "Marc [MVP Windows]" escribió:
>> >
>> >> Bien, así por encima (y empezando por abajo):
>> >>
>> >> El netdiag en servidor2.main.local muestra que tienes 3 DNS en tres rangos de IPs diferentes, y entiendo que el 213.172.33.34 es del ISP, y por tanto, NO ha de estar aquí, así que fuera que no pinta nada.
>> >>
>> >> El 10.0.0.50, de quien es? De "Servidor1"? Si es de este server, cómo están enlazados?
>> >>
>> >> "Servidor1", qué configuración DNS tiene? Y "Servidor"?
>> >>
>> >> Respecto al DCDiag, te dice que "Servidor" no puede replicarse con "Servidor2". Están en el mismo rango de red? En otra red? Cómo están configurados los "Sites"? Tiene cada Site asociada una "Subnet"?
>> >>
>> >> Es más, te dice que la última replicación correcta fue en The last success occurred at 2006-06-08 12:55:23. Si pasan más de 60 días desde la última buena (o sea, que te quedan 30 dias) no podrás volver a sincronizarlos si no es "matándolo" con DCPromo y empezando otra vez.
>> >>
>> >>
>> >> Saludos,
>> >>
>> >> Marc
>> >> MVP Windows Shell/User
>> >> MCSA Windows Server 2003
>> >> 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.
>> >>
>> >> "Claudio" escribió en el mensaje news:
>> >> > Gracias, por la respuesta
>> >> > El resultado del DCDiag es este:
>> >> >
>> >> > Domain Controller Diagnosis
>> >> >
>> >> > Performing initial setup:
>> >> > * Verifying that the local machine servidor2, is a DC.
>> >> > * Connecting to directory service on server servidor2.
>> >> > * Collecting site info.
>> >> > * Identifying all servers.
>> >> > * Identifying all NC cross-refs.
>> >> > * Found 3 DC(s). Testing 1 of them.
>> >> > Done gathering initial info.
>> >> >
>> >> > Doing initial required tests
>> >> >
>> >> > Testing server: Nombre-predeterminado-primer-sitio\SERVIDOR2
>> >> > Starting test: Connectivity
>> >> > * Active Directory LDAP Services Check
>> >> > * Active Directory RPC Services Check
>> >> > . SERVIDOR2 passed test Connectivity
>> >> >
>> >> > Doing primary tests
>> >> >
>> >> > Testing server: Nombre-predeterminado-primer-sitio\SERVIDOR2
>> >> > Starting test: Replications
>> >> > * Replications Check
>> >> > [Replications Check,SERVIDOR2] A recent replication attempt failed:
>> >> > From SERVIDOR to SERVIDOR2
>> >> > Naming Context: CN=Schema,CN=Configuration,DC=MAIN,DC=local
>> >> > The replication generated an error (5):
>> >> > Acceso denegado.
>> >> > The failure occurred at 2006-07-04 17:53:24.
>> >> > The last success occurred at 2006-06-08 12:55:23.
>> >> > 655 failures have occurred since the last success.
>> >> > [Replications Check,SERVIDOR2] A recent replication attempt failed:
>> >> > From SERVIDOR to SERVIDOR2
>> >> > Naming Context: CN=Configuration,DC=MAIN,DC=local
>> >> > The replication generated an error (5):
>> >> > Acceso denegado.
>> >> > The failure occurred at 2006-07-04 18:16:21.
>> >> > The last success occurred at 2006-06-08 12:55:43.
>> >> > 3514 failures have occurred since the last success.
>> >> > [Replications Check,SERVIDOR2] A recent replication attempt failed:
>> >> > From SERVIDOR to SERVIDOR2
>> >> > Naming Context: DC=MAIN,DC=local
>> >> > The replication generated an error (5):
>> >> > Acceso denegado.
>> >> > The failure occurred at 2006-07-04 18:18:50.
>> >> > The last success occurred at 2006-06-08 12:56:54.
>> >> > 5199 failures have occurred since the last success.
>> >> > * Replication Latency Check
>> >> > REPLICATION-RECEIVED LATENCY WARNING
>> >> > SERVIDOR2: Current time is 2006-07-04 18:19:30.
>> >> > CN=Schema,CN=Configuration,DC=MAIN,DC=local
>> >> > Last replication recieved from SERVIDOR at 2006-06-08 12:55:23.
>> >> > Latency information for 1 entries in the vector were ignored.
>> >> > 1 were retired Invocations. 0 were either: read-only
>> >> > replicas and are not verifiably latent, or dc's no longer replicating this
>> >> > nc. 0 had no latency information (Win2K DC).
>> >> > CN=Configuration,DC=MAIN,DC=local
>> >> > Last replication recieved from SERVIDOR at 2006-06-08 12:55:43.
>> >> > Latency information for 1 entries in the vector were ignored.
>> >> > 1 were retired Invocations. 0 were either: read-only
>> >> > replicas and are not verifiably latent, or dc's no longer replicating this
>> >> > nc. 0 had no latency information (Win2K DC).
>> >> > DC=MAIN,DC=local
>> >> > Last replication recieved from SERVIDOR at 2006-06-08 12:56:54.
>> >> > Latency information for 1 entries in the vector were ignored.
>> >> > 1 were retired Invocations. 0 were either: read-only
>> >> > replicas and are not verifiably latent, or dc's no longer replicating this
>> >> > nc. 0 had no latency information (Win2K DC).
>> >> > * Replication Site Latency Check
>> >> > . SERVIDOR2 passed test Replications
>> >> > Starting test: Topology
>> >> > * Configuration Topology Integrity Check
>> >> > * Analyzing the connection topology for
>> >> > CN=Schema,CN=Configuration,DC=MAIN,DC=local.
>> >> > * Performing upstream (of target) analysis.
>> >> > * Performing downstream (of target) analysis.
>> >> > Downstream topology is disconnected for
>> >> > CN=Schema,CN=Configuration,DC=MAIN,DC=local.
>> >> > These servers can't get changes from home server SERVIDOR2:
>> >> > Nombre-predeterminado-primer-sitio/SERVIDOR
>> >> > Nombre-predeterminado-primer-sitio/SERVIDOR1
>> >> > * Analyzing the connection topology for
>> >> > CN=Configuration,DC=MAIN,DC=local.
>> >> > * Performing upstream (of target) analysis.
>> >> > * Performing downstream (of target) analysis.
>> >> > Downstream topology is disconnected for
>> >> > CN=Configuration,DC=MAIN,DC=local.
>> >> > These servers can't get changes from home server SERVIDOR2:
>> >> > Nombre-predeterminado-primer-sitio/SERVIDOR
>> >> > Nombre-predeterminado-primer-sitio/SERVIDOR1
>> >> > * Analyzing the connection topology for DC=MAIN,DC=local.
>> >> > * Performing upstream (of target) analysis.
>> >> > * Performing downstream (of target) analysis.
>> >> > Downstream topology is disconnected for DC=MAIN,DC=local.
>> >> > These servers can't get changes from home server SERVIDOR2:
>> >> > Nombre-predeterminado-primer-sitio/SERVIDOR
>> >> > Nombre-predeterminado-primer-sitio/SERVIDOR1
>> >> > . SERVIDOR2 failed test Topology
>> >> > Starting test: CutoffServers
>> >> > * Configuration Topology Aliveness Check
>> >> > * Analyzing the alive system replication topology for
>> >> > CN=Schema,CN=Configuration,DC=MAIN,DC=local.
>> >> > * Performing upstream (of target) analysis.
>> >> > * Performing downstream (of target) analysis.
>> >> > Downstream topology is disconnected for
>> >> > CN=Schema,CN=Configuration,DC=MAIN,DC=local.
>> >> > These servers can't get changes from home server SERVIDOR2:
>> >> > Nombre-predeterminado-primer-sitio/SERVIDOR
>> >> > Nombre-predeterminado-primer-sitio/SERVIDOR1
>> >> > * Analyzing the alive system replication topology for
>> >> > CN=Configuration,DC=MAIN,DC=local.
>> >> > * Performing upstream (of target) analysis.
>> >> > * Performing downstream (of target) analysis.
>> >> > Downstream topology is disconnected for
>> >> > CN=Configuration,DC=MAIN,DC=local.
>> >> > These servers can't get changes from home server SERVIDOR2:
>> >> > Nombre-predeterminado-primer-sitio/SERVIDOR
>> >> > Nombre-predeterminado-primer-sitio/SERVIDOR1
>> >> > * Analyzing the alive system replication topology for
>> >> > DC=MAIN,DC=local.
>> >> > * Performing upstream (of target) analysis.
>> >> > * Performing downstream (of target) analysis.
>> >> > Downstream topology is disconnected for DC=MAIN,DC=local.
>> >> > These servers can't get changes from home server SERVIDOR2:
>> >> > Nombre-predeterminado-primer-sitio/SERVIDOR
>> >> > Nombre-predeterminado-primer-sitio/SERVIDOR1
>> >> > . SERVIDOR2 failed test CutoffServers
>> >> > Starting test: NCSecDesc
>> >> > * Security Permissions Check for
>> >> > CN=Schema,CN=Configuration,DC=MAIN,DC=local
>> >> > (Schema,Version 2)
>> >> > * Security Permissions Check for
>> >> > CN=Configuration,DC=MAIN,DC=local
>> >> > (Configuration,Version 2)
>> >> > * Security Permissions Check for
>> >> > DC=MAIN,DC=local
>> >> > (Domain,Version 2)
>> >> > . SERVIDOR2 passed test NCSecDesc
>> >> > Starting test: NetLogons
>> >> > * Network Logons Privileges Check
>> >> > . SERVIDOR2 passed test NetLogons
>> >> > Starting test: Advertising
>> >> > Warning: DsGetDcName returned information for
>> >> > \\servidor.MAIN.local, when we were trying to reach SERVIDOR2.
>> >> > Server is not responding or is not considered suitable.
>> >> > The DC SERVIDOR2 is advertising itself as a DC and having a DS.
>> >> > The DC SERVIDOR2 is advertising as an LDAP server
>> >> > The DC SERVIDOR2 is advertising as having a writeable directory
>> >> > The DC SERVIDOR2 is advertising as a Key Distribution Center
>> >> > The DC SERVIDOR2 is advertising as a time server
>> >> > . SERVIDOR2 failed test Advertising
>> >> > Starting test: KnowsOfRoleHolders
>> >> > Role Schema Owner = CN=NTDS
>> >> > Settings,CN=SERVIDOR,CN=Servers,CN=Nombre-predeterminado-primer-sitio,CN=Sites,CN=Configuration,DC=MAIN,DC=local
>> >> > Role Domain Owner = CN=NTDS
>> >> > Settings,CN=SERVIDOR,CN=Servers,CN=Nombre-predeterminado-primer-sitio,CN=Sites,CN=Configuration,DC=MAIN,DC=local
>> >> > Role PDC Owner = CN=NTDS
>> >> > Settings,CN=SERVIDOR,CN=Servers,CN=Nombre-predeterminado-primer-sitio,CN=Sites,CN=Configuration,DC=MAIN,DC=local
>> >> > Role Rid Owner = CN=NTDS
>> >> > Settings,CN=SERVIDOR,CN=Servers,CN=Nombre-predeterminado-primer-sitio,CN=Sites,CN=Configuration,DC=MAIN,DC=local
>> >> > Role Infrastructure Update Owner = CN=NTDS
>> >> > Settings,CN=SERVIDOR,CN=Servers,CN=Nombre-predeterminado-primer-sitio,CN=Sites,CN=Configuration,DC=MAIN,DC=local
>> >> > . SERVIDOR2 passed test KnowsOfRoleHolders
>> >> > Starting test: RidManager
>> >> > * Available RID Pool for the Domain is 1604 to 1073741823
>> >> > * servidor.MAIN.local is the RID Master
>> >> > * DsBind with RID Master was successful
>> >> > Warning: attribute rIdSetReferences missing from
>> >> > CN=SERVIDOR2,OU=Domain Controllers,DC=MAIN,DC=local
>> >> > Could not get Rid set Reference :failed with 8481: La b£squeda no
>> >> > pudo obtener atributos de la base de datos.
>> >> > . SERVIDOR2 failed test RidManager
>> >> > Starting test: MachineAccount
>> >> > * SPN found :LDAP/servidor2.MAIN.local/MAIN.local
>> >> > * SPN found :LDAP/servidor2.MAIN.local
>> >> > * SPN found :LDAP/SERVIDOR2
>> >> > * SPN found :LDAP/servidor2.MAIN.local/MAIN
>> >> > * SPN found
>> >> > :LDAP/ef52da95-7c94-4b61-bb24-2ea632d696cd._msdcs.MAIN.local
>> >> > * SPN found
>> >> > :E3514235-4B06-11D1-AB04-00C04FC2DCD2/ef52da95-7c94-4b61-bb24-2ea632d696cd/MAIN.local
>> >> > * SPN found :HOST/servidor2.MAIN.local/MAIN.local
>> >> > * SPN found :HOST/servidor2.MAIN.local
>> >> > * SPN found :HOST/SERVIDOR2
>> >> > * SPN found :HOST/servidor2.MAIN.local/MAIN
>> >> > * SPN found :GC/servidor2.MAIN.local/MAIN.local
>> >> > . SERVIDOR2 passed test MachineAccount
>> >> > Starting test: Services
>> >> > * Checking Service: Dnscache
>> >> > * Checking Service: NtFrs
>> >> > * Checking Service: IsmServ
>> >> > * Checking Service: kdc
>> >> > * Checking Service: SamSs
>> >> > * Checking Service: LanmanServer
>> >> > * Checking Service: LanmanWorkstation
>> >> > * Checking Service: RpcSs
>> >> > * Checking Service: w32time
>> >> > * Checking Service: NETLOGON
>> >> > . SERVIDOR2 passed test Services
>> >> > Starting test: OutboundSecureChannels
>> >> > * The Outbound Secure Channels test
>> >> > ** Did not run Outbound Secure Channels test
>> >> > because /testdomain: was not entered
>> >> > . SERVIDOR2 passed test
>> >> > OutboundSecureChannels
>> >> > Starting test: ObjectsReplicated
>> >> > SERVIDOR2 is in domain DC=MAIN,DC=local
>> >> > Checking for CN=SERVIDOR2,OU=Domain Controllers,DC=MAIN,DC=local in
>> >> > domain DC=MAIN,DC=local on 1 servers
>> >> > Object is up-to-date on all servers.
>> >> > Checking for CN=NTDS
>> >> > Settings,CN=SERVIDOR2,CN=Servers,CN=Nombre-predeterminado-primer-sitio,CN=Sites,CN=Configuration,DC=MAIN,DC=local
>> >> > in domain CN=Configuration,DC=MAIN,DC=local on 1 servers
>> >> > Object is up-to-date on all servers.
>> >> > . SERVIDOR2 passed test ObjectsReplicated