Error urgente registro DNS servidor

03/10/2008 - 09:42 por David | Informe spam
Buenas a todos,

tengo mi servidor secundario de AD con errores en el DNS. Por ejemplo, no
puedo hacer ping a los pcs de los usuarios desde este servidor, en cambio a
ciertos servidores si.

Os copio los resultados de dcdiag y netdiag a ver si me podeis ayudar:

NETDIAG:
DNS test . . . . . . . . . . . . . : Failed
[WARNING] Cannot find a primary authoritative DNS server for the
name
'server2.midominio.com.'. [WSAENOPROTOOPT ]
The name 'server2.midominio.com.' may not be registered in DNS.
[FATAL] File \configetlogon.dns contains invalid DNS entries.
[FATAL] File \configetlogon.dns contains invalid DNS entries. [FATAL]
No DNS servers have the DNS records for this DC registered.

Trust relationship test. . . . . . : Failed
[FATAL] Secure channel to domain 'MIDOMINIO' 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\SERVER2
Starting test: Connectivity
The host 2b677287-00d3-4997-b2b0-8b41248dabe2._msdcs.midominio.com
could not be resolved to an
IP address. Check the DNS server, DHCP, server name, etc
Although the Guid DNS name
(2b677287-00d3-4997-b2b0-8b41248dabe2._msdcs.midominio.com) couldn't be
resolved, the server name (server2.midominio.com) resolved to the IP
address (192.168.1.4) and was pingable. Check that the IP address is
registered correctly with the DNS server.
. SERVER2 failed test Connectivity

Doing primary tests

Starting test: FsmoCheck
Warning: DcGetDcName(PDC_REQUIRED) call failed, error 10042
A Primary Domain Controller could not be located.
The server holding the PDC role is down.
Warning: DcGetDcName(TIME_SERVER) call failed, error 10042
A Time Server could not be located.
The server holding the PDC role is down.
Warning: DcGetDcName(GOOD_TIME_SERVER_PREFERRED) call failed, error
10042
A Good Time Server could not be located.
. midominio.com failed test FsmoCheck



Muchas gracias,

Preguntas similare

Leer las respuestas

#1 Roberto Di Lello
03/10/2008 - 22:10 | Informe spam
a ver si entendi. El servidor secundario es DC y tiene el rol de DNS.
esta bien configurada la placa de red? La zona es AD integrated y tiene
habilitado dynamic updates (???).

Saludos.


"David" escribió en el mensaje de
noticias:#
Buenas a todos,

tengo mi servidor secundario de AD con errores en el DNS. Por ejemplo, no
puedo hacer ping a los pcs de los usuarios desde este servidor, en cambio
a ciertos servidores si.

Os copio los resultados de dcdiag y netdiag a ver si me podeis ayudar:

NETDIAG:
DNS test . . . . . . . . . . . . . : Failed
[WARNING] Cannot find a primary authoritative DNS server for the
name
'server2.midominio.com.'. [WSAENOPROTOOPT ]
The name 'server2.midominio.com.' may not be registered in DNS.
[FATAL] File \configetlogon.dns contains invalid DNS entries.
[FATAL] File \configetlogon.dns contains invalid DNS entries. [FATAL]
No DNS servers have the DNS records for this DC registered.

Trust relationship test. . . . . . : Failed
[FATAL] Secure channel to domain 'MIDOMINIO' 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\SERVER2
Starting test: Connectivity
The host 2b677287-00d3-4997-b2b0-8b41248dabe2._msdcs.midominio.com
could not be resolved to an
IP address. Check the DNS server, DHCP, server name, etc
Although the Guid DNS name
(2b677287-00d3-4997-b2b0-8b41248dabe2._msdcs.midominio.com) couldn't be
resolved, the server name (server2.midominio.com) resolved to the IP
address (192.168.1.4) and was pingable. Check that the IP address is
registered correctly with the DNS server.
. SERVER2 failed test Connectivity

Doing primary tests

Starting test: FsmoCheck
Warning: DcGetDcName(PDC_REQUIRED) call failed, error 10042
A Primary Domain Controller could not be located.
The server holding the PDC role is down.
Warning: DcGetDcName(TIME_SERVER) call failed, error 10042
A Time Server could not be located.
The server holding the PDC role is down.
Warning: DcGetDcName(GOOD_TIME_SERVER_PREFERRED) call failed,
error 10042
A Good Time Server could not be located.
. midominio.com failed test FsmoCheck



Muchas gracias,

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