Socio, SERVIDOR es el nombre real que tiene el server?? Si es así, es un
nombre un poco conflictivo y nunca se aocnseja poner nombres que puedan
acarrear problemas (como por ejemplo, server, servidor, fileserver, etc...).
No obstante, haz un ipconfig /registerdns y reinicia el servicio de netlogon
(el servicio, no el servidor, si no no sirve), luego espera unos 10 minutos
y ponnos de nuevo el resultado del netdiag
--
Salu2!!
Javier Inglés
https://mvp.support.microsoft.com/pr...9-2CB5567431B0
MS MVP, Windows Server-Directory Services
jingles***NOSPAMmvps.org
"Angel Zapata" <angel.zapata***gruposh.es> escribió en el mensaje
news:eTqMfTPtIHA.5832***TK2MSFTNGP02.phx.gbl...
> Hola Javier,
>
> gracias por tu pronta respuesta,
>
> adjunto te envío el resultado en txt de dcdiag y netdiag, encuentro
> algunos errores, pero me reconozco incapaz de encontrar el porque de
> cada uno.
>
> Por favor, echame una mano, gracias.
>
> Un saludo
> Angel Zapata
>
> Javier Inglés [MS MVP] escribió:
>> Has pasado ya un dcdiag y netdiag al primer DC?
>>
>
--------------------------------------------------------------------------------
>
> ...................................
>
> Computer Name: SERVIDOR
> DNS Host Name: servidor.SiglhogarXXI.local
> System info : Microsoft Windows Server 2003 R2 (Build 3790)
> Processor : EM64T Family 6 Model 15 Stepping 11, GenuineIntel
> List of installed hotfixes :
> KB924667-v2
> KB925398_WMP64
> KB925902
> KB927891
> KB929123
> KB930178
> KB932168
> KB932596
> KB933729
> KB935839
> KB935840
> KB936021
> KB936357
> KB936782
> KB938127
> KB938127-IE7
> KB941202
> KB941568
> KB941569
> KB941644
> KB941672
> KB941693
> KB942763
> KB943055
> KB943460
> KB943484
> KB943485
> KB944338
> KB944533-IE7
> KB944653
> KB945553
> KB946026
> KB947864
> KB947864-IE7
> KB948496
> KB948590
> KB948881
> Q147222
>
>
> Netcard queries test . . . . . . . : Passed
>
>
>
> Per interface results:
>
> Adapter : Servidor/VLAN1
>
> Netcard queries test . . . : Passed
>
> Host Name. . . . . . . . . : servidor
> IP Address . . . . . . . . : 192.168.0.1
> Subnet Mask. . . . . . . . : 255.255.255.0
> Default Gateway. . . . . . : 192.168.0.100
> Dns Servers. . . . . . . . : 192.168.0.1
>
>
> AutoConfiguration results. . . . . . : Passed
>
> Default gateway test . . . : Passed
>
> NetBT name test. . . . . . : Passed
> [WARNING] At least one of the <00> 'WorkStation Service', <03>
> 'Messenger Service', <20> 'WINS' names is missing.
> No remote names have been found.
>
> 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_{DE69D172-5593-4520-B5AE-7D40E8589799}
> 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
> Service', <03> 'Messenger Service', <20> 'WINS' names defined.
>
>
> Winsock test . . . . . . . . . . . : Passed
>
>
> DNS test . . . . . . . . . . . . . : Failed
> [WARNING] Cannot find a primary authoritative DNS server for the
> name
> 'servidor.SiglhogarXXI.local.'. [RCODE_SERVER_FAILURE]
> The name 'servidor.SiglhogarXXI.local.' may not be registered
> in DNS.
> [WARNING] The DNS entries for this DC are not registered correctly on
> DNS server '192.168.0.1'. Please wait for 30 minutes for DNS server
> replication.
> [FATAL] No DNS servers have the DNS records for this DC registered.
>
>
> Redir and Browser test . . . . . . : Passed
> List of NetBt transports currently bound to the Redir
> NetBT_Tcpip_{DE69D172-5593-4520-B5AE-7D40E8589799}
> The redir is bound to 1 NetBt transport.
>
> List of NetBt transports currently bound to the browser
> NetBT_Tcpip_{DE69D172-5593-4520-B5AE-7D40E8589799}
> 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
>
--------------------------------------------------------------------------------
>
> Domain Controller Diagnosis
>
> Performing initial setup:
> Done gathering initial info.
>
> Doing initial required tests
>
> Testing server: Default-First-Site\SERVIDOR
> Starting test: Connectivity
> The host
> a296c1cf-229d-4843-92c9-5e2173cef1ed._msdcs.SiglhogarXXI.local could not
> be resolved to an
> IP address. Check the DNS server, DHCP, server name, etc
> Although the Guid DNS name
> (a296c1cf-229d-4843-92c9-5e2173cef1ed._msdcs.SiglhogarXXI.local)
> couldn't be resolved, the server name
> (servidor.SiglhogarXXI.local)
> resolved to the IP address (192.168.0.1) and was pingable. Check
> that
> the IP address is registered correctly with the DNS server.
> ......................... SERVIDOR failed test Connectivity
>
> Doing primary tests
>
> Testing server: Default-First-Site\SERVIDOR
> Skipping all tests, because server SERVIDOR is
> not responding to directory service requests
>
> Running partition tests on : TAPI3Directory
> Starting test: CrossRefValidation
> ......................... TAPI3Directory passed test
> CrossRefValidation
> Starting test: CheckSDRefDom
> ......................... TAPI3Directory passed test CheckSDRefDom
>
> 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 : SiglhogarXXI
> Starting test: CrossRefValidation
> ......................... SiglhogarXXI passed test
> CrossRefValidation
> Starting test: CheckSDRefDom
> ......................... SiglhogarXXI passed test CheckSDRefDom
>
> Running enterprise tests on : SiglhogarXXI.local
> Starting test: Intersite
> ......................... SiglhogarXXI.local passed test Intersite
> Starting test: FsmoCheck
> ......................... SiglhogarXXI.local passed test FsmoCheck
>