Amigos,

A ver si logro hacerme entender.

Tenia dos DC, "aparentemente" replicando correctamente entre ellos,
hasta que, luego de un golpe de tension electrica, uno de ellos quedo
obsoleto.

Bien, en principio, pude ver que todo seguia funcionando bien, hasta
que arme una nueva maquina cliente, y cuando quiero meterla en el
dominio, no puedo, el mensaje es el siguiente:

"No se puede conectar a un controlador de dominio en el dominio LOCAL

Asegurese de que el nombre del dominio este bien escrito"

Cuando voy a "Detalles", encuentro lo siguiente:

Es posible que el nombre de dominio "LOCAL" sea un nombre de dominio
NetBIOS. Si este es el caso, compruebe que el nombre de dominio está
registrado correctamente con WINS.

Si está seguro de que el nombre no es un nombre de dominio NetBIOS, la
siguiente información le ayuda a solucionar los problemas con su
configuración DNS:

Ocurrió un error cuando se consultó al DNS acerca del registro de
recursos de ubicación de servicio (SRV) usado para ubicar un
controlador de dominio para el dominio LOCAL.

El error fue: "No hay servidores DNS configurados para el sistema
local."
(código de error 0x0000267C DNS_ERROR_NO_DNS_SERVERS)

La solicitud era para el registro SRV para _ldap._tcp.dc._msdcs.LOCAL

Para obtener más información, haga clic en Ayuda.

Todas las demas funciones del Servidor (ERP, Impresion, DHCP, FTP,
Archivos) estan funcionando correctamente, incluso el logueo de los
usuarios (32 en total) es totalmente "normal".

Alguna idea?

Desde ya muyyyyy agradecido por su tiempo y ayuda.

slds

Según lo que pones , yo estoy casi seguro estoy que es un problema de DNS.
Revisa tu dns y dhcp a ver si funcionan correctamente.
Mira a ver si lo equipos restantes no tardan mucho el logearse.

No tardan mucho en loguearse, al contrario esta mas rapido que antes, peor si tarda y pide user y pass cuando intento ver un archivo desde otra maquina.

Seguramente sea problema de DNS, no creo de DHCP, pero el punto es QUE PROBLEMA....

graicas amigo.

Pongo un reporte hecho con RELPMON

Active Directory Replication Monitor
Printed on 17/10/2006 09:24:07 a.m.
This report was generated on data from the server: SERV

***************************************************************************
SERV Data
***************************************************************************

This server currently has writable copies of the following directory partitions:
---------------------------------------------------------------------------
DC=ranieri,DC=local
CN=Configuration,DC=ranieri,DC=local
CN=Schema,CN=Configuration,DC=ranieri,DC=local
DC=DomainDnsZones,DC=ranieri,DC=local
DC=ForestDnsZones,DC=ranieri,DC=local

Current NTDS Connection Objects
-------------------------------

Current Direct Replication Partner Status
-----------------------------------------

Directory Partition: DC=ranieri,DC=local

Directory Partition: CN=Configuration,DC=ranieri,DC=local

Directory Partition: CN=Schema,CN=Configuration,DC=ranieri,DC=local

Directory Partition: DC=DomainDnsZones,DC=ranieri,DC=local

Directory Partition: DC=ForestDnsZones,DC=ranieri,DC=local

Current Transitive Replication Partner Status
---------------------------------------------

Directory Partition: DC=ranieri,DC=local

Partner Name: Default-First-Site\SERV
Partner GUID: 2F606CBB-DA6C-4E3E-BE24-6179D18351A6
USN: 336013

Partner Name: **DELETED SERVER #1
Partner GUID: 58AC89B1-5653-41C2-B55D-ABB5F45B1743
USN: 105542

Partner Name: **DELETED SERVER #2
Partner GUID: A0D19F77-1102-4A0E-84DF-73B0EF89DB60
USN: 5811448

Partner Name: **DELETED SERVER #3
Partner GUID: CFF59601-9B78-4066-A372-21E259264DC9
USN: 65313

Directory Partition: CN=Configuration,DC=ranieri,DC=local

Partner Name: Default-First-Site\SERV
Partner GUID: 2F606CBB-DA6C-4E3E-BE24-6179D18351A6
USN: 336013

