Re: Windows 2000 Server Replication Problem
- From: "Paul Bergson [MVP-DS]" <pbergson@xxxxxxxxxxxxxxxxx>
- Date: Mon, 18 Feb 2008 07:50:48 -0600
Just because you can ping a remote site doesn't mean that you can
communicate with it on other ports. You should run portqry or portqryui and
check to see if the AD ports are open.
Read the following article I have on this and it has steps to follow for
portqryui (Firewall Ports Needed for Replication)
http://www.pbbergs.com/windows/articles.htm
Do you have remote sites defined for your dc's? Are IP addresses defined
for these sites? The KCC is having troubles per the Event log errors you
describe.
Best Practices for Sites and Services
http://technet2.microsoft.com/windowsserver/en/library/86417143-92b6-431b-8439-91f456e921dd1033.mspx?mfr=true
When someone has troubles and unclear as to why I usually suggest the
following:
Run diagnostics against your Active Directory domain.
If you don't have the support tools installed, install them from your server
install disk.
d:\support\tools\setup.exe
Run dcdiag, netdiag and repadmin in verbose mode.
-> DCDIAG /V /C /D /E /s:yourdcname > c:\dcdiag.log
-> netdiag.exe /v > c:\netdiag.log (On each dc)
-> repadmin.exe /showrepl dc* /verbose /all /intersite > c:\repl.txt
-> dnslint /ad /s "ip address of your dc"
**Note: Using the /E switch in dcdiag will run diagnostics against ALL dc's
in the forest. If you have significant numbers of DC's this test could
generate significant detail and take a long time. You also want to take
into account slow links to dc's will also add to the testing time.
If you download a gui script I wrote it should be simple to set and run
(DCDiag and NetDiag). It also has the option to run individual tests
without having to learn all the switch options. The details will be output
in notepad text files that pop up automagically.
The script is located on my website at
http://www.pbbergs.com/windows/downloads.htm
Just select both dcdiag and netdiag make sure verbose is set. (Leave the
default settings for dcdiag as set when selected)
When complete search for fail, error and warning messages.
Description and download for dnslint
http://support.microsoft.com/kb/321045
--
Paul Bergson
MVP - Directory Services
MCT, MCSE, MCSA, Security+, BS CSci
2003, 2000 (Early Achiever), NT
http://www.pbbergs.com
Please no e-mails, any questions should be posted in the NewsGroup
This posting is provided "AS IS" with no warranties, and confers no rights.
"windowsfirst" <windowsfirst@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:3DBEB87E-E64B-4BB1-BF7E-5AAEEBA2D508@xxxxxxxxxxxxxxxx
Hi,
I am having windows server 2000 Replication problem as follows
Hq server and Two branch offices
Both brach offices are not replication to my hq server
In my Brach office servers every 15 min i am getting event id 1311 and
1566
I am able to ping from and to all the servers using FQDN names
I ran dcdiag on my hq server i am getting the following error
[1] FRS can not correctly resolve the DNS name
SOUTHSRV01.test.com from this computer.
[2] FRS is not running on
SOUTHSRV01.test.com.
[3] The topology information in the Active
Directory for this replica has not yet replicated
to all the Domain Controllers.
[1] FRS can not correctly resolve the DNS name
NORTHSVR01.test.com from this computer.
[2] FRS is not running on
NORTHSVR01.test.com.
[3] The topology information in the Active
Directory for this replica has not yet replicated
to all the Domain Controllers.
Servers SOUTHSRV01.test.com,NORTHSVR01.test.com are my brach offices when
i
checked all the DNS setting and FQDN seems to be fine
I really need expert help on this and what otherthings i can look for
problem root cause
Thanks for your help
.
- Follow-Ups:
- Re: Windows 2000 Server Replication Problem
- From: windowsfirst
- Re: Windows 2000 Server Replication Problem
- References:
- Windows 2000 Server Replication Problem
- From: windowsfirst
- Windows 2000 Server Replication Problem
- Prev by Date: Re: Migrating active directory and exchange
- Next by Date: Re: Trying to create mandatory profiles....
- Previous by thread: Windows 2000 Server Replication Problem
- Next by thread: Re: Windows 2000 Server Replication Problem
- Index(es):
Relevant Pages
|
Loading
