Forums Últimos mensajes - Powered by IBM
 
Tags Palabras claves

Replicacion del DA

04/07/2006 - 17:09 por Claudio | Informe spam
Ayuda Hacer una pregunta
Buenos Dias, Tengo un DC Windows 2000 SP4, que es el root domain, y 2 Windows
2003 Std SP1 R2, que ambos se elevaron a controladores de dominio.
Pero el servicio de replicacion no logra pasar la info desde el 2000 a los
otros servidores,el error es el Id. 13508, "Tiene problemas habilitando la
replicacion desde W2kServer a W2k3server"
Alguna sugerencia?
email Siga el debateRespuesta 9 respuestasRespuesta Tengo una respuesta

Preguntas similare

Mostrar todos los temas similares

Leer las respuestas

#1 Marc [MVP Windows]
04/07/2006 - 17:42 | Informe spam
Pasa un DCdiag y un Netdiag a esos servidores y por por aquí los resultados.

Respecto al ID del error: http://www.eventid.net/display.asp?eventid508&eventnoe85&source=FRS&phase=1


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:
Buenos Dias, Tengo un DC Windows 2000 SP4, que es el root domain, y 2 Windows
2003 Std SP1 R2, que ambos se elevaron a controladores de dominio.
Pero el servicio de replicacion no logra pasar la info desde el 2000 a los
otros servidores,el error es el Id. 13508, "Tiene problemas habilitando la
replicacion desde W2kServer a W2k3server"
Alguna sugerencia?
Respuesta Responder a este mensaje
#2 Claudio
04/07/2006 - 18:20 | Informe spam
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.
. SERVIDOR2 passed test kccevent
Starting test: systemlog
* The System Event log test
Found no errors in System Event log in the last 60 minutes.
. SERVIDOR2 passed test systemlog
Starting test: VerifyReplicas
. SERVIDOR2 passed test VerifyReplicas
Starting test: VerifyReferences
The system object reference (serverReference)

CN=SERVIDOR2,OU=Domain Controllers,DC=MAIN,DC=local and backlink on


CN=SERVIDOR2,CN=Servers,CN=Nombre-predeterminado-primer-sitio,CN=Sites,CN=Configuration,DC=MAIN,DC=local

are correct.
The system object reference (frsComputerReferenceBL)

CN=SERVIDOR2,CN=Domain System Volume (SYSVOL share),CN=File
Replication Service,CN=System,DC=MAIN,DC=local

and backlink on CN=SERVIDOR2,OU=Domain Controllers,DC=MAIN,DC=local

are correct.
The system object reference (serverReferenceBL)

CN=SERVIDOR2,CN=Domain System Volume (SYSVOL share),CN=File
Replication Service,CN=System,DC=MAIN,DC=local

and backlink on

CN=NTDS
Settings,CN=SERVIDOR2,CN=Servers,CN=Nombre-predeterminado-primer-sitio,CN=Sites,CN=Configuration,DC=MAIN,DC=local

are correct.
. SERVIDOR2 passed test VerifyReferences
Starting test: VerifyEnterpriseReferences
. SERVIDOR2 passed test
VerifyEnterpriseReferences

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 : MAIN
Starting test: CrossRefValidation
. MAIN passed test CrossRefValidation
Starting test: CheckSDRefDom
. MAIN passed test CheckSDRefDom

Running enterprise tests on : MAIN.local
Starting test: Intersite
Skipping site Nombre-predeterminado-primer-sitio, this site is
outside

the scope provided by the command line arguments provided.
. MAIN.local passed test Intersite
Starting test: FsmoCheck
GC Name: \\servidor.MAIN.local
Locator Flags: 0xe00001fd
PDC Name: \\servidor.MAIN.local
Locator Flags: 0xe00001fd
Time Server Name: \\servidor.MAIN.local
Locator Flags: 0xe00001fd
Preferred Time Server Name: \\servidor.MAIN.local
Locator Flags: 0xe00001fd
KDC Name: \\servidor.MAIN.local
Locator Flags: 0xe00001fd
. MAIN.local passed test FsmoCheck
El resultado del NetDiag es este:



Computer Name: SERVIDOR2
DNS Host Name: servidor2.MAIN.local
System info : Windows 2000 Server (Build 3790)
Processor : x86 Family 15 Model 4 Stepping 3, GenuineIntel
List of installed hotfixes :
KB890046
KB893756
KB896358
KB896422
KB896424
KB896428
KB897616
KB898715
KB898900
KB899587
KB899588
KB899589
KB899591
KB900725
KB901017
KB901214
KB902400
KB903651
KB904706
KB905414
KB908519
KB908521
KB908531
KB910437
KB911280
KB911562
KB911567
KB911927
KB912919
KB914389
KB916281
KB917344
KB917734
KB917953
KB918439
Q147222


Netcard queries test . . . . . . . : Passed
GetStats failed for 'Paralelo directo'. [ERROR_NOT_SUPPORTED]
GetStats failed for 'Minipuerto WAN (PPTP)'. [ERROR_NOT_SUPPORTED]
GetStats failed for 'Minipuerto WAN (PPPOE)'. [ERROR_NOT_SUPPORTED]
[WARNING] The net card 'Minipuerto WAN (IP)' may not be working because
it has not received any packets.
GetStats failed for 'Minipuerto WAN (L2TP)'. [ERROR_NOT_SUPPORTED]



Per interface results:

Adapter : Conexión de área local

Netcard queries test . . . : Passed

Host Name. . . . . . . . . : servidor2.main.local
IP Address . . . . . . . . : 192.168.10.50
Subnet Mask. . . . . . . . : 255.255.255.0
Default Gateway. . . . . . : 192.168.10.20
Dns Servers. . . . . . . . : 192.168.10.50
10.0.0.50
213.172.33.34


AutoConfiguration results. . . . . . : Passed

Default gateway test . . . : Passed

NetBT name test. . . . . . : Passed
[WARNING] At least one of the <00> 'WorkStation Service', <03>
'Messenger Service', <20> 'WINS' names is missing.

WINS service test. . . . . : Skipped
There are no WINS servers configured for this interface.


Global results:


Domain membership test . . . . . . : Failed
[WARNING] Ths system volume has not been completely replicated to the
local machine. This machine is not working properly as a DC.


NetBT transports test. . . . . . . : Passed
List of NetBt transports currently configured:
NetBT_Tcpip_{603DA264-890F-4288-BF3B-672F9FA662C1}
1 NetBt transport currently configured.


Autonet address test . . . . . . . : Passed


IP loopback ping test. . . . . . . : Passed


Default gateway test . . . . . . . : Passed


NetBT name test. . . . . . . . . . : Passed
[WARNING] You don't have a single interface with the <00> 'WorkStation
Service', <03> 'Messenger Service', <20> 'WINS' names defined.


Winsock test . . . . . . . . . . . : Passed


DNS test . . . . . . . . . . . . . : Passed
PASS - All the DNS entries for DC are registered on DNS server
'192.168.10.50' and other DCs also have some of the names registered.
PASS - All the DNS entries for DC are registered on DNS server
'10.0.0.50' and other DCs also have some of the names registered.
[WARNING] The DNS entries for this DC are not registered correctly on
DNS server '213.172.33.34'. Please wait for 30 minutes for DNS server
replication.


Redir and Browser test . . . . . . : Passed
List of NetBt transports currently bound to the Redir
NetBT_Tcpip_{603DA264-890F-4288-BF3B-672F9FA662C1}
The redir is bound to 1 NetBt transport.

List of NetBt transports currently bound to the browser
NetBT_Tcpip_{603DA264-890F-4288-BF3B-672F9FA662C1}
The browser is bound to 1 NetBt transport.


DC discovery test. . . . . . . . . : Passed


DC list test . . . . . . . . . . . : Passed


Trust relationship test. . . . . . : Passed
Secure channel for domain 'MAIN' is to '\\servidor.MAIN.local'.