Partner Name: **DELETED SERVER #1
Partner GUID: 58AC89B1-5653-41C2-B55D-ABB5F45B1743
USN: 105542

Partner Name: **DELETED SERVER #2
Partner GUID: A0D19F77-1102-4A0E-84DF-73B0EF89DB60
USN: 5811448

Partner Name: **DELETED SERVER #3
Partner GUID: CFF59601-9B78-4066-A372-21E259264DC9
USN: 65312

Directory Partition: CN=Schema,CN=Configuration,DC=ranieri,DC=local

Partner Name: Default-First-Site\SERV
Partner GUID: 2F606CBB-DA6C-4E3E-BE24-6179D18351A6
USN: 336013

Partner Name: **DELETED SERVER #1
Partner GUID: 58AC89B1-5653-41C2-B55D-ABB5F45B1743
USN: 105542

Partner Name: **DELETED SERVER #2
Partner GUID: A0D19F77-1102-4A0E-84DF-73B0EF89DB60
USN: 5811448

Partner Name: **DELETED SERVER #3
Partner GUID: CFF59601-9B78-4066-A372-21E259264DC9
USN: 65296

Directory Partition: DC=DomainDnsZones,DC=ranieri,DC=local

Partner Name: Default-First-Site\SERV
Partner GUID: 2F606CBB-DA6C-4E3E-BE24-6179D18351A6
USN: 336013

Directory Partition: DC=ForestDnsZones,DC=ranieri,DC=local

Partner Name: Default-First-Site\SERV
Partner GUID: 2F606CBB-DA6C-4E3E-BE24-6179D18351A6
USN: 336013

Current Group Policy Object Status
----------------------------------
Default Domain Policy
Group Policy Object GUID: {31B2F340-016D-11D2-945F-00C04FB984F9}
Group Policy Object Version in the DS: 65539
Group Policy Object Version in SYSVOL: ERROR

Default Domain Controllers Policy
Group Policy Object GUID: {6AC1786C-016F-11D2-945F-00C04fB984F9}
Group Policy Object Version in the DS: 46
Group Policy Object Version in SYSVOL: ERROR


The server SERV knows about the following FSMO roles:
--------------------------------------------------------------------------
Schema FSMO: Default-First-Site\SERV
Domain Naming FSMO: Default-First-Site\SERV
Infrastructure FSMO: Default-First-Site\SERV
Primary Domain Controller FSMO: Default-First-Site\SERV
RID Pool FSMO: Default-First-Site\SERV

Performance Statistics at Time of Report
----------------------------------------

Configuration (Registry)
NOTE: an empty value indicates that Windows 2000 will use the internal default
NOTE: all empty values may indicate insufficient permission to retrieve this information from the domain controller
------------------------

DSA
---

Days per Database Phantom Scan:
Initialize MAPI interface:
Enforce LIST_OBJECTS rights:
DSA Heuristics:
Max Threads (ExDS+NSP+DRA):
DSA Database file: C:\WINDOWS\NTDS\ntds.dit
DSA Working Directory: C:\WINDOWS\NTDS
Critical Object Installation:
DS Drive Mappings:
DSA Previous Restore Count:

REPLICATION
-----------

Replicator notify pause after modify (secs):
Replicator notify pause between DSAs (secs):
Replicator intra site packet size (objects):
Replicator intra site packet size (bytes):
Replicator inter site packet size (objects):
Replicator inter site packet size (bytes):
Replicator maximum concurrent read threads:
Replicator operation backlog limit:
Replicator thread op priority threshold:
Replicator intra site RPC handle lifetime (secs):
Replicator inter site RPC handle lifetime (secs):
Replicator RPC handle expiry check interval (secs):

LDAP
----

Max objects in LDAP Search (Admin Limit):
Max concurrent LDAP connections allowed:
Max time allowed for an LDAP Search:
Max concurrent LDAP searches allowed:
Max concurrent threads per LDAP connection allowed:
Minimum idle seconds before potential \ timeout of LDAP connection (non-authenticated client):
Minimum idle seconds before potential \ timeout of LDAP connection (authenticated client):

Database
--------

