DC dado de baja

27/03/2009 - 21:58 por Esteban | Informe spam
Estimados

En mi dominio tenia un DC 2000 y luego promovi otro WK2003.Ambos
estuvieron funcionando bien.En un momento quite el WK2000.Siguio todo
lo ms bien.
ahora quize instalar otro WK2003 y no me permitia, descubri que el
Wk2000 tenia los 5 roles.
Realice un Seize de los roles al WK2003 pero no me generar el
Forestprep y Domainprep.Dice que el dominio no esta replicado,En Sites
and Services active Directory sigue figurando ese 2000.
De acuerdo a la documentacion intente con NTDSutil, Metadata cleanup
pero tampoco lo he podido solucionar.Les adjunto el DCDIAG.de manera
que puedan ver si pueden ver como pueden ayudarme a solucionarlo.

De antemano muchs gracias.

Esteban

C:\Archivos de programa\Support Tools>dcdiag

Domain Controller Diagnosis

Performing initial setup:
Done gathering initial info.

Doing initial required tests

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

Doing primary tests

Testing server: Nombre-predeterminado-primer-sitio\SERVER2003
Starting test: Replications
[Replications Check,SERVER2003] A recent replication attempt
failed:
From BDC to SERVER2003
Naming Context:
CN=Schema,CN=Configuration,DC=rlya,DC=com,DC=ar
The replication generated an error (1722):
El servidor RPC no está disponible.
The failure occurred at 2009-03-27 17:00:11.
The last success occurred at 2007-05-14 10:58:30.
16242 failures have occurred since the last success.
[BDC] DsBindWithSpnEx() failed with error 1722,
El servidor RPC no está disponible..
The source remains down. Please check the machine.
[Replications Check,SERVER2003] A recent replication attempt
failed:
From BDC to SERVER2003
Naming Context: CN=Configuration,DC=rlya,DC=com,DC=ar
The replication generated an error (1722):
El servidor RPC no está disponible.
The failure occurred at 2009-03-27 16:59:50.
The last success occurred at 2007-05-14 11:22:29.
16242 failures have occurred since the last success.
The source remains down. Please check the machine.
[Replications Check,SERVER2003] A recent replication attempt
failed:
From BDC to SERVER2003
Naming Context: DC=rlya,DC=com,DC=ar
The replication generated an error (1722):
El servidor RPC no está disponible.
The failure occurred at 2009-03-27 16:59:29.
The last success occurred at 2007-05-14 11:24:00.
20310 failures have occurred since the last success.
The source remains down. Please check the machine.
REPLICATION-RECEIVED LATENCY WARNING
SERVER2003: Current time is 2009-03-27 17:35:20.
CN=Schema,CN=Configuration,DC=rlya,DC=com,DC=ar
Last replication recieved from BDC at 2007-05-14
10:58:30.
WARNING: This latency is over the Tombstone Lifetime
of 60 days!

CN=Configuration,DC=rlya,DC=com,DC=ar
Last replication recieved from BDC at 2007-05-14
11:22:29.
WARNING: This latency is over the Tombstone Lifetime
of 60 days!

DC=rlya,DC=com,DC=ar
Last replication recieved from BDC at 2007-05-14
11:24:00.
WARNING: This latency is over the Tombstone Lifetime
of 60 days!

. SERVER2003 passed test Replications
Starting test: NCSecDesc
. SERVER2003 passed test NCSecDesc
Starting test: NetLogons
. SERVER2003 passed test NetLogons
Starting test: Advertising
. SERVER2003 passed test Advertising
Starting test: KnowsOfRoleHolders
. SERVER2003 passed test
KnowsOfRoleHolders
Starting test: RidManager
. SERVER2003 passed test RidManager
Starting test: MachineAccount
. SERVER2003 passed test
MachineAccount
Starting test: Services
. SERVER2003 passed test Services
Starting test: ObjectsReplicated
. SERVER2003 passed test
ObjectsReplicated
Starting test: frssysvol
. SERVER2003 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.
. SERVER2003 failed test frsevent
Starting test: kccevent
. SERVER2003 passed test kccevent
Starting test: systemlog
. SERVER2003 passed test systemlog
Starting test: VerifyReferences
. SERVER2003 passed test
VerifyReferences

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

Running enterprise tests on : rlya.com.ar
Starting test: Intersite
. rlya.com.ar passed test Intersite
Starting test: FsmoCheck
. rlya.com.ar passed test FsmoCheck

C:\Archivos de programa\Support Tools>

Preguntas similare

Leer las respuestas

#1 Antonio Zorita
02/04/2009 - 09:04 | Informe spam
Cuando has usado NTDSUTIL, ¿has seguido los siguientes pasos?:
- Roles
- Connection
- Connection Server <controlador_de_dominio>
- Quit
- Transfer <rol>
En el caso de que no funcione esto último intentar:
- Seize <rol>