Kerberos test. . . . . . . . . . . : Passed


LDAP test. . . . . . . . . . . . . : Passed
[WARNING] The default SPN registration for 'HOST/servidor2.MAIN.local'
is missing on DC 'SERVIDOR1.MAIN.local'.
[WARNING] The default SPN registration for 'HOST/SERVIDOR2' is missing
on DC 'SERVIDOR1.MAIN.local'.


Bindings test. . . . . . . . . . . : Passed


WAN configuration test . . . . . . : Skipped
No active remote access connections.


Modem diagnostics test . . . . . . : Passed

IP Security test . . . . . . . . . : Skipped

Note: run "netsh ipsec dynamic show /?" for more detailed information


The command completed successfully

***** Espero que puedas entender algo y gracias ******


"Marc [MVP Windows]" escribió:

Pasa un DCdiag y un Netdiag a esos servidores y por por aquí los resultados.

Respecto al ID del error: http://www.eventid.net/display.asp?eventid508&eventnoe85&source=FRS&phase=1


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:
> Buenos Dias, Tengo un DC Windows 2000 SP4, que es el root domain, y 2 Windows
> 2003 Std SP1 R2, que ambos se elevaron a controladores de dominio.
> Pero el servicio de replicacion no logra pasar la info desde el 2000 a los
> otros servidores,el error es el Id. 13508, "Tiene problemas habilitando la
> replicacion desde W2kServer a W2k3server"
> Alguna sugerencia?

Respuesta Responder a este mensaje
#3 Marc [MVP Windows]
04/07/2006 - 20:18 | Informe spam
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.
. SERVIDOR2 passed test kccevent
Starting test: systemlog
* The System Event log test
Found no errors in System Event log in the last 60 minutes.
. SERVIDOR2 passed test systemlog
Starting test: VerifyReplicas
. SERVIDOR2 passed test VerifyReplicas
Starting test: VerifyReferences
The system object reference (serverReference)

CN=SERVIDOR2,OU=Domain Controllers,DC=MAIN,DC=local and backlink on


CN=SERVIDOR2,CN=Servers,CN=Nombre-predeterminado-primer-sitio,CN=Sites,CN=Configuration,DC=MAIN,DC=local

are correct.
The system object reference (frsComputerReferenceBL)

CN=SERVIDOR2,CN=Domain System Volume (SYSVOL share),CN=File
Replication Service,CN=System,DC=MAIN,DC=local

and backlink on CN=SERVIDOR2,OU=Domain Controllers,DC=MAIN,DC=local

are correct.
The system object reference (serverReferenceBL)

CN=SERVIDOR2,CN=Domain System Volume (SYSVOL share),CN=File
Replication Service,CN=System,DC=MAIN,DC=local

and backlink on

CN=NTDS
Settings,CN=SERVIDOR2,CN=Servers,CN=Nombre-predeterminado-primer-sitio,CN=Sites,CN=Configuration,DC=MAIN,DC=local

are correct.
. SERVIDOR2 passed test VerifyReferences
Starting test: VerifyEnterpriseReferences
. SERVIDOR2 passed test
VerifyEnterpriseReferences

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 : MAIN
Starting test: CrossRefValidation
. MAIN passed test CrossRefValidation
Starting test: CheckSDRefDom
. MAIN passed test CheckSDRefDom

Running enterprise tests on : MAIN.local
Starting test: Intersite
Skipping site Nombre-predeterminado-primer-sitio, this site is
outside

the scope provided by the command line arguments provided.
. MAIN.local passed test Intersite
Starting test: FsmoCheck
GC Name: \\servidor.MAIN.local
Locator Flags: 0xe00001fd
PDC Name: \\servidor.MAIN.local
Locator Flags: 0xe00001fd
Time Server Name: \\servidor.MAIN.local
Locator Flags: 0xe00001fd
Preferred Time Server Name: \\servidor.MAIN.local
Locator Flags: 0xe00001fd
KDC Name: \\servidor.MAIN.local
Locator Flags: 0xe00001fd
. MAIN.local passed test FsmoCheck
El resultado del NetDiag es este:



