sysvol folder on bdc

[junaid]

hi friends
i have two windows 2000 domain controllers running in
my windows 2000 domain.I promoted one more win2k member to
win2k domain controller as another bdc in my existing
domain.i cannot see my sysvol folder shared in my new
win2k bdc domain controller.
when i go to
c:\WINNT\SYSVOL\SYSVOL.
IT IS NOT SHARED.
there are no policies in it.nothing
i doubt my win2k domain controllers are not replicating.
need your help

junaid

 

[Guest]

On a DC which has just been introduced into the domain, it generally takes a
while before the SYSVOL is initialized. First your AD Objects (the replica
sets) would have to be replicated before FRS can initialize the SYSVOL

Is the AD Replication working good. If you create a dummy user on your PDC,
does it get replicated over to your New DC?

The FRS Event Viewer is pretty descriptive and does a good of letting you
know the current status. So check that out.

Check the status of the FRS Service.

See how good name resoltution for this DC is. See the EventIDs on the other
DCs is you get anything about them being unable to reach the New DC

ps: all of what I sais above doesnt have any logical order. But this is most
of the stuff I would try initially

 

[Herb Martin]

hi friends
i have two windows 2000 domain controllers running in
my windows 2000 domain.I promoted one more win2k member to
win2k domain controller as another bdc in my existing
domain.

DC, not BDC -- only NT has BDCs and they do not have SysVol.

i cannot see my sysvol folder shared in my new
win2k bdc domain controller.

Win2000+ DCs should all have SysVol.

when i go to
c:\WINNT\SYSVOL\SYSVOL.
IT IS NOT SHARED.
there are no policies in it.nothing
i doubt my win2k domain controllers are not replicating.
need your help

Is it listed in the DNS zone where you other DCs are registered,
especially in the _underscore subdomains, like _MSDSS or
_Sites.

Are there firewalls between the DC and the others -- you must
upon the File Replication Service (FRS) ports if so.

Is the AD replicating? If you look in AD Sites and Services
(and connect to this DC) do you see you AD objects?

Run DCDiag on ALL DCs and send the output to a file --
search the file for FAIL, WARN, ERROR and fix or
report those problems.

Most AD replication issues are DNS-based but FRS and
Sysvol are occasionally due to firefall filters or something
else.

DNS considerations:

1) Dynamic for the zone supporting AD
2) All internal DNS client NIC\IP properties must specify SOLELY
that internal, dynamic DNS server (set.)
3) DCs and even DNS servers are DNS clients too -- see #2

Restart NetLogon on any DC if you change any of the above that
affects a DC.

Make sure DNS is replicating to ALL DNS servers for the zone
also.