El servidor DNS encontró un error crítico en Active Directory. Compruebe que Active Directory está funcionado correctamente. La información de depuración de error extendida (puede estar vacía) es "". Los datos del evento contienen el error.
hola "andres nope" como estas,
comprueba el event id desde,
https://technet.microsoft.com/en-us/library/cc735674(v=ws.10).aspx
aplica:
1.logon domain controller enterprise admin account (prefer logon replication partner of problematic dc)
2.run ntdsutil in domain controller
3.run "domain management" command in ntdsutil
4.run "connections" command , connect local server "connect server localdcname" command. (replace localdcname local dc's hostname)
5.hit q , enter.
6.run following command , see problematic server not listed in output, although should since has dns server installed.
if replicating dns zone forest run "list nc replicas dc=forestdnszones,dc=domain,dc=com"
if replicating dns zone domain run "list nc replicas dc=domaindnszones,dc=domain,dc=com"
7.before continuing next step make sure there no object under "lostandfoundconfig" (serves container lost forestwide objects) container. can check adsiedit.msc under configuration partition. if there object first check "lastknownparent" attribute , if decide if not orphaned object move location. if decide orphaned object delete it.
8.now add problematic domain controller dns server install nc's replicating. running following commands.
for forest wide dns partition:
"add nc replica dc=forestdnszones,dc=domain,dc=com problemdcname.domain.com" (problematic dc name must in full dns name format). domain wide dns partition:
"add nc replica dc=domaindnszones,dc=domain,dc=com problemdcname.domain.com" (problematic dc name must in full dns name format).
9.force replication on problematic dc partner (where follow steps 1 8).
si es rodc ver: https://support.microsoft.com/en-us/kb/969488
espero sea de ayuda. saludos.
Windows Server > Administración de servidor
Comments
Post a Comment