Forums Últimos mensajes - Powered by IBM
 
Tags Palabras claves

errores 1058 y 1030 en servidores

16/10/2007 - 09:16 por rodolfo | Informe spam
Ayuda Hacer una pregunta
Tengo un dominio con dos servidores Windows Server 2003 Standar Edition
(ambos con Service Pack 2) y cada vez que hay que hacer un reinicio
(habitualmente debido a las actualizaciones) en cualquiera de ellos sucede
que tarda aparecer la pantalla de bienvenida (pulse CTRL + ALT + SUPR) y
despues aparecen muchos mensajes de error 1058 y 1030 en el visor de sucesos
(aparecen cada 5 minutos) de ambos servidores. Ademas los usuarios del
dominio notan cortes en la conexion con los servidores que les hace reiniciar
las aplicaciones. Ambos (servidor 1 y servidor2) son controladores de dominio
y servidores DNS. Uno de ellos (servidor1) es catalogo global, emulador PDC y
maestro de esquema, nombres de dominio, RID e infraestructura, y ademas es
reenviador de las peticiones DNS de fuera del dominio (internet) de forma que
ambos servidores y todas las estaciones de trabajo (que son Windows XP
Professional) apuntan a dicho servidor como servidor DNS preferido, estando
vacio el servidor DNS alternativo.
Todo aparentemente esta correcto ya que cuando NO se dan dichos errores
sucede que:
- el comando nslookup devuelve servidor1
- dcdiag no devuelve errores (passed test en todos los test que realiza)
- el funcionamiento es correcto en ambos servidores y no hay cortes en las
aplicaciones
Quisiera saber como resolverlo, ya que en esta situacion da miedo hacer un
reinicio.
Un saludo,
Rodolfo.
email Siga el debateRespuesta 9 respuestasRespuesta Tengo una respuesta

Preguntas similare

Leer las respuestas

#6 rodolfo
17/10/2007 - 09:37 | Informe spam
Buenos dias Javier,
Ambos DC son servidores DNS (pues así le instalé): tanto en el primero como
en el segundo cuando arranco la aplicacion Inicio -> Herramientas
Administrativas -> DNS puedo ver a ambos servidores, y ademas si ejecuto
Inicio -> Herramientas Aministrativas -> Administre su servidor en ambos
puedo ver que tienen la funcion de Servidor DNS. Servidor1 es ademas
reenviador y ambos en las propiedades de TCP/IP en servidor DNS preferido
apuntan a servidor1. Quisiera saber en que te basas para decir que servidor2
no es servidor DNS, te lo digo por si tuviera algo mal configurado. Las
Support Tools las he instalado del cd de windows server 2003 (sin Service
packs) despues de instalar Service Pack 2 en ambos servidores: es por ello
por lo que esten desactualizadas; quisiera que me dijeras donde conseguir las
actualizadas. Y muchas gracias por todo, me quedo mas tranquilo al saber que
la tardanza sea normal.
Un saludo,
Rodolfo.


"Javier Inglés [MS MVP]" wrote:

Perfecto, no obstante, actualiza las supoprt tools que tienes instalaas las
de 2000 y no las de 2003.

A aprte, el segundo DC no es DNS, por lo que a la hora de reiniciar los DCS,
deberías rieniciar siempre primero el DC1, y cuando haya arrancado del todo,
reiniciar el segundo; un DC puede ser normal que tarde más o menos tiempo en
iniciar debido a todas las comprobacions/registros/etc implicados en
levantar loss ervicios de directorio adecuados.

Una vez hayas hecho el reinicio controlado de esa forma, verifica de nuevo
los visores de eventos a ver si se siguen produciendo o no los errores
Salu2!!
Javier Inglés
https://mvp.support.microsoft.com/p...B5567431B0
MS MVP, Windows Server-Directory Services