Computer Name: SERVIDOR2
DNS Host Name: servidor2.MAIN.local
System info : Windows 2000 Server (Build 3790)
Processor : x86 Family 15 Model 4 Stepping 3, GenuineIntel
List of installed hotfixes :
KB890046
KB893756
KB896358
KB896422
KB896424
KB896428
KB897616
KB898715
KB898900
KB899587
KB899588
KB899589
KB899591
KB900725
KB901017
KB901214
KB902400
KB903651
KB904706
KB905414
KB908519
KB908521
KB908531
KB910437
KB911280
KB911562
KB911567
KB911927
KB912919
KB914389
KB916281
KB917344
KB917734
KB917953
KB918439
Q147222


Netcard queries test . . . . . . . : Passed
GetStats failed for 'Paralelo directo'. [ERROR_NOT_SUPPORTED]
GetStats failed for 'Minipuerto WAN (PPTP)'. [ERROR_NOT_SUPPORTED]
GetStats failed for 'Minipuerto WAN (PPPOE)'. [ERROR_NOT_SUPPORTED]
[WARNING] The net card 'Minipuerto WAN (IP)' may not be working because
it has not received any packets.
GetStats failed for 'Minipuerto WAN (L2TP)'. [ERROR_NOT_SUPPORTED]



Per interface results:

Adapter : Conexión de área local

Netcard queries test . . . : Passed

Host Name. . . . . . . . . : servidor2.main.local
IP Address . . . . . . . . : 192.168.10.50
Subnet Mask. . . . . . . . : 255.255.255.0
Default Gateway. . . . . . : 192.168.10.20
Dns Servers. . . . . . . . : 192.168.10.50
10.0.0.50
213.172.33.34


AutoConfiguration results. . . . . . : Passed

Default gateway test . . . : Passed

NetBT name test. . . . . . : Passed
[WARNING] At least one of the <00> 'WorkStation Service', <03>
'Messenger Service', <20> 'WINS' names is missing.

WINS service test. . . . . : Skipped
There are no WINS servers configured for this interface.


Global results:


Domain membership test . . . . . . : Failed
[WARNING] Ths system volume has not been completely replicated to the
local machine. This machine is not working properly as a DC.


NetBT transports test. . . . . . . : Passed
List of NetBt transports currently configured:
NetBT_Tcpip_{603DA264-890F-4288-BF3B-672F9FA662C1}
1 NetBt transport currently configured.


Autonet address test . . . . . . . : Passed


IP loopback ping test. . . . . . . : Passed


Default gateway test . . . . . . . : Passed


NetBT name test. . . . . . . . . . : Passed
[WARNING] You don't have a single interface with the <00> 'WorkStation
Service', <03> 'Messenger Service', <20> 'WINS' names defined.


Winsock test . . . . . . . . . . . : Passed


DNS test . . . . . . . . . . . . . : Passed
PASS - All the DNS entries for DC are registered on DNS server
'192.168.10.50' and other DCs also have some of the names registered.
PASS - All the DNS entries for DC are registered on DNS server
'10.0.0.50' and other DCs also have some of the names registered.
[WARNING] The DNS entries for this DC are not registered correctly on
DNS server '213.172.33.34'. Please wait for 30 minutes for DNS server
replication.


Redir and Browser test . . . . . . : Passed
List of NetBt transports currently bound to the Redir
NetBT_Tcpip_{603DA264-890F-4288-BF3B-672F9FA662C1}
The redir is bound to 1 NetBt transport.

List of NetBt transports currently bound to the browser
NetBT_Tcpip_{603DA264-890F-4288-BF3B-672F9FA662C1}
The browser is bound to 1 NetBt transport.


DC discovery test. . . . . . . . . : Passed


DC list test . . . . . . . . . . . : Passed


Trust relationship test. . . . . . : Passed
Secure channel for domain 'MAIN' is to '\\servidor.MAIN.local'.