Espero que te sea de utilidad.


"Esteban" wrote:

Estimados

En mi dominio tenia un DC 2000 y luego promovi otro WK2003.Ambos
estuvieron funcionando bien.En un momento quite el WK2000.Siguio todo
lo ms bien.
ahora quize instalar otro WK2003 y no me permitia, descubri que el
Wk2000 tenia los 5 roles.
Realice un Seize de los roles al WK2003 pero no me generar el
Forestprep y Domainprep.Dice que el dominio no esta replicado,En Sites
and Services active Directory sigue figurando ese 2000.
De acuerdo a la documentacion intente con NTDSutil, Metadata cleanup
pero tampoco lo he podido solucionar.Les adjunto el DCDIAG.de manera
que puedan ver si pueden ver como pueden ayudarme a solucionarlo.

De antemano muchs gracias.

Esteban

C:\Archivos de programa\Support Tools>dcdiag

Domain Controller Diagnosis

Performing initial setup:
Done gathering initial info.

Doing initial required tests

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

Doing primary tests

Testing server: Nombre-predeterminado-primer-sitio\SERVER2003
Starting test: Replications
[Replications Check,SERVER2003] A recent replication attempt
failed:
From BDC to SERVER2003
Naming Context:
CN=Schema,CN=Configuration,DC=rlya,DC=com,DC=ar
The replication generated an error (1722):
El servidor RPC no está disponible.
The failure occurred at 2009-03-27 17:00:11.
The last success occurred at 2007-05-14 10:58:30.
16242 failures have occurred since the last success.
[BDC] DsBindWithSpnEx() failed with error 1722,
El servidor RPC no está disponible..
The source remains down. Please check the machine.
[Replications Check,SERVER2003] A recent replication attempt
failed:
From BDC to SERVER2003
Naming Context: CN=Configuration,DC=rlya,DC=com,DC=ar
The replication generated an error (1722):
El servidor RPC no está disponible.
The failure occurred at 2009-03-27 16:59:50.
The last success occurred at 2007-05-14 11:22:29.
16242 failures have occurred since the last success.
The source remains down. Please check the machine.
[Replications Check,SERVER2003] A recent replication attempt
failed:
From BDC to SERVER2003
Naming Context: DC=rlya,DC=com,DC=ar
The replication generated an error (1722):
El servidor RPC no está disponible.
The failure occurred at 2009-03-27 16:59:29.
The last success occurred at 2007-05-14 11:24:00.
20310 failures have occurred since the last success.
The source remains down. Please check the machine.
REPLICATION-RECEIVED LATENCY WARNING
SERVER2003: Current time is 2009-03-27 17:35:20.
CN=Schema,CN=Configuration,DC=rlya,DC=com,DC=ar
Last replication recieved from BDC at 2007-05-14
10:58:30.
WARNING: This latency is over the Tombstone Lifetime
of 60 days!

CN=Configuration,DC=rlya,DC=com,DC=ar
Last replication recieved from BDC at 2007-05-14
11:22:29.
WARNING: This latency is over the Tombstone Lifetime
of 60 days!

DC=rlya,DC=com,DC=ar
Last replication recieved from BDC at 2007-05-14
11:24:00.
WARNING: This latency is over the Tombstone Lifetime
of 60 days!

. SERVER2003 passed test Replications
Starting test: NCSecDesc
. SERVER2003 passed test NCSecDesc
Starting test: NetLogons
. SERVER2003 passed test NetLogons
Starting test: Advertising
. SERVER2003 passed test Advertising
Starting test: KnowsOfRoleHolders
. SERVER2003 passed test
KnowsOfRoleHolders
Starting test: RidManager
. SERVER2003 passed test RidManager
Starting test: MachineAccount
. SERVER2003 passed test
MachineAccount
Starting test: Services
. SERVER2003 passed test Services
Starting test: ObjectsReplicated
. SERVER2003 passed test
ObjectsReplicated
Starting test: frssysvol
. SERVER2003 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.
. SERVER2003 failed test frsevent
Starting test: kccevent
. SERVER2003 passed test kccevent
Starting test: systemlog
. SERVER2003 passed test systemlog
Starting test: VerifyReferences
. SERVER2003 passed test
VerifyReferences

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

Running enterprise tests on : rlya.com.ar
Starting test: Intersite
. rlya.com.ar passed test Intersite
Starting test: FsmoCheck
. rlya.com.ar passed test FsmoCheck

C:\Archivos de programa\Support Tools>

email Siga el debate Respuesta Responder a este mensaje
Ads by Google
Help Hacer una preguntaRespuesta Tengo una respuesta
Search Busqueda sugerida