"rodolfo" escribió en el mensaje
news:
> Buenos dias Javier, te mando el resultado:
>
> (servidor1)
> C:\>dcdiag
>
> Domain Controller Diagnosis
>
> Performing initial setup:
> Done gathering initial info.
>
> Doing initial required tests
>
> Testing server: Nombre-predeterminado-primer-sitio\SERVIDOR1
> Starting test: Connectivity
> . SERVIDOR1 passed test Connectivity
>
> Doing primary tests
>
> Testing server: Nombre-predeterminado-primer-sitio\SERVIDOR1
> Starting test: Replications
> . SERVIDOR1 passed test Replications
> Starting test: NCSecDesc
> . SERVIDOR1 passed test NCSecDesc
> Starting test: NetLogons
> . SERVIDOR1 passed test NetLogons
> Starting test: Advertising
> . SERVIDOR1 passed test Advertising
> Starting test: KnowsOfRoleHolders
> . SERVIDOR1 passed test KnowsOfRoleHolders
> Starting test: RidManager
> . SERVIDOR1 passed test RidManager
> Starting test: MachineAccount
> . SERVIDOR1 passed test MachineAccount
> Starting test: Services
> . SERVIDOR1 passed test Services
> Starting test: ObjectsReplicated
> . SERVIDOR1 passed test ObjectsReplicated
> Starting test: frssysvol
> . SERVIDOR1 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.
> . SERVIDOR1 failed test frsevent
> Starting test: kccevent
> . SERVIDOR1 passed test kccevent
> Starting test: systemlog
> . SERVIDOR1 passed test systemlog
> Starting test: VerifyReferences
> . SERVIDOR1 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 : ayuntamiento
> Starting test: CrossRefValidation
> . ayuntamiento passed test CrossR
> efValidation
> Starting test: CheckSDRefDom
> . ayuntamiento passed test CheckS
> DRefDom
>
> Running enterprise tests on : ayuntamiento.local
> Starting test: Intersite
> . ayuntamiento.local passed test
> Intersite
> Starting test: FsmoCheck
> . ayuntamiento.local passed test
> FsmoCheck
>
> C:\>netdiag
>
>
>
> Computer Name: SERVIDOR1
> DNS Host Name: servidor1.ayuntamiento.local
> System info : Windows 2000 Server (Build 3790)
> Processor : x86 Family 6 Model 15 Stepping 6, GenuineIntel
> List of installed hotfixes :
> KB921503
> KB924667-v2
> KB925398_WMP64
> KB925902
> KB926122
> KB927891
> KB929123
> KB930178
> KB931784
> KB932168
> KB933360
> KB933729
> KB933854
> KB935839
> KB935840
> KB935966
> KB936021
> KB936357
> KB936782
> KB937143
> KB938127
> KB939653
> KB941202
> 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 h
> as 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. . . . . . . . . : servidor1
> IP Address . . . . . . . . : 192.168.1.11
> Subnet Mask. . . . . . . . : 255.255.255.0
> Default Gateway. . . . . . : 192.168.1.2
> Dns Servers. . . . . . . . : 192.168.1.11
>
>
> AutoConfiguration results. . . . . . : Passed
>
> Default gateway test . . . : Passed
>
> NetBT name test. . . . . . : Passed
> [WARNING] At least one of the <00> 'WorkStation Service', <03>
> 'Messenge
> r Service', <20> 'WINS' names is missing.
>
> WINS service test. . . . . : Skipped
> There are no WINS servers configured for this interface.
>
>
> Global results:
>
>
> Domain membership test . . . . . . : Passed
>
>
> NetBT transports test. . . . . . . : Passed
> List of NetBt transports currently configured:
> NetBT_Tcpip_{8C6C1006-28EB-4053-8DCF-FA4391FB2EC3}
> 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
> Servi
> ce', <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.1.11
> ' and other DCs also have some of the names registered.
>
>
> Redir and Browser test . . . . . . : Passed
> List of NetBt transports currently bound to the Redir
> NetBT_Tcpip_{8C6C1006-28EB-4053-8DCF-FA4391FB2EC3}
> The redir is bound to 1 NetBt transport.
>
> List of NetBt transports currently bound to the browser
> NetBT_Tcpip_{8C6C1006-28EB-4053-8DCF-FA4391FB2EC3}
> The browser is bound to 1 NetBt transport.
>
>
> DC discovery test. . . . . . . . . : Passed
>
>
> DC list test . . . . . . . . . . . : Passed
>
>
> Trust relationship test. . . . . . : Skipped
>
>
> Kerberos test. . . . . . . . . . . : Passed
>
>
> LDAP test. . . . . . . . . . . . . : Passed
>
>
> 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
>
> C:\>
>
> (servidor2)
>
> C:\>dcdiag
>
> Domain Controller Diagnosis
>
> Performing initial setup:
> Done gathering initial info.
>
> Doing initial required tests
>
> Testing server: Nombre-predeterminado-primer-sitio\SERVIDOR2
> Starting test: Connectivity
> . SERVIDOR2 passed test Connectivity
>
> Doing primary tests
>
> Testing server: Nombre-predeterminado-primer-sitio\SERVIDOR2
> Starting test: Replications
> . SERVIDOR2 passed test Replications
> Starting test: NCSecDesc
> . SERVIDOR2 passed test NCSecDesc
> Starting test: NetLogons
> . SERVIDOR2 passed test NetLogons
> Starting test: Advertising
> . SERVIDOR2 passed test Advertising
> Starting test: KnowsOfRoleHolders
> . SERVIDOR2 passed test KnowsOfRoleHolders
> Starting test: RidManager
> . SERVIDOR2 passed test RidManager
Respuesta Responder a este mensaje
#7 Javier Inglés [MS MVP]
17/10/2007 - 09:49 | Informe spam
Lo del DNs te lo digo porque si ambos DCs son DNSs, deberían tener la
configuración así

