Problemas entre W2k y un w2k3 r2

25/01/2007 - 00:05 por David Caso | Informe spam
Buenas,

os comento la situación, tenemos 2 servidores, uno con w2k y otro con
w2k3r2. Y estamos teniendo problemas para la replicacion entre ellos.
Desde sitios y servicios si intentamos sincronizar desde w2k al W2k3r2,
se nos dice que el servidor RPC no es operacional.
Una de las cosas que me ha llamado la atencion, es que desde el Sitios y
servicios, donde estan las entradas para replicar entre servidores, la
que replica desde el w2k al w2k3r2, se nos ha cambiado el texto de
"<generado automaticamente>", por la cadena del identificador.

He probado a reiniciar el netlogon, para que registre todas las DNS, y
una cuantas cosillas mas.

He corrido el netdiag,dcdiag y el nltest. os dejo la parte de los
resultados que "yo creo", que sean mas "importantes", a ver si podeis
ayudarme, si necesitais algo mas, aqui estoy.

central2 - es el w2k3 r2
central - es el w2k

-


netdiag (da todas pasadas menos estas)

Trust relationship test. . . . . . : Failed
[FATAL] Secure channel to domain 'DOMINIO' is broken.
[ERROR_NO_LOGON_SERVERS]



-


dcdiag

Domain Controller Diagnosis

Performing initial setup:
Done gathering initial info.

Doing initial required tests

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

Doing primary tests

Testing server: Nombre-predeterminado-primer-sitio\central2
Starting test: Replications
[CENTRAL] DsBindWithSpnEx() failed with error 1722,
El servidor RPC no está disponible..
. central2 passed test Replications
Starting test: NCSecDesc
. central2 passed test NCSecDesc
Starting test: NetLogons
. central2 passed test NetLogons
Starting test: Advertising
Warning: central2 is not advertising as a time server.
. central2 failed test Advertising
Starting test: KnowsOfRoleHolders
Warning: CENTRAL is the Schema Owner, but is not responding to
DS RPC B
ind.
[CENTRAL] LDAP search failed with error 58,
El servidor especificado no puede ejecutar la operación
solicitada..
Warning: CENTRAL is the Schema Owner, but is not responding to
LDAP Bin
d.
Warning: CENTRAL is the Domain Owner, but is not responding to
DS RPC B
ind.
Warning: CENTRAL is the Domain Owner, but is not responding to
LDAP Bin
d.
Warning: CENTRAL is the PDC Owner, but is not responding to DS
RPC Bind
.
Warning: CENTRAL is the PDC Owner, but is not responding to
LDAP Bind.
Warning: CENTRAL is the Rid Owner, but is not responding to DS
RPC Bind
.
Warning: CENTRAL is the Rid Owner, but is not responding to
LDAP Bind.
Warning: CENTRAL is the Infrastructure Update Owner, but is
not respond
ing to DS RPC Bind.
Warning: CENTRAL is the Infrastructure Update Owner, but is
not respond
ing to LDAP Bind.
. central2 failed test KnowsOfRoleHolders
Starting test: RidManager
. central2 failed test RidManager
Starting test: MachineAccount
Warning: Attribute userAccountControl of central2 is: 0x82020
= ( UF_
PASSWD_NOTREQD | UF_SERVER_TRUST_ACCOUNT | UF_TRUSTED_FOR_DELEGATION )
Typical setting for a DC is 0x82000 = (
UF_SERVER_TRUST_ACCOUNT | UF_TR
USTED_FOR_DELEGATION )
This may be affecting replication?


Running enterprise tests on : DOMINIO
Starting test: Intersite
. DOMINIO passed test Intersite
Starting test: FsmoCheck
Warning: DcGetDcName(PDC_REQUIRED) call failed, error 1355
A Primary Domain Controller could not be located.
The server holding the PDC role is down.
. DOMINIO failed test FsmoCheck




-



nltest /dsgetdc:dominio /pdc

