Principales respuestas
Problemas de Replicacion - Servidor caido varios meses.
Pregunta
-
Ante todo muchas gracias por la ayuda que me puedan brindar.
Tengo un servidor que estuvo caido varios meses, le cambiamos de placa, ahora levanta normal, pero no quiere replicar y actualizar la informacion de AD, desde el DC principal que se encuentra en otro site.
Informo que he buscado informacion al respecto antes de hacer esta pregunta y sigo haciendolo.
Abajo pongo los evento que aparecen y el resultado del dcdiag.
Evento:1865 (advertencia)
El Comprobador de coherencia de réplica (KCC) no ha podido formar una topología de red de árbol de expansión completa. Como resultado, no se puede alcanzar la siguiente lista de sitios desde el sitio local.
Evento:1566 (advertencia)
Los controladores de dominio del siguiente sitio que pueden replicar la partición de directorio por medio de este transporte no están disponibles actualmente.
Evento:1311 (error)
El Comprobador de coherencia de réplica (KCC) ha detectado problemas con la siguiente partición del directorio.
No hay suficiente información de conectividad de sitio en Sitios y servicios de Active Directory para que el KCC cree una topología de replicación de árbol de expansión. O bien, uno o más controladores de dominio con esta partición del directorio no pueden replicar la información de partición del directorio. Esto probablemente se deba a controladores de dominio inaccesibles.Resultado dcdiag
Domain Controller Diagnosis
Performing initial setup:
Done gathering initial info.
Doing initial required tests
Testing server: SiteHome\MASTERHOME
Starting test: Connectivity
......................... MASTERHOME passed test Connectivity
Doing primary tests
Testing server: SiteHome\MASTERHOME
Starting test: Replications
[Replications Check,MASTERHOME] A recent replication attempt failed:
From MASTER to MASTERHOME
Naming Context: DC=ForestDnsZones,DC=iluminacion,DC=com
The replication generated an error (1256):
Win32 Error 1256
The failure occurred at 2012-06-20 11:39:52.
The last success occurred at 2012-03-14 21:47:04.
265 failures have occurred since the last success.
[Replications Check,MASTERHOME] A recent replication attempt failed:
From MASTERSQO to MASTERHOME
Naming Context: DC=ForestDnsZones,DC=iluminacion,DC=com
The replication generated an error (1256):
Win32 Error 1256
The failure occurred at 2012-06-20 11:39:52.
The last success occurred at 2012-03-14 21:47:04.
265 failures have occurred since the last success.
[Replications Check,MASTERHOME] A recent replication attempt failed:
From MASTER to MASTERHOME
Naming Context: DC=DomainDnsZones,DC=iluminacion,DC=com
The replication generated an error (1256):
Win32 Error 1256
The failure occurred at 2012-06-20 11:39:52.
The last success occurred at 2012-03-14 21:47:04.
265 failures have occurred since the last success.
[Replications Check,MASTERHOME] A recent replication attempt failed:
From MASTERSQO to MASTERHOME
Naming Context: DC=DomainDnsZones,DC=iluminacion,DC=com
The replication generated an error (1256):
Win32 Error 1256
The failure occurred at 2012-06-20 11:39:53.
The last success occurred at 2012-03-14 21:47:04.
265 failures have occurred since the last success.
[Replications Check,MASTERHOME] A recent replication attempt failed:
From MASTER to MASTERHOME
Naming Context: CN=Schema,CN=Configuration,DC=iluminacion,DC=com
The replication generated an error (-2146893022):
Win32 Error -2146893022
The failure occurred at 2012-06-20 11:39:53.
The last success occurred at 2012-03-14 21:47:04.
263 failures have occurred since the last success.
[Replications Check,MASTERHOME] A recent replication attempt failed:
From MASTERSQO to MASTERHOME
Naming Context: CN=Schema,CN=Configuration,DC=iluminacion,DC=com
The replication generated an error (-2146893022):
Win32 Error -2146893022
The failure occurred at 2012-06-20 11:39:53.
The last success occurred at 2012-03-14 21:47:04.
263 failures have occurred since the last success.
[Replications Check,MASTERHOME] A recent replication attempt failed:
From MASTER to MASTERHOME
Naming Context: CN=Configuration,DC=iluminacion,DC=com
The replication generated an error (-2146893022):
Win32 Error -2146893022
The failure occurred at 2012-06-20 11:39:52.
The last success occurred at 2012-03-14 21:47:04.
264 failures have occurred since the last success.
[Replications Check,MASTERHOME] A recent replication attempt failed:
From MASTERSQO to MASTERHOME
Naming Context: CN=Configuration,DC=iluminacion,DC=com
The replication generated an error (-2146893022):
Win32 Error -2146893022
The failure occurred at 2012-06-20 11:39:52.
The last success occurred at 2012-03-14 21:47:04.
265 failures have occurred since the last success.
[Replications Check,MASTERHOME] A recent replication attempt failed:
From MASTER to MASTERHOME
Naming Context: DC=iluminacion,DC=com
The replication generated an error (-2146893022):
Win32 Error -2146893022
The failure occurred at 2012-06-20 11:39:52.
The last success occurred at 2012-03-14 21:47:04.
263 failures have occurred since the last success.
[Replications Check,MASTERHOME] A recent replication attempt failed:
From MASTERSQO to MASTERHOME
Naming Context: DC=iluminacion,DC=com
The replication generated an error (-2146893022):
Win32 Error -2146893022
The failure occurred at 2012-06-20 11:39:53.
The last success occurred at 2012-03-14 21:47:04.
263 failures have occurred since the last success.
REPLICATION-RECEIVED LATENCY WARNING
MASTERHOME: Current time is 2012-06-20 11:54:25.
DC=ForestDnsZones,DC=iluminacion,DC=com
Last replication recieved from MASTERSQO at 2012-03-14 21:47:04.
Last replication recieved from MASTER at 2012-03-14 21:47:04.
DC=DomainDnsZones,DC=iluminacion,DC=com
Last replication recieved from MASTERSQO at 2012-03-14 21:47:04.
Last replication recieved from MASTER at 2012-03-14 21:47:04.
CN=Schema,CN=Configuration,DC=iluminacion,DC=com
Last replication recieved from MASTERSQO at 2012-03-14 21:47:04.
Last replication recieved from MASTER at 2012-03-14 21:47:04.
CN=Configuration,DC=iluminacion,DC=com
Last replication recieved from MASTERSQO at 2012-03-14 21:47:04.
Last replication recieved from MASTER at 2012-03-14 21:47:04.
DC=iluminacion,DC=com
Last replication recieved from MASTERSQO at 2012-03-14 21:47:04.
Last replication recieved from MASTER at 2012-03-14 21:47:04.
REPLICATION-RECEIVED LATENCY WARNING
Source site:
CN=NTDS Site Settings,CN=SiteLibertadores,CN=Sites,CN=Configuration,DC=iluminacion,DC=com
Current time: 2012-06-20 11:54:25
Last update time: 2012-03-14 21:43:53
Check if source site has an elected ISTG running.
Check replication from source site to this server.
REPLICATION-RECEIVED LATENCY WARNING
Source site:
CN=NTDS Site Settings,CN=SiteSQO,CN=Sites,CN=Configuration,DC=iluminacion,DC=com
Current time: 2012-06-20 11:54:25
Last update time: 2012-03-14 21:36:39
Check if source site has an elected ISTG running.
Check replication from source site to this server.
......................... MASTERHOME passed test Replications
Starting test: NCSecDesc
......................... MASTERHOME passed test NCSecDesc
Starting test: NetLogons
......................... MASTERHOME passed test NetLogons
Starting test: Advertising
......................... MASTERHOME passed test Advertising
Starting test: KnowsOfRoleHolders
[MASTER] DsBindWithSpnEx() failed with error -2146893022,
Win32 Error -2146893022.
Warning: MASTER is the Schema Owner, but is not responding to DS RPC Bind.
[MASTER] LDAP bind failed with error 8341,
Win32 Error 8341.
Warning: MASTER is the Schema Owner, but is not responding to LDAP Bind.
Warning: MASTER is the Domain Owner, but is not responding to DS RPC Bind.
Warning: MASTER is the Domain Owner, but is not responding to LDAP Bind.
Warning: MASTER is the PDC Owner, but is not responding to DS RPC Bind.
Warning: MASTER is the PDC Owner, but is not responding to LDAP Bind.
Warning: MASTER is the Rid Owner, but is not responding to DS RPC Bind.
Warning: MASTER is the Rid Owner, but is not responding to LDAP Bind.
Warning: MASTER is the Infrastructure Update Owner, but is not responding to DS RPC Bind.
Warning: MASTER is the Infrastructure Update Owner, but is not responding to LDAP Bind.
......................... MASTERHOME failed test KnowsOfRoleHolders
Starting test: RidManager
......................... MASTERHOME failed test RidManager
Starting test: MachineAccount
......................... MASTERHOME passed test MachineAccount
Starting test: Services
......................... MASTERHOME passed test Services
Starting test: ObjectsReplicated
......................... MASTERHOME passed test ObjectsReplicated
Starting test: frssysvol
......................... MASTERHOME passed test frssysvol
Starting test: frsevent
There are warning or error events within the last 24 hours after the
SYSVOL has been shared. Failing SYSVOL replication problems may cause
Group Policy problems.
......................... MASTERHOME failed test frsevent
Starting test: kccevent
An Warning Event occured. EventID: 0x8025082D
Time Generated: 06/20/2012 11:39:52
(Event String could not be retrieved)
An Warning Event occured. EventID: 0x8025082D
Time Generated: 06/20/2012 11:39:52
(Event String could not be retrieved)
An Warning Event occured. EventID: 0x8025082D
Time Generated: 06/20/2012 11:39:52
(Event String could not be retrieved)
An Error Event occured. EventID: 0xC0000748
Time Generated: 06/20/2012 11:39:52
(Event String could not be retrieved)
An Warning Event occured. EventID: 0x8025082D
Time Generated: 06/20/2012 11:39:52
(Event String could not be retrieved)
An Error Event occured. EventID: 0xC0000748
Time Generated: 06/20/2012 11:39:52
(Event String could not be retrieved)
An Warning Event occured. EventID: 0x8025082D
Time Generated: 06/20/2012 11:39:52
(Event String could not be retrieved)
An Error Event occured. EventID: 0xC0000748
Time Generated: 06/20/2012 11:39:52
(Event String could not be retrieved)
An Error Event occured. EventID: 0xC0000748
Time Generated: 06/20/2012 11:39:52
(Event String could not be retrieved)
An Error Event occured. EventID: 0xC0000748
Time Generated: 06/20/2012 11:39:52
(Event String could not be retrieved)
An Warning Event occured. EventID: 0x8000061E
Time Generated: 06/20/2012 11:45:02
(Event String could not be retrieved)
An Warning Event occured. EventID: 0x8000061E
Time Generated: 06/20/2012 11:45:02
(Event String could not be retrieved)
An Error Event occured. EventID: 0xC000051F
Time Generated: 06/20/2012 11:45:02
(Event String could not be retrieved)
An Warning Event occured. EventID: 0x80000749
Time Generated: 06/20/2012 11:45:02
(Event String could not be retrieved)
An Warning Event occured. EventID: 0x8000061E
Time Generated: 06/20/2012 11:45:02
(Event String could not be retrieved)
An Warning Event occured. EventID: 0x8000061E
Time Generated: 06/20/2012 11:45:02
(Event String could not be retrieved)
An Error Event occured. EventID: 0xC000051F
Time Generated: 06/20/2012 11:45:02
(Event String could not be retrieved)
An Warning Event occured. EventID: 0x80000749
Time Generated: 06/20/2012 11:45:02
(Event String could not be retrieved)
An Warning Event occured. EventID: 0x8000061E
Time Generated: 06/20/2012 11:45:02
(Event String could not be retrieved)
An Warning Event occured. EventID: 0x8000061E
Time Generated: 06/20/2012 11:45:02
(Event String could not be retrieved)
An Error Event occured. EventID: 0xC000051F
Time Generated: 06/20/2012 11:45:02
(Event String could not be retrieved)
An Warning Event occured. EventID: 0x80000749
Time Generated: 06/20/2012 11:45:02
(Event String could not be retrieved)
An Warning Event occured. EventID: 0x8000061E
Time Generated: 06/20/2012 11:45:02
(Event String could not be retrieved)
An Warning Event occured. EventID: 0x8000061E
Time Generated: 06/20/2012 11:45:02
(Event String could not be retrieved)
An Error Event occured. EventID: 0xC000051F
Time Generated: 06/20/2012 11:45:02
(Event String could not be retrieved)
An Warning Event occured. EventID: 0x80000749
Time Generated: 06/20/2012 11:45:02
(Event String could not be retrieved)
......................... MASTERHOME failed test kccevent
Starting test: systemlog
An Error Event occured. EventID: 0x40000004
Time Generated: 06/20/2012 10:54:53
(Event String could not be retrieved)
An Error Event occured. EventID: 0x40000004
Time Generated: 06/20/2012 11:00:17
(Event String could not be retrieved)
An Error Event occured. EventID: 0x40000004
Time Generated: 06/20/2012 11:00:17
(Event String could not be retrieved)
An Error Event occured. EventID: 0x40000004
Time Generated: 06/20/2012 11:05:08
(Event String could not be retrieved)
An Error Event occured. EventID: 0x40000004
Time Generated: 06/20/2012 11:05:09
(Event String could not be retrieved)
An Error Event occured. EventID: 0x40000004
Time Generated: 06/20/2012 11:28:28
(Event String could not be retrieved)
An Error Event occured. EventID: 0x40000004
Time Generated: 06/20/2012 11:28:32
(Event String could not be retrieved)
An Error Event occured. EventID: 0x40000004
Time Generated: 06/20/2012 11:36:01
(Event String could not be retrieved)
An Error Event occured. EventID: 0x40000004
Time Generated: 06/20/2012 11:36:02
(Event String could not be retrieved)
An Error Event occured. EventID: 0x40000004
Time Generated: 06/20/2012 11:41:25
(Event String could not be retrieved)
An Error Event occured. EventID: 0x40000004
Time Generated: 06/20/2012 11:41:26
(Event String could not be retrieved)
An Error Event occured. EventID: 0x40000004
Time Generated: 06/20/2012 11:41:31
(Event String could not be retrieved)
An Error Event occured. EventID: 0x40000004
Time Generated: 06/20/2012 11:53:32
(Event String could not be retrieved)
......................... MASTERHOME failed test systemlog
Starting test: VerifyReferences
......................... MASTERHOME passed test VerifyReferences
Running partition tests on : ForestDnsZones
Starting test: CrossRefValidation
......................... ForestDnsZones passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... ForestDnsZones passed test CheckSDRefDom
Running partition tests on : DomainDnsZones
Starting test: CrossRefValidation
......................... DomainDnsZones passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... DomainDnsZones passed test CheckSDRefDom
Running partition tests on : Schema
Starting test: CrossRefValidation
......................... Schema passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... Schema passed test CheckSDRefDom
Running partition tests on : Configuration
Starting test: CrossRefValidation
......................... Configuration passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... Configuration passed test CheckSDRefDom
Running partition tests on : iluminacion
Starting test: CrossRefValidation
......................... iluminacion passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... iluminacion passed test CheckSDRefDom
Running enterprise tests on : iluminacion.com
Starting test: Intersite
......................... iluminacion.com passed test Intersite
Starting test: FsmoCheck
......................... iluminacion.com passed test FsmoCheck
Respuestas
-
Ricardo, siendo que estuvo interrumpida la comunicación durante "varios meses" lo primero a revisar es si tienes algún evento con el ID 2042 por que esto creo que sería lo normal, pasado tanto tiempo
Si estás completamente seguro que no hay ningún evento 2042, entonces lo primero que hay que revisar es resolución de nombres y conectividad IP
Guillermo Delprato - Buenos Aires, Argentina
Visite Notas Windows Server
MVP - MCT - MCSE - MCSA
MCITP: Enterprise Administrator / Server Administrator
MCTS: Active Directory/Network Configuration/Applications Configuration/Server Virtualization/Windows 7 Configuration/Windows 7 & Office 2010 Deployment/Vista Configuration
Este mensaje se proporciona "como está" sin garantías de ninguna clase. Usted asume todos los riesgos.- Marcado como respuesta Eduardo PorteschellerModerator lunes, 25 de junio de 2012 14:10
-
Segun tu DCDIAG , asumo que tienes dos DCs, Master y MASTERHOME, en cuanto a los errores de comunicacion el error 1256 quiere decir "The remote system is not available" por lo cual no esta habiendo una comunicacion correcta entre estos sistemas, la cual podria estar dada por un problema a nivel de DNS por ejemplo, o bien conectividad.
Ambos DCs tienen sus registros SRV bien creados ? Estamos hablando de una misma LAN , o hay algun firewall de por medio ? Que sucede si apuntas la direccion de DNS primaria del servidor MASTERHOME hacia la direccion IP de MASTER ?
Si continuamos viendo el dcdiag, podemos ver que desde masterhome, se da el error 8341 ()
[MASTER] DsBindWithSpnEx() failed with error -2146893022,
Win32 Error -2146893022.
Warning: MASTER is the Schema Owner, but is not responding to DS RPC Bind.
[MASTER] LDAP bind failed with error 8341,
Win32 Error 8341.
Warning: MASTER is the Schema Owner, but is not responding to LDAP Bind.
Warning: MASTER is the Domain Owner, but is not responding to DS RPC Bind.
Warning: MASTER is the Domain Owner, but is not responding to LDAP Bind.
Warning: MASTER is the PDC Owner, but is not responding to DS RPC Bind.
Warning: MASTER is the PDC Owner, but is not responding to LDAP Bind.
Warning: MASTER is the Rid Owner, but is not responding to DS RPC Bind.
Warning: MASTER is the Rid Owner, but is not responding to LDAP Bind.
Warning: MASTER is the Infrastructure Update Owner, but is not responding to DS RPC Bind.
Warning: MASTER is the Infrastructure Update Owner, but is not responding to LDAP BindQue sucede si tratas de hacer una conexion ldap ?
Desde masterhome
1 . Abre la herramienta ldp.exe
2 . Pon el nombre del servidor MASTER en Server
3 . Luego dale BIND y dale aceptar para utilizar las credenciales del usuario logueadoTe deja conectar correctamente ? con esta prueba estarias chequeando si el LDAP bind funciona correctamente :)
Adicionalmente FRS parece tener errores reportados
Group Policy problems.
......................... MASTERHOME failed test frsevent. Aqui deberias verificar que tipo de eventos tienes en el eventviewer de File Replication Service, y trabajar esos errores por separado.
Para poder hacer un troubleshooting correcto de este incoveniente deberias separar los problemas e ir trabajando uno a la vez (quizas esten relacionados) aunque aun no lo sabemos.
Adicionalmente, si miras el DCdiag de MASTER, el reporta errores o esta limpio ?
Sebastian del Rio - MCP - MCSA +S - MCSE +S - MCITP:Enterprise Administrator Buenos Aires - Argentina Este mensaje se proporciona "como está" sin garantías de ninguna clase, y no otorga ningún derecho. Ud. asume los riesgos
- Marcado como respuesta Eduardo PorteschellerModerator lunes, 25 de junio de 2012 14:10
-
Hola,
Perdon que me meta, vienen respondiendote dos importantes personas en el foro, pero me tomo el atrevimiento de agregarme en este tema y ver que podemos ayudar..
Chequea por favor, que valor tienes de tombstone lifetime en tu Forest, siguiendo el siguiente acticulo: http://technet.microsoft.com/en-us/library/cc784932(WS.10).aspx
Luego de esto, ver si el equipo supero ese tiempo estando caido, desde ya te confirmo que no hay otra opcion que realizar un Metadata Cleanup, eliminando todas referencias de este Domain Controller afectado: http://support.microsoft.com/kb/216498 / http://technet.microsoft.com/en-us/library/cc731035(v=ws.10).aspx Si el mismo tenia roles de AD, moverlos al Domain Controller en funcionamiento: http://support.microsoft.com/kb/255504 y luego reinstalar el servidor afectado para promoverlo nuevamente a tu estructura actual.-
Si estas seguro que el downtime del server, no supero lo definido como tombstone lifetime, que eventos ves tanto en el Domain Controller afectado y el productivo?
Salu2
Leonardo Ponti
MVP: Directory Services
MCTS: Microsoft Certified Technology Specialist
MCSE: Microsoft Certified Systems Engineer (Windows Server 2003)
MCSA: Microsoft Certified Systems Administrator (Windows Server 2003)
Blog: Link!
Este mensaje se proporciona "como está" sin garantías de ninguna clase, y no otorga ningún derecho. Ud. asume los riesgos.
This posting is provided "AS IS" with no warranties, and confer no rights. You assume all risk for your use.- Marcado como respuesta Guillermo Delprato []Moderator martes, 17 de julio de 2012 16:50
Todas las respuestas
-
Ricardo, siendo que estuvo interrumpida la comunicación durante "varios meses" lo primero a revisar es si tienes algún evento con el ID 2042 por que esto creo que sería lo normal, pasado tanto tiempo
Si estás completamente seguro que no hay ningún evento 2042, entonces lo primero que hay que revisar es resolución de nombres y conectividad IP
Guillermo Delprato - Buenos Aires, Argentina
Visite Notas Windows Server
MVP - MCT - MCSE - MCSA
MCITP: Enterprise Administrator / Server Administrator
MCTS: Active Directory/Network Configuration/Applications Configuration/Server Virtualization/Windows 7 Configuration/Windows 7 & Office 2010 Deployment/Vista Configuration
Este mensaje se proporciona "como está" sin garantías de ninguna clase. Usted asume todos los riesgos.- Marcado como respuesta Eduardo PorteschellerModerator lunes, 25 de junio de 2012 14:10
-
Segun tu DCDIAG , asumo que tienes dos DCs, Master y MASTERHOME, en cuanto a los errores de comunicacion el error 1256 quiere decir "The remote system is not available" por lo cual no esta habiendo una comunicacion correcta entre estos sistemas, la cual podria estar dada por un problema a nivel de DNS por ejemplo, o bien conectividad.
Ambos DCs tienen sus registros SRV bien creados ? Estamos hablando de una misma LAN , o hay algun firewall de por medio ? Que sucede si apuntas la direccion de DNS primaria del servidor MASTERHOME hacia la direccion IP de MASTER ?
Si continuamos viendo el dcdiag, podemos ver que desde masterhome, se da el error 8341 ()
[MASTER] DsBindWithSpnEx() failed with error -2146893022,
Win32 Error -2146893022.
Warning: MASTER is the Schema Owner, but is not responding to DS RPC Bind.
[MASTER] LDAP bind failed with error 8341,
Win32 Error 8341.
Warning: MASTER is the Schema Owner, but is not responding to LDAP Bind.
Warning: MASTER is the Domain Owner, but is not responding to DS RPC Bind.
Warning: MASTER is the Domain Owner, but is not responding to LDAP Bind.
Warning: MASTER is the PDC Owner, but is not responding to DS RPC Bind.
Warning: MASTER is the PDC Owner, but is not responding to LDAP Bind.
Warning: MASTER is the Rid Owner, but is not responding to DS RPC Bind.
Warning: MASTER is the Rid Owner, but is not responding to LDAP Bind.
Warning: MASTER is the Infrastructure Update Owner, but is not responding to DS RPC Bind.
Warning: MASTER is the Infrastructure Update Owner, but is not responding to LDAP BindQue sucede si tratas de hacer una conexion ldap ?
Desde masterhome
1 . Abre la herramienta ldp.exe
2 . Pon el nombre del servidor MASTER en Server
3 . Luego dale BIND y dale aceptar para utilizar las credenciales del usuario logueadoTe deja conectar correctamente ? con esta prueba estarias chequeando si el LDAP bind funciona correctamente :)
Adicionalmente FRS parece tener errores reportados
Group Policy problems.
......................... MASTERHOME failed test frsevent. Aqui deberias verificar que tipo de eventos tienes en el eventviewer de File Replication Service, y trabajar esos errores por separado.
Para poder hacer un troubleshooting correcto de este incoveniente deberias separar los problemas e ir trabajando uno a la vez (quizas esten relacionados) aunque aun no lo sabemos.
Adicionalmente, si miras el DCdiag de MASTER, el reporta errores o esta limpio ?
Sebastian del Rio - MCP - MCSA +S - MCSE +S - MCITP:Enterprise Administrator Buenos Aires - Argentina Este mensaje se proporciona "como está" sin garantías de ninguna clase, y no otorga ningún derecho. Ud. asume los riesgos
- Marcado como respuesta Eduardo PorteschellerModerator lunes, 25 de junio de 2012 14:10
-
-
Buenos días,
Estimados, estuve revisando lo que me dijeron y no encontré ninguna anomalía.
Revise los registros SRV todo OK.
Hice ping entre equipos con Nombre e IP y todo OK.
No encontré ningún evento 2042.
La conexión ldap en ambos servidores responde lo mismo, pero al hacer el BIND, en Master si me deja autenticar contra MasterHome, pero en MasterHome no me permite hacerlo contra Master.
Por ultimo un dcdiag en Master esta limpio salvo por un problema con el frsevent.
Starting test: frsevent
There are warning or error events within the last 24 hours after the
SYSVOL has been shared. Failing SYSVOL replication problems may cause
Group Policy problems.
......................... MASTER failed test frseventLa verdad que estoy pensando en quitarlo a la fuerza y despues limpiar AD, pero preferiría no hacerlo.
Muchas gracias por su ayuda.
-
Hola,
Perdon que me meta, vienen respondiendote dos importantes personas en el foro, pero me tomo el atrevimiento de agregarme en este tema y ver que podemos ayudar..
Chequea por favor, que valor tienes de tombstone lifetime en tu Forest, siguiendo el siguiente acticulo: http://technet.microsoft.com/en-us/library/cc784932(WS.10).aspx
Luego de esto, ver si el equipo supero ese tiempo estando caido, desde ya te confirmo que no hay otra opcion que realizar un Metadata Cleanup, eliminando todas referencias de este Domain Controller afectado: http://support.microsoft.com/kb/216498 / http://technet.microsoft.com/en-us/library/cc731035(v=ws.10).aspx Si el mismo tenia roles de AD, moverlos al Domain Controller en funcionamiento: http://support.microsoft.com/kb/255504 y luego reinstalar el servidor afectado para promoverlo nuevamente a tu estructura actual.-
Si estas seguro que el downtime del server, no supero lo definido como tombstone lifetime, que eventos ves tanto en el Domain Controller afectado y el productivo?
Salu2
Leonardo Ponti
MVP: Directory Services
MCTS: Microsoft Certified Technology Specialist
MCSE: Microsoft Certified Systems Engineer (Windows Server 2003)
MCSA: Microsoft Certified Systems Administrator (Windows Server 2003)
Blog: Link!
Este mensaje se proporciona "como está" sin garantías de ninguna clase, y no otorga ningún derecho. Ud. asume los riesgos.
This posting is provided "AS IS" with no warranties, and confer no rights. You assume all risk for your use.- Marcado como respuesta Guillermo Delprato []Moderator martes, 17 de julio de 2012 16:50
-
Leonardo,
Verifique el valor de la variable y esta en 180 días, el servidor no tuvo caído tanto tiempo.
Igual he decidido hacerle un dcpromo /forceremoval y limpiar AD con el link que me pasaste.
Muchas gracias
- Marcado como respuesta RicardoMUZ lunes, 16 de julio de 2012 22:36
- Desmarcado como respuesta Guillermo Delprato []Moderator martes, 17 de julio de 2012 16:50