DC1
DNS1: DC1
DNS2: DC2

DC2
DNS1:DC2
DNS2:DC1

Las Support Tools que tienes instaladas son las de 2000, ya que el report te
reocnoce el sistema como tal y no como 2003:

System info : Windows 2000 Server (Build 3790)
Processor : x86 Family 6 Model 15 Stepping 6, GenuineIntel

Para las actualizadas puedes usar estas

http://www.petri.co.il/download_win..._tools.htm


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



"rodolfo" escribió en el mensaje
news:
Buenos dias Javier,
Ambos DC son servidores DNS (pues así le instalé): tanto en el primero
como
en el segundo cuando arranco la aplicacion Inicio -> Herramientas
Administrativas -> DNS puedo ver a ambos servidores, y ademas si ejecuto
Inicio -> Herramientas Aministrativas -> Administre su servidor en ambos
puedo ver que tienen la funcion de Servidor DNS. Servidor1 es ademas
reenviador y ambos en las propiedades de TCP/IP en servidor DNS preferido
apuntan a servidor1. Quisiera saber en que te basas para decir que
servidor2
no es servidor DNS, te lo digo por si tuviera algo mal configurado. Las
Support Tools las he instalado del cd de windows server 2003 (sin Service
packs) despues de instalar Service Pack 2 en ambos servidores: es por ello
por lo que esten desactualizadas; quisiera que me dijeras donde conseguir
las
actualizadas. Y muchas gracias por todo, me quedo mas tranquilo al saber
que
la tardanza sea normal.
Un saludo,
Rodolfo.


"Javier Inglés [MS MVP]" wrote:

Perfecto, no obstante, actualiza las supoprt tools que tienes instalaas
las
de 2000 y no las de 2003.

A aprte, el segundo DC no es DNS, por lo que a la hora de reiniciar los
DCS,
deberías rieniciar siempre primero el DC1, y cuando haya arrancado del
todo,
reiniciar el segundo; un DC puede ser normal que tarde más o menos tiempo
en
iniciar debido a todas las comprobacions/registros/etc implicados en
levantar loss ervicios de directorio adecuados.

Una vez hayas hecho el reinicio controlado de esa forma, verifica de
nuevo
los visores de eventos a ver si se siguen produciendo o no los errores
Salu2!!
Javier Inglés
https://mvp.support.microsoft.com/p...B5567431B0
MS MVP, Windows Server-Directory Services