DC: \\central.DOMINIO
Address: \\192.168.10.1
Dom Guid: 42156556-ff59-4048-ade6-100672f8e131
Dom Name: DOMINIO
Forest Name: DOMINIO
Dc Site Name: Nombre-predeterminado-primer-sitio
Our Site Name: Nombre-predeterminado-primer-sitio
Flags: PDC GC DS LDAP KDC TIMESERV WRITABLE DNS_DC DNS_DOMAIN
DNS_FOREST
CLOSE_SITE
The command completed successfully



-


nltest /dsgetdc:dominio /force
DC: \\central2.DOMINIO
Address: \\192.168.11.1
Dom Guid: 42156556-ff59-4048-ade6-100672f8e131
Dom Name: DOMINIO
Forest Name: DOMINIO
Dc Site Name: Nombre-predeterminado-primer-sitio
Our Site Name: Nombre-predeterminado-primer-sitio
Flags: GC DS LDAP KDC WRITABLE DNS_DC DNS_DOMAIN DNS_FOREST
CLOSE_SITE
The command completed successfully

-

nltest /sc_query:dominio
Flags: 0
Trusted DC Name
Trusted DC Connection Status Status = 1311 0x51f ERROR_NO_LOGON_SERVERS
The command completed successfully


-


nltest /dsgetdc:dominio /force
DC: \\central2.DOMINIO
Address: \\192.168.11.1
Dom Guid: 42156556-ff59-4048-ade6-100672f8e131
Dom Name: DOMINIO
Forest Name: DOMINIO
Dc Site Name: Nombre-predeterminado-primer-sitio
Our Site Name: Nombre-predeterminado-primer-sitio
Flags: GC DS LDAP KDC WRITABLE DNS_DC DNS_DOMAIN DNS_FOREST
CLOSE_SITE
The command completed successfully



-




si has llegado hasta aqui, solo por eso, muchas gracias
 

Leer las respuestas

#1 Javier Inglés [MS MVP]
25/01/2007 - 08:37 | Informe spam
Qué procedimiento llevásteis a cabo para poner un 2003 R2 como DC adicional
de un dominio con DCs de 2000??

Se comprobó antes que el AD estaba correcto? Se preparó bien el esquema y el
dominio antes para que el 2000 soporte un DC con 2003 R2??

A parte:

Domain controller is not functioning correctly
http://support.microsoft.com/kb/837513/en-us


Salu2!!
Javier Inglés
https://mvp.support.microsoft.com/p...B5567431B0
MS MVP, Windows Server-Directory Services



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

os comento la situación, tenemos 2 servidores, uno con w2k y otro con
w2k3r2. Y estamos teniendo problemas para la replicacion entre ellos.
Desde sitios y servicios si intentamos sincronizar desde w2k al W2k3r2, se
nos dice que el servidor RPC no es operacional.
Una de las cosas que me ha llamado la atencion, es que desde el Sitios y
servicios, donde estan las entradas para replicar entre servidores, la que
replica desde el w2k al w2k3r2, se nos ha cambiado el texto de "<generado
automaticamente>", por la cadena del identificador.

He probado a reiniciar el netlogon, para que registre todas las DNS, y una
cuantas cosillas mas.

He corrido el netdiag,dcdiag y el nltest. os dejo la parte de los
resultados que "yo creo", que sean mas "importantes", a ver si podeis
ayudarme, si necesitais algo mas, aqui estoy.

central2 - es el w2k3 r2
central - es el w2k

-


netdiag (da todas pasadas menos estas)

Trust relationship test. . . . . . : Failed
[FATAL] Secure channel to domain 'DOMINIO' is broken.
[ERROR_NO_LOGON_SERVERS]



-


dcdiag

Domain Controller Diagnosis

Performing initial setup:
Done gathering initial info.

Doing initial required tests

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

Doing primary tests

