replication problem

  • Thread starter Thread starter Ahmed Nour
  • Start date Start date
A

Ahmed Nour

I have WIn2k AS Domain ,I have two DCs one of them works
also as a global catalog,I think that my DC (not a global
catalog server)has a replication problem with the Global
Catalog server (i.e. folders like sysvol and netlogon are
not shared and also the netlogon folder is not created on
the DC server and now I have some logged errors forfile
replication servers.
what Iam Asking about is what could I do to check the
replication is correct and how to repair it if there is a
problem.

Iam thinking about demoting the Dc to a standalone server
and then promote it again but Iam afraid because it has
both exchange and Isa server installed on the same server

any help will be much appreciated

Best Regards:-
Ahmed Nour
...


..
 
Ahmed Nour says...
I have WIn2k AS Domain ,I have two DCs one of them works
also as a global catalog,I think that my DC (not a global
catalog server)has a replication problem with the Global
Catalog server (i.e. folders like sysvol and netlogon are
not shared and also the netlogon folder is not created on
the DC server and now I have some logged errors forfile
replication servers.
what Iam Asking about is what could I do to check the
replication is correct and how to repair it if there is a
problem.

Iam thinking about demoting the Dc to a standalone server
and then promote it again but Iam afraid because it has
both exchange and Isa server installed on the same server

any help will be much appreciated

Best Regards:-
Ahmed Nour
..
Click to expand...
Hello Ahmed,

since I don't know what errors you receive, I suggest the following steps:
1. Look up your events at www.eventid.net and read the suggestions there
2. run netdiag and dcdiag out of the support tools on both dcs. Redirect the
output to a logfile, and search the logfiles for "Fail". Try to fix those
points or provide the information what's failing in here.

And look at your dns-infrastructure. Point both DCs to the same DNS-Server,
make sure the zone exists with it's subzones _msdcs, _tcp, _udp and _sites,
make sure that the server registered themselves in dns (if not look if you
forgot to enable dynamic dns on the properties of the zone, then type "net stop
netlogon" and "net start netlogon" on both dcs).

And make sure you have a valid domain name, not a single label name. A dns name
of "company" would be BAD, a dns name of "company.local" or anything like that
is good (you need the "." in between).

Gruesse - Sincerely,

Ulf B. Simon-Weidner
 
Back
Top