IT Dept said:
Please HELP!
We have win2k domain with win2k dc and win2k3 dc
replication between them doesn;t work!
What specifically do you see? Just problems with SysVol?
(That's not actually AD replication but is related to it by
using a similar topology -- Sysvol is replicated by the FRS)
Usually it is a DNS problem, assuming you have basic
network connectivity (which you seem to have).
Pay special attention to DCDiag below....
All other thing is seam to work fine: users logins, dns make resolution dhcp
works too
Usually you will have (some) authentication problems
too -- so this implies that only one (or a few) of your DCs
are misconfigured (likely for DNS.)
I put some files on sysvol and they didn;t copy to another dc
And any policy from domain doesn;t aplly at all to users computers
Check these:
DNS for AD
1) Dynamic for the zone supporting AD
2) All internal DNS clients NIC\IP properties must specify SOLELY
that internal, dynamic DNS server (set.)
3) DCs and even DNS servers are DNS clients too -- see #2
4) If you have more than one Domain, every DNS server must
be able to resolve ALL domains (either directly or indirectly)
netdiag /fix
....or maybe:
dcdiag /fix
(Win2003 can do this from Support tools):
nltest /dsregdns /server
C-ServerNameGoesHere
http://support.microsoft.com/kb/q260371/
Ensure that DNS zones/domains are fully replicated to all DNS
servers for that (internal) zone/domain.
Also useful may be running DCDiag on each DC, sending the
output to a text file, and searching for FAIL, ERROR, WARN.
Single Label domain zone names are a problem Google:
[ "SINGLE LABEL" domain names DNS 2000 | 2003 microsoft: ]