"rodolfo" escribió en el mensaje
news:
> Buenos dias Javier, te mando el resultado:
>
> (servidor1)
> C:\>dcdiag
>
> Domain Controller Diagnosis
>
> Performing initial setup:
> Done gathering initial info.
>
> Doing initial required tests
>
> Testing server: Nombre-predeterminado-primer-sitio\SERVIDOR1
> Starting test: Connectivity
> . SERVIDOR1 passed test Connectivity
>
> Doing primary tests
>
> Testing server: Nombre-predeterminado-primer-sitio\SERVIDOR1
> Starting test: Replications
> . SERVIDOR1 passed test Replications
> Starting test: NCSecDesc
> . SERVIDOR1 passed test NCSecDesc
> Starting test: NetLogons
> . SERVIDOR1 passed test NetLogons
> Starting test: Advertising
> . SERVIDOR1 passed test Advertising
> Starting test: KnowsOfRoleHolders
> . SERVIDOR1 passed test
> KnowsOfRoleHolders
> Starting test: RidManager
> . SERVIDOR1 passed test RidManager
> Starting test: MachineAccount
> . SERVIDOR1 passed test MachineAccount
> Starting test: Services
> . SERVIDOR1 passed test Services
> Starting test: ObjectsReplicated
> . SERVIDOR1 passed test
> ObjectsReplicated
> Starting test: frssysvol
> . SERVIDOR1 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.
> . SERVIDOR1 failed test frsevent
> Starting test: kccevent
> . SERVIDOR1 passed test kccevent
> Starting test: systemlog
> . SERVIDOR1 passed test systemlog
> Starting test: VerifyReferences
> . SERVIDOR1 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 : ayuntamiento
> Starting test: CrossRefValidation
> . ayuntamiento passed test CrossR
> efValidation
> Starting test: CheckSDRefDom
> . ayuntamiento passed test CheckS
> DRefDom
>
> Running enterprise tests on : ayuntamiento.local
> Starting test: Intersite
> . ayuntamiento.local passed test
> Intersite
> Starting test: FsmoCheck
> . ayuntamiento.local passed test
> FsmoCheck
>
> C:\>netdiag
>
>
>
> Computer Name: SERVIDOR1
> DNS Host Name: servidor1.ayuntamiento.local
> System info : Windows 2000 Server (Build 3790)
> Processor : x86 Family 6 Model 15 Stepping 6, GenuineIntel
> List of installed hotfixes :
> KB921503
> KB924667-v2
> KB925398_WMP64
> KB925902
> KB926122
> KB927891
> KB929123
> KB930178
> KB931784
> KB932168
> KB933360
> KB933729
> KB933854
> KB935839
> KB935840
> KB935966
> KB936021
> KB936357
> KB936782
> KB937143
> KB938127
> KB939653
> KB941202
> 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 h
> as 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. . . . . . . . . : servidor1
> IP Address . . . . . . . . : 192.168.1.11
> Subnet Mask. . . . . . . . : 255.255.255.0
> Default Gateway. . . . . . : 192.168.1.2
> Dns Servers. . . . . . . . : 192.168.1.11
>
>
> AutoConfiguration results. . . . . . : Passed
>
> Default gateway test . . . : Passed
>
> NetBT name test. . . . . . : Passed
> [WARNING] At least one of the <00> 'WorkStation Service', <03>
> 'Messenge
> r Service', <20> 'WINS' names is missing.
>
> WINS service test. . . . . : Skipped
> There are no WINS servers configured for this interface.
>
>
> Global results:
>
>
> Domain membership test . . . . . . : Passed
>
>
> NetBT transports test. . . . . . . : Passed
> List of NetBt transports currently configured:
> NetBT_Tcpip_{8C6C1006-28EB-4053-8DCF-FA4391FB2EC3}
> 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
> Servi
> ce', <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.1.11
> ' and other DCs also have some of the names registered.
>
>
> Redir and Browser test . . . . . . : Passed
> List of NetBt transports currently bound to the Redir
> NetBT_Tcpip_{8C6C1006-28EB-4053-8DCF-FA4391FB2EC3}
> The redir is bound to 1 NetBt transport.
>
> List of NetBt transports currently bound to the browser
> NetBT_Tcpip_{8C6C1006-28EB-4053-8DCF-FA4391FB2EC3}
> The browser is bound to 1 NetBt transport.
>
>
> DC discovery test. . . . . . . . . : Passed
>
>
> DC list test . . . . . . . . . . . : Passed
>
>
> Trust relationship test. . . . . . : Skipped
>
>
> Kerberos test. . . . . . . . . . . : Passed
>
>
> LDAP test. . . . . . . . . . . . . : Passed
>
>
> 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
>
> C:\>
>
> (servidor2)
>
> C:\>dcdiag
>
> Domain Controller Diagnosis
>
> Performing initial setup:
> Done gathering initial info.
>
> Doing initial required tests
>
> Testing server: Nombre-predeterminado-primer-sitio\SERVIDOR2
> Starting test: Connectivity
> . SERVIDOR2 passed test Connectivity
>
> Doing primary tests
>
> Testing server: Nombre-predeterminado-primer-sitio\SERVIDOR2
> Starting test: Replications
> . SERVIDOR2 passed test Replications
> Starting test: NCSecDesc
> . SERVIDOR2 passed test NCSecDesc
> Starting test: NetLogons
> . SERVIDOR2 passed test NetLogons
> Starting test: Advertising
> . SERVIDOR2 passed test Advertising
> Starting test: KnowsOfRoleHolders
> . SERVIDOR2 passed test
> KnowsOfRoleHolders
> Starting test: RidManager
> . SERVIDOR2 passed test RidManager
Respuesta Responder a este mensaje
#8 rodolfo
17/10/2007 - 10:05 | Informe spam
Hola Javier,
muchisimas gracias por todo,
un saludo,
Rodolfo.