Testing server: Nombre-predeterminado-primer-sitio\central2
Starting test: Replications
[CENTRAL] DsBindWithSpnEx() failed with error 1722,
El servidor RPC no está disponible..
. central2 passed test Replications
Starting test: NCSecDesc
. central2 passed test NCSecDesc
Starting test: NetLogons
. central2 passed test NetLogons
Starting test: Advertising
Warning: central2 is not advertising as a time server.
. central2 failed test Advertising
Starting test: KnowsOfRoleHolders
Warning: CENTRAL is the Schema Owner, but is not responding to DS
RPC B
ind.
[CENTRAL] LDAP search failed with error 58,
El servidor especificado no puede ejecutar la operación
solicitada..
Warning: CENTRAL is the Schema Owner, but is not responding to
LDAP Bin
d.
Warning: CENTRAL is the Domain Owner, but is not responding to DS
RPC B
ind.
Warning: CENTRAL is the Domain Owner, but is not responding to
LDAP Bin
d.
Warning: CENTRAL is the PDC Owner, but is not responding to DS
RPC Bind
.
Warning: CENTRAL is the PDC Owner, but is not responding to LDAP
Bind.
Warning: CENTRAL is the Rid Owner, but is not responding to DS
RPC Bind
.
Warning: CENTRAL is the Rid Owner, but is not responding to LDAP
Bind.
Warning: CENTRAL is the Infrastructure Update Owner, but is not
respond
ing to DS RPC Bind.
Warning: CENTRAL is the Infrastructure Update Owner, but is not
respond
ing to LDAP Bind.
. central2 failed test KnowsOfRoleHolders
Starting test: RidManager
. central2 failed test RidManager
Starting test: MachineAccount
Warning: Attribute userAccountControl of central2 is: 0x82020 =
( UF_
PASSWD_NOTREQD | UF_SERVER_TRUST_ACCOUNT | UF_TRUSTED_FOR_DELEGATION )
Typical setting for a DC is 0x82000 = ( UF_SERVER_TRUST_ACCOUNT |
UF_TR
USTED_FOR_DELEGATION )
This may be affecting replication?


Running enterprise tests on : DOMINIO
Starting test: Intersite
. DOMINIO passed test Intersite
Starting test: FsmoCheck
Warning: DcGetDcName(PDC_REQUIRED) call failed, error 1355
A Primary Domain Controller could not be located.
The server holding the PDC role is down.
. DOMINIO failed test FsmoCheck




-



nltest /dsgetdc:dominio /pdc

DC: \\central.DOMINIO
Address: \\192.168.10.1
Dom Guid: 42156556-ff59-4048-ade6-100672f8e131
Dom Name: DOMINIO
Forest Name: DOMINIO
Dc Site Name: Nombre-predeterminado-primer-sitio
Our Site Name: Nombre-predeterminado-primer-sitio
Flags: PDC GC DS LDAP KDC TIMESERV WRITABLE DNS_DC DNS_DOMAIN
DNS_FOREST
CLOSE_SITE
The command completed successfully



-


nltest /dsgetdc:dominio /force
DC: \\central2.DOMINIO
Address: \\192.168.11.1
Dom Guid: 42156556-ff59-4048-ade6-100672f8e131
Dom Name: DOMINIO
Forest Name: DOMINIO
Dc Site Name: Nombre-predeterminado-primer-sitio
Our Site Name: Nombre-predeterminado-primer-sitio
Flags: GC DS LDAP KDC WRITABLE DNS_DC DNS_DOMAIN DNS_FOREST
CLOSE_SITE
The command completed successfully

-

nltest /sc_query:dominio
Flags: 0
Trusted DC Name
Trusted DC Connection Status Status = 1311 0x51f ERROR_NO_LOGON_SERVERS
The command completed successfully


-


nltest /dsgetdc:dominio /force
DC: \\central2.DOMINIO
Address: \\192.168.11.1
Dom Guid: 42156556-ff59-4048-ade6-100672f8e131
Dom Name: DOMINIO
Forest Name: DOMINIO
Dc Site Name: Nombre-predeterminado-primer-sitio
Our Site Name: Nombre-predeterminado-primer-sitio
Flags: GC DS LDAP KDC WRITABLE DNS_DC DNS_DOMAIN DNS_FOREST
CLOSE_SITE
The command completed successfully



-




si has llegado hasta aqui, solo por eso, muchas gracias

Preguntas similares