Re: SysVol and NetLogon Share
- From: "Chris Malone" <persillade@xxxxxxxxxxx>
- Date: 3 May 2006 09:45:23 -0700
Check the following items:
1. Check the "Access this Computer from the Network" right in
default DC policy.
Add the Everyone group and "Enterprise Domain Controllers" if
needed.
2. Check that the connection objects for each DC are correct in AD
Sites/Services. Build
new connection objects if needed by triggering the KCC with the
"Check Replication
Topology" option.
3. Check that AD replication is successful with REPADMIN (FRS is
dependent upon AD
replication).
4. Ping all DCs that should be involved in FRS replication by FQDN.
5. From a command prompt, run \\<computername>\admin$\ntfrs\jet to
determine
whether the replica partner has an NTFRS.JDB database file.
6. If this is the only DC in the domain, you may want to try doing a D4
(auth
restore) of SYSVOL:
315457 How to Rebuild SYSVOL and Its Content in a Domain
http://support.microsoft.com/?id=315457
7. Confirm that all computers in the replica set are listed under SET:
DOMAIN
SYSTEMVOLUME (SYSVOL SHARE) when running a NTFRSUTL DS
<computername> command.
8. Check disk space on replica partners.
9. If the DC was recently promoted, check the ntfrsapi.log in
\winnt\debug.
This log can be used to identify reasons why the DC did not
initially share
Netlogon and SYSVOL.
.
- Follow-Ups:
- Re: SysVol and NetLogon Share
- From: Jorge Silva
- Re: SysVol and NetLogon Share
- References:
- Re: SysVol and NetLogon Share
- From: Jorge de Almeida Pinto [MVP]
- Re: SysVol and NetLogon Share
- Prev by Date: Re: DNS Nightmare - Can't create forward zone
- Next by Date: Re: AD Upgrade Question
- Previous by thread: Re: SysVol and NetLogon Share
- Next by thread: Re: SysVol and NetLogon Share
- Index(es):
Relevant Pages
|