"Javier Inglés [MS MVP]" wrote:

Lo del DNs te lo digo porque si ambos DCs son DNSs, deberían tener la
configuración así

DC1
DNS1: DC1
DNS2: DC2

DC2
DNS1:DC2
DNS2:DC1

Las Support Tools que tienes instaladas son las de 2000, ya que el report te
reocnoce el sistema como tal y no como 2003:

System info : Windows 2000 Server (Build 3790)
Processor : x86 Family 6 Model 15 Stepping 6, GenuineIntel

Para las actualizadas puedes usar estas

http://www.petri.co.il/download_win..._tools.htm


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



"rodolfo" escribió en el mensaje
news:
> Buenos dias Javier,
> Ambos DC son servidores DNS (pues así le instalé): tanto en el primero
> como
> en el segundo cuando arranco la aplicacion Inicio -> Herramientas
> Administrativas -> DNS puedo ver a ambos servidores, y ademas si ejecuto
> Inicio -> Herramientas Aministrativas -> Administre su servidor en ambos
> puedo ver que tienen la funcion de Servidor DNS. Servidor1 es ademas
> reenviador y ambos en las propiedades de TCP/IP en servidor DNS preferido
> apuntan a servidor1. Quisiera saber en que te basas para decir que
> servidor2
> no es servidor DNS, te lo digo por si tuviera algo mal configurado. Las
> Support Tools las he instalado del cd de windows server 2003 (sin Service
> packs) despues de instalar Service Pack 2 en ambos servidores: es por ello
> por lo que esten desactualizadas; quisiera que me dijeras donde conseguir
> las
> actualizadas. Y muchas gracias por todo, me quedo mas tranquilo al saber
> que
> la tardanza sea normal.
> Un saludo,
> Rodolfo.
>
>
> "Javier Inglés [MS MVP]" wrote:
>
>> Perfecto, no obstante, actualiza las supoprt tools que tienes instalaas
>> las
>> de 2000 y no las de 2003.
>>
>> A aprte, el segundo DC no es DNS, por lo que a la hora de reiniciar los
>> DCS,
>> deberías rieniciar siempre primero el DC1, y cuando haya arrancado del
>> todo,
>> reiniciar el segundo; un DC puede ser normal que tarde más o menos tiempo
>> en
>> iniciar debido a todas las comprobacions/registros/etc implicados en
>> levantar loss ervicios de directorio adecuados.
>>
>> Una vez hayas hecho el reinicio controlado de esa forma, verifica de
>> nuevo
>> los visores de eventos a ver si se siguen produciendo o no los errores
>> Salu2!!
>> Javier Inglés
>> https://mvp.support.microsoft.com/p...B5567431B0
>> MS MVP, Windows Server-Directory Services
>>
>>
>>
>> "rodolfo" escribió en el mensaje
>> news:
>> > Buenos dias Javier, te mando el resultado:
>> >
>> > (servidor1)
>> > C:\>dcdiag
>> >
>> > Domain Controller Diagnosis
>> >
>> > Performing initial setup:
>> > Done gathering initial info.
>> >
>> > Doing initial required tests
>> >
>> > Testing server: Nombre-predeterminado-primer-sitio\SERVIDOR1
>> > Starting test: Connectivity
>> > . SERVIDOR1 passed test Connectivity
>> >
>> > Doing primary tests
>> >
>> > Testing server: Nombre-predeterminado-primer-sitio\SERVIDOR1
>> > Starting test: Replications
>> > . SERVIDOR1 passed test Replications
>> > Starting test: NCSecDesc
>> > . SERVIDOR1 passed test NCSecDesc
>> > Starting test: NetLogons
>> > . SERVIDOR1 passed test NetLogons
>> > Starting test: Advertising
>> > . SERVIDOR1 passed test Advertising
>> > Starting test: KnowsOfRoleHolders
>> > . SERVIDOR1 passed test
>> > KnowsOfRoleHolders
>> > Starting test: RidManager
>> > . SERVIDOR1 passed test RidManager
>> > Starting test: MachineAccount
>> > . SERVIDOR1 passed test MachineAccount
>> > Starting test: Services
>> > . SERVIDOR1 passed test Services
>> > Starting test: ObjectsReplicated
>> > . SERVIDOR1 passed test
>> > ObjectsReplicated
>> > Starting test: frssysvol
>> > . SERVIDOR1 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.
>> > . SERVIDOR1 failed test frsevent
>> > Starting test: kccevent
>> > . SERVIDOR1 passed test kccevent
>> > Starting test: systemlog
>> > . SERVIDOR1 passed test systemlog
>> > Starting test: VerifyReferences
>> > . SERVIDOR1 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 : ayuntamiento
>> > Starting test: CrossRefValidation
>> > . ayuntamiento passed test CrossR
>> > efValidation
>> > Starting test: CheckSDRefDom
>> > . ayuntamiento passed test CheckS
>> > DRefDom
>> >
>> > Running enterprise tests on : ayuntamiento.local
>> > Starting test: Intersite
>> > . ayuntamiento.local passed test
>> > Intersite
>> > Starting test: FsmoCheck
>> > . ayuntamiento.local passed test
>> > FsmoCheck
>> >
>> > C:\>netdiag
>> >
>> >
>> >
>> > Computer Name: SERVIDOR1
>> > DNS Host Name: servidor1.ayuntamiento.local
>> > System info : Windows 2000 Server (Build 3790)
>> > Processor : x86 Family 6 Model 15 Stepping 6, GenuineIntel
>> > List of installed hotfixes :
>> > KB921503
>> > KB924667-v2
>> > KB925398_WMP64
>> > KB925902
>> > KB926122
>> > KB927891
>> > KB929123
>> > KB930178
>> > KB931784
>> > KB932168
>> > KB933360
>> > KB933729
>> > KB933854
>> > KB935839
>> > KB935840
>> > KB935966
>> > KB936021
>> > KB936357
>> > KB936782
>> > KB937143
>> > KB938127
>> > KB939653
>> > KB941202
>> > 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 h
>> > as 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. . . . . . . . . : servidor1
>> > IP Address . . . . . . . . : 192.168.1.11
>> > Subnet Mask. . . . . . . . : 255.255.255.0
>> > Default Gateway. . . . . . : 192.168.1.2
>> > Dns Servers. . . . . . . . : 192.168.1.11
>> >
>> >
>> > AutoConfiguration results. . . . . . : Passed
>> >
>> > Default gateway test . . . : Passed
>> >
>> > NetBT name test. . . . . . : Passed
>> > [WARNING] At least one of the <00> 'WorkStation Service', <03>
>> > 'Messenge
>> > r Service', <20> 'WINS' names is missing.
>> >
>> > WINS service test. . . . . : Skipped
>> > There are no WINS servers configured for this interface.
>> >
>> >
>> > Global results:
>> >
>> >
>> > Domain membership test . . . . . . : Passed
>> >
>> >
>> > NetBT transports test. . . . . . . : Passed
>> > List of NetBt transports currently configured:
>> > NetBT_Tcpip_{8C6C1006-28EB-4053-8DCF-FA4391FB2EC3}
>> > 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
>> > Servi
>> > ce', <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.1.11
>> > ' and other DCs also have some of the names registered.
>> >
>> >
>> > Redir and Browser test . . . . . . : Passed
>> > List of NetBt transports currently bound to the Redir
Respuesta Responder a este mensaje
#9 Javier Inglés [MS MVP]
17/10/2007 - 10:20 | Informe spam
:-)

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