Database backup path: C:\WINDOWS\NTDS\dsadata.bak
Database backup interval (hours):
Database log files path: C:\WINDOWS\NTDS
Database logging/recovery: ON
Hierarchy Table Recalculation interval (minutes): 720
Database restored from backup:
Pending object ownership conversions:
EDB max buffers:
EDB max log buffers:
EDB log buffer flush threshold:
EDB buffer flush start:
EDB buffer flush stop:
EDB max ver pages (increment over the minimum:
Circular Logging:
Server Functionality:
TCP/IP Port:
Restore from disk backup:
Performance Counter Version: 17

KCC
---

Repl topology update delay (secs):
Repl topology update period (secs):
KCC site generator fail-over (minutes):
KCC site generator renewal interval (minutes):
KCC site generator renewal interval (minutes):
CriticalLinkFailuresAllowed:
MaxFailureTimeForCriticalLink (sec):
NonCriticalLinkFailuresAllowed:
MaxFailureTimeForNonCriticalLink (sec):
IntersiteFailuresAllowed:
MaxFailureTimeForIntersiteLink (sec):
KCC connection failures:
IntersiteFailuresAllowed:
IntersiteFailuresAllowed:

***************************************************************************
Enterprise Data
***************************************************************************

Globally Unique Identifiers (GUIDs) for each domain controller in the enterprise
NOTE: the absence of a GUID means that the server has been demoted.
--------------------------------------------------------------------------------

Site Name: Default-First-Site
---------------------------------------
Site Options :
Site Topology Generator: CN=NTDS Settings,CN=SERV,CN=Servers,CN=Default-First-Site,CN=Sites,CN=Configuration,DC=ranieri,DC=local
Site Topology Renewal :
Site Topology Failover :

SERV
Server GUID (used for DNS) : 72017BC8-B0A8-4B82-8CE5-582838DB9B52
Replication Database GUID (used to identify partner in replication): 2F606CBB-DA6C-4E3E-BE24-6179D18351A6
DSA Options : NTDSDSA_OPT_IS_GC
DSA Computer Path : CN=SERV,OU=Domain Controllers,DC=ranieri,DC=local
DSA Schema Location : CN=Schema,CN=Configuration,DC=ranieri,DC=local
DSA Mail Address :
DSA DNS Host Name : serv.ranieri.local
DSA BridgeHead Transports :



Site Links and Site Link Bridges
-----------------------------------------------------

Site Links
----------

DEFAULTIPSITELINK
Link Type: : IP
Distinguished Name : CN=DEFAULTIPSITELINK,CN=IP,CN=Inter-Site Transports,CN=Sites,CN=Configuration,DC=ranieri,DC=local
Replication Interval : 180
Cost : 100
Options :
Site List :
Default-First-Site

Site Link Bridges
------------------

Active Directory Replication Monitor determined that no Site Link Bridges are present in the Directory.
Inter-Site Transports
---------------------

IP
Options :
DLL Name : ismip.dll
Address Type: dNSHostName

SMTP
Options : NTDSTRANSPORT_OPT_IGNORE_SCHEDULES
DLL Name : ismsmtp.dll
Address Type: mailAddress

Subnets
-------
Active Directory Replication Monitor determined that no Subnets are present in the Directory.
Active Directory Configuration Data
-----------------------------------
Stay of Execution for Servers: 0
SPN Mappings : host=alerter,appmgmt,cisvc,clipsrv,browser,dhcp,dnscache,replicator,eventlog,eve
ntsystem,policyagent,oakley,dmserver,dns,mcsvc,fax,msiserver,ias,messenger,netlo
gon,netman,netdde,netddedsm,nmagent,plugplay,protectedstorage,rasman,rpclocator,
rpc,rpcss,remoteaccess,rsvp,samss,scardsvr,scesrv,seclogon,scm,dcom,cifs,spooler
,snmp,schedule,tapisrv,trksvr,trkwks,ups,time,wins,www,http,w3svc,iisadmin

Amigos, tema solucionado.

315457 How to Rebuild SYSVOL and Its Content in a Domain

http://support.microsoft.com/?id=315457

Troubleshooting Missing SYSVOL and NETLOGON Shares on Windows 2000 Domain
Controllers (Q257338)

http://support.microsoft.com/search/previe...b;en-us;Q257338

Gracias por su tiempo y ayuda.

slds