Kerberos test. . . . . . . . . . . : Passed


LDAP test. . . . . . . . . . . . . : Passed
[WARNING] The default SPN registration for 'HOST/servidor2.MAIN.local'
is missing on DC 'SERVIDOR1.MAIN.local'.
[WARNING] The default SPN registration for 'HOST/SERVIDOR2' is missing
on DC 'SERVIDOR1.MAIN.local'.


Bindings test. . . . . . . . . . . : Passed


WAN configuration test . . . . . . : Skipped
No active remote access connections.


Modem diagnostics test . . . . . . : Passed

IP Security test . . . . . . . . . : Skipped

Note: run "netsh ipsec dynamic show /?" for more detailed information


The command completed successfully

***** Espero que puedas entender algo y gracias ******


"Marc [MVP Windows]" escribió:

Pasa un DCdiag y un Netdiag a esos servidores y por por aquí los resultados.

Respecto al ID del error: http://www.eventid.net/display.asp?eventid508&eventnoe85&source=FRS&phase=1


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:
> Buenos Dias, Tengo un DC Windows 2000 SP4, que es el root domain, y 2 Windows
> 2003 Std SP1 R2, que ambos se elevaron a controladores de dominio.
> Pero el servicio de replicacion no logra pasar la info desde el 2000 a los
> otros servidores,el error es el Id. 13508, "Tiene problemas habilitando la
> replicacion desde W2kServer a W2k3server"
> Alguna sugerencia?

Respuesta Responder a este mensaje
#4 Claudio
05/07/2006 - 17:31 | Informe spam
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.
> . SERVIDOR2 passed test kccevent
> Starting test: systemlog
> * The System Event log test
> Found no errors in System Event log in the last 60 minutes.
> . SERVIDOR2 passed test systemlog
> Starting test: VerifyReplicas
> . SERVIDOR2 passed test VerifyReplicas
> Starting test: VerifyReferences
> The system object reference (serverReference)
>
> CN=SERVIDOR2,OU=Domain Controllers,DC=MAIN,DC=local and backlink on
>
>
> CN=SERVIDOR2,CN=Servers,CN=Nombre-predeterminado-primer-sitio,CN=Sites,CN=Configuration,DC=MAIN,DC=local
>
> are correct.
> The system object reference (frsComputerReferenceBL)
>
> CN=SERVIDOR2,CN=Domain System Volume (SYSVOL share),CN=File
> Replication Service,CN=System,DC=MAIN,DC=local
>
> and backlink on CN=SERVIDOR2,OU=Domain Controllers,DC=MAIN,DC=local
>
> are correct.
> The system object reference (serverReferenceBL)
>
Respuesta Responder a este mensaje
#5 Marc [MVP Windows]
06/07/2006 - 12:39 | Informe spam
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.
> . SERVIDOR2 passed test kccevent
> Starting test: systemlog
> * The System Event log test
> Found no errors in System Event log in the last 60 minutes.
> . SERVIDOR2 passed test systemlog
> Starting test: VerifyReplicas
> . SERVIDOR2 passed test VerifyReplicas
> Starting test: VerifyReferences
> The system object reference (serverReference)
>
> CN=SERVIDOR2,OU=Domain Controllers,DC=MAIN,DC=local and backlink on
>
>
> CN=SERVIDOR2,CN=Servers,CN=Nombre-predeterminado-primer-sitio,CN=Sites,CN=Configuration,DC=MAIN,DC=local
>
> are correct.
> The system object reference (frsComputerReferenceBL)
>
> CN=SERVIDOR2,CN=Domain System Volume (SYSVOL share),CN=File
> Replication Service,CN=System,DC=MAIN,DC=local
>
> and backlink on CN=SERVIDOR2,OU=Domain Controllers,DC=MAIN,DC=local
>
> are correct.
> The system object reference (serverReferenceBL)
>
Respuesta Responder a este mensaje
Ads by Google
Help Hacer una preguntaSiguiente Respuesta Tengo una respuesta
Search Busqueda sugerida