"rodolfo" escribió en el mensaje
news:
Hola Javier,
muchisimas gracias por todo,
un saludo,
Rodolfo.


"Javier Inglés [MS MVP]" wrote:

Lo del DNs te lo digo porque si ambos DCs son DNSs, deberían tener la
configuración así

DC1
DNS1: DC1
DNS2: DC2

DC2
DNS1:DC2
DNS2:DC1

Las Support Tools que tienes instaladas son las de 2000, ya que el report
te
reocnoce el sistema como tal y no como 2003:

System info : Windows 2000 Server (Build 3790)
Processor : x86 Family 6 Model 15 Stepping 6, GenuineIntel

Para las actualizadas puedes usar estas

http://www.petri.co.il/download_win..._tools.htm


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



"rodolfo" escribió en el mensaje
news:
> Buenos dias Javier,
> Ambos DC son servidores DNS (pues así le instalé): tanto en el primero
> como
> en el segundo cuando arranco la aplicacion Inicio -> Herramientas
> Administrativas -> DNS puedo ver a ambos servidores, y ademas si
> ejecuto
> Inicio -> Herramientas Aministrativas -> Administre su servidor en
> ambos
> puedo ver que tienen la funcion de Servidor DNS. Servidor1 es ademas
> reenviador y ambos en las propiedades de TCP/IP en servidor DNS
> preferido
> apuntan a servidor1. Quisiera saber en que te basas para decir que
> servidor2
> no es servidor DNS, te lo digo por si tuviera algo mal configurado. Las
> Support Tools las he instalado del cd de windows server 2003 (sin
> Service
> packs) despues de instalar Service Pack 2 en ambos servidores: es por
> ello
> por lo que esten desactualizadas; quisiera que me dijeras donde
> conseguir
> las
> actualizadas. Y muchas gracias por todo, me quedo mas tranquilo al
> saber
> que
> la tardanza sea normal.
> Un saludo,
> Rodolfo.
>
>
> "Javier Inglés [MS MVP]" wrote:
>
>> Perfecto, no obstante, actualiza las supoprt tools que tienes
>> instalaas
>> las
>> de 2000 y no las de 2003.
>>
>> A aprte, el segundo DC no es DNS, por lo que a la hora de reiniciar
>> los
>> DCS,
>> deberías rieniciar siempre primero el DC1, y cuando haya arrancado del
>> todo,
>> reiniciar el segundo; un DC puede ser normal que tarde más o menos
>> tiempo
>> en
>> iniciar debido a todas las comprobacions/registros/etc implicados en
>> levantar loss ervicios de directorio adecuados.
>>
>> Una vez hayas hecho el reinicio controlado de esa forma, verifica de
>> nuevo
>> los visores de eventos a ver si se siguen produciendo o no los errores
>> Salu2!!
>> Javier Inglés
>> https://mvp.support.microsoft.com/p...B5567431B0
>> MS MVP, Windows Server-Directory Services
>>
>>
>>
>> "rodolfo" escribió en el mensaje
>> news:
>> > Buenos dias Javier, te mando el resultado:
>> >
>> > (servidor1)
>> > C:\>dcdiag
>> >
>> > Domain Controller Diagnosis
>> >
>> > Performing initial setup:
>> > Done gathering initial info.
>> >
>> > Doing initial required tests
>> >
>> > Testing server: Nombre-predeterminado-primer-sitio\SERVIDOR1
>> > Starting test: Connectivity
>> > . SERVIDOR1 passed test Connectivity
>> >
>> > Doing primary tests
>> >
>> > Testing server: Nombre-predeterminado-primer-sitio\SERVIDOR1
>> > Starting test: Replications
>> > . SERVIDOR1 passed test Replications
>> > Starting test: NCSecDesc
>> > . SERVIDOR1 passed test NCSecDesc
>> > Starting test: NetLogons
>> > . SERVIDOR1 passed test NetLogons
>> > Starting test: Advertising
>> > . SERVIDOR1 passed test Advertising
>> > Starting test: KnowsOfRoleHolders
>> > . SERVIDOR1 passed test
>> > KnowsOfRoleHolders
>> > Starting test: RidManager
>> > . SERVIDOR1 passed test RidManager
>> > Starting test: MachineAccount
>> > . SERVIDOR1 passed test
>> > MachineAccount
>> > Starting test: Services
>> > . SERVIDOR1 passed test Services
>> > Starting test: ObjectsReplicated
>> > . SERVIDOR1 passed test
>> > ObjectsReplicated
>> > Starting test: frssysvol
>> > . SERVIDOR1 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.
>> > . SERVIDOR1 failed test frsevent
>> > Starting test: kccevent
>> > . SERVIDOR1 passed test kccevent
>> > Starting test: systemlog
>> > . SERVIDOR1 passed test systemlog
>> > Starting test: VerifyReferences
>> > . SERVIDOR1 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 : ayuntamiento
>> > Starting test: CrossRefValidation
>> > . ayuntamiento passed test CrossR
>> > efValidation
>> > Starting test: CheckSDRefDom
>> > . ayuntamiento passed test CheckS
>> > DRefDom
>> >
>> > Running enterprise tests on : ayuntamiento.local
>> > Starting test: Intersite
>> > . ayuntamiento.local passed test
>> > Intersite
>> > Starting test: FsmoCheck
>> > . ayuntamiento.local passed test
>> > FsmoCheck
>> >
>> > C:\>netdiag
>> >
>> >
>> >
>> > Computer Name: SERVIDOR1
>> > DNS Host Name: servidor1.ayuntamiento.local
>> > System info : Windows 2000 Server (Build 3790)
>> > Processor : x86 Family 6 Model 15 Stepping 6, GenuineIntel
>> > List of installed hotfixes :
>> > KB921503
>> > KB924667-v2
>> > KB925398_WMP64
>> > KB925902
>> > KB926122
>> > KB927891
>> > KB929123
>> > KB930178
>> > KB931784
>> > KB932168
>> > KB933360
>> > KB933729
>> > KB933854
>> > KB935839
>> > KB935840
>> > KB935966
>> > KB936021
>> > KB936357
>> > KB936782
>> > KB937143
>> > KB938127
>> > KB939653
>> > KB941202
>> > 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 h
>> > as 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. . . . . . . . . : servidor1
>> > IP Address . . . . . . . . : 192.168.1.11
>> > Subnet Mask. . . . . . . . : 255.255.255.0
>> > Default Gateway. . . . . . : 192.168.1.2
>> > Dns Servers. . . . . . . . : 192.168.1.11
>> >
>> >
>> > AutoConfiguration results. . . . . . : Passed
>> >
>> > Default gateway test . . . : Passed
>> >
>> > NetBT name test. . . . . . : Passed
>> > [WARNING] At least one of the <00> 'WorkStation Service',
>> > <03>
>> > 'Messenge
>> > r Service', <20> 'WINS' names is missing.
>> >
>> > WINS service test. . . . . : Skipped
>> > There are no WINS servers configured for this interface.
>> >
>> >
>> > Global results:
>> >
>> >
>> > Domain membership test . . . . . . : Passed
>> >
>> >
>> > NetBT transports test. . . . . . . : Passed
>> > List of NetBt transports currently configured:
>> > NetBT_Tcpip_{8C6C1006-28EB-4053-8DCF-FA4391FB2EC3}
>> > 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
>> > Servi
>> > ce', <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.1.11
>> > ' and other DCs also have some of the names registered.
>> >
>> >
>> > Redir and Browser test . . . . . . : Passed
>> > List of NetBt transports currently bound to the Redir
email Siga el debate Respuesta Responder a este mensaje
Ads by Google
Help Hacer una pregunta AnteriorRespuesta Tengo una respuesta
Search Busqueda sugerida