para Guillermo Delprato

22/02/2007 - 15:51 por inyakigil | Informe spam
Hola Guillermo
No se si te acoradaras del tema del dns con el dominio "no standard" y
con el siguiente error al pasar el netdiag
DC list test . . . . . . . . . . . : Failed
'IBAÑEZALDAZ': No DCs are up.
el dcdiag me da correcto
bueno pues el cliente me ha llamado 2 veces en 3 semanas porque no
conseguian ver los recuros compartidos del servidor (reiniciando la
máquina se soluciona) he seguido mirando y le he pasado el diagnostico
dcdiag /test:dns y me sale lo siguiente:


Domain Controller Diagnosis

Performing initial setup:
Done gathering initial info.

Doing initial required tests

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

Doing primary tests

Testing server: Nombre-predeterminado-primer-sitio\SERVIDOR

DNS Tests are running and not hung. Please wait a few minutes...

Running partition tests on : ForestDnsZones

Running partition tests on : DomainDnsZones

Running partition tests on : Schema

Running partition tests on : Configuration

Running partition tests on : iba€ezaldaz

Running enterprise tests on : iba€ezaldaz.local
Starting test: DNS
Test results for domain controllers:

DC: servidor.iba€ezaldaz.local
Domain: iba€ezaldaz.local


TEST: Forwarders/Root hints (Forw)
Error: Forwarders list has invalid forwarder:
80.58.61.250 (<name unavailable>)
Error: Forwarders list has invalid forwarder:
80.58.61.254 (<name unavailable>)
Error: Root hints list has invalid root hint server:
a.root-servers.net. (198.41.0.4)
Error: Root hints list has invalid root hint server:
b.root-servers.net. (128.9.0.107)
Error: Root hints list has invalid root hint server:
c.root-servers.net. (192.33.4.12)
Error: Root hints list has invalid root hint server:
d.root-servers.net. (128.8.10.90)
Error: Root hints list has invalid root hint server:
e.root-servers.net. (192.203.230.10)
Error: Root hints list has invalid root hint server:
f.root-servers.net. (192.5.5.241)
Error: Root hints list has invalid root hint server:
h.root-servers.net. (128.63.2.53)
Error: Root hints list has invalid root hint server:
i.root-servers.net. (192.36.148.17)
Error: Root hints list has invalid root hint server:
j.root-servers.net. (192.58.128.30)
Error: Root hints list has invalid root hint server:
k.root-servers.net. (193.0.14.129)
Error: Root hints list has invalid root hint server:
l.root-servers.net. (198.32.64.12)
Error: Root hints list has invalid root hint server:
m.root-servers.net. (202.12.27.33)

TEST: Delegations (Del)
Error: Failed to enumerate the records at the zone
root on the server servidor.iba€ezaldaz.local

Summary of test results for DNS servers used by the above
domain controllers:

DNS server: 128.63.2.53 (h.root-servers.net.)
1 test failure on this DNS server
This is not a valid DNS server. PTR record query for
the 1.0.0.127.in-addr.arpa. failed on the DNS server 128.63.2.53

DNS server: 128.8.10.90 (d.root-servers.net.)
1 test failure on this DNS server
This is not a valid DNS server. PTR record query for
the 1.0.0.127.in-addr.arpa. failed on the DNS server 128.8.10.90

DNS server: 128.9.0.107 (b.root-servers.net.)
1 test failure on this DNS server
This is not a valid DNS server. PTR record query for
the 1.0.0.127.in-addr.arpa. failed on the DNS server 128.9.0.107

DNS server: 192.203.230.10 (e.root-servers.net.)
1 test failure on this DNS server
This is not a valid DNS server. PTR record query for
the 1.0.0.127.in-addr.arpa. failed on the DNS server 192.203.230.10

DNS server: 192.33.4.12 (c.root-servers.net.)
1 test failure on this DNS server
This is not a valid DNS server. PTR record query for
the 1.0.0.127.in-addr.arpa. failed on the DNS server 192.33.4.12

DNS server: 192.36.148.17 (i.root-servers.net.)
1 test failure on this DNS server
This is not a valid DNS server. PTR record query for
the 1.0.0.127.in-addr.arpa. failed on the DNS server 192.36.148.17

DNS server: 192.5.5.241 (f.root-servers.net.)
1 test failure on this DNS server
This is not a valid DNS server. PTR record query for
the 1.0.0.127.in-addr.arpa. failed on the DNS server 192.5.5.241

DNS server: 192.58.128.30 (j.root-servers.net.)
1 test failure on this DNS server
This is not a valid DNS server. PTR record query for
the 1.0.0.127.in-addr.arpa. failed on the DNS server 192.58.128.30

DNS server: 193.0.14.129 (k.root-servers.net.)
1 test failure on this DNS server
This is not a valid DNS server. PTR record query for
the 1.0.0.127.in-addr.arpa. failed on the DNS server 193.0.14.129

DNS server: 198.32.64.12 (l.root-servers.net.)
1 test failure on this DNS server
This is not a valid DNS server. PTR record query for
the 1.0.0.127.in-addr.arpa. failed on the DNS server 198.32.64.12

DNS server: 198.41.0.4 (a.root-servers.net.)
1 test failure on this DNS server
This is not a valid DNS server. PTR record query for
the 1.0.0.127.in-addr.arpa. failed on the DNS server 198.41.0.4

DNS server: 202.12.27.33 (m.root-servers.net.)
1 test failure on this DNS server
This is not a valid DNS server. PTR record query for
the 1.0.0.127.in-addr.arpa. failed on the DNS server 202.12.27.33

DNS server: 80.58.61.250 (<name unavailable>)
1 test failure on this DNS server
This is not a valid DNS server. PTR record query for
the 1.0.0.127.in-addr.arpa. failed on the DNS server 80.58.61.250

DNS server: 80.58.61.254 (<name unavailable>)
1 test failure on this DNS server
This is not a valid DNS server. PTR record query for
the 1.0.0.127.in-addr.arpa. failed on the DNS server 80.58.61.254

Summary of DNS test results:

Auth Basc Forw Del Dyn
RReg Ext

________________________________________________________________
Domain: iba€ezaldaz.local
servidor PASS PASS FAIL FAIL PASS
PASS n/a

. iba€ezaldaz.local failed test DNS

No quiero que siga pasando esto, así que como voy ha ir esta semana,
la idea era coger un system state y el cd de instalación del Windows
2003 Server R2, instalarlo en en el laboratorio restaurando el system
state, la misma configuración... y probar lo del renombrado de
dominios, pero si puedo solucionarle esto antes de realizar en el
cliente este renombrado o montarle de nuevo el domino (puesto que son
7 equipos en total y únicamente lo que utilizan del servidor son los
datos en la partición d: de cada usuario) me daría un poco de margen
muchas gracias y un saludo

Preguntas similare

Leer las respuestas

#6 inyakigil
23/02/2007 - 12:44 | Informe spam
muchas gracias Guillermo
he llamado a Microsoft para perdiles el hotfix, en breve lo tendré
disponible y lo probaré
lo de la tajeta de red, sí que está integrada, pero es una Marvell
Yukon Gigabit, como tiene una segunda tarjeta de red (no operativa)
probaré a configurar esa y haber que pasa, ya te comentaré, un saludo,
Iñaki.
Respuesta Responder a este mensaje
#7 inyakigil
02/03/2007 - 00:28 | Informe spam
hola Guillermo
La placa base que es Intel tenía dos tarjetas de red.
Le he dejado funcionando la otra y de momento todo ok
con respecto al dns, el hotfix que me mandó microsoft es para una
versión anterior
al service pack que tengo instalado, asi que de momento con el dns
sigo igual
este finde probaré lo del renombrado de dominio y si todo sale ok lo
llevaré a cabo
en el cliente. Si se te ocurre algo te agradeceria si me lo cuentas.un
saludo.iñaki
email Siga el debate Respuesta Responder a este mensaje
Ads by Google
Help Hacer una pregunta AnteriorRespuesta Tengo una respuesta
Search Busqueda sugerida