Re: DFSR - 2003 R2. EventID 5012
- From: "Jorge de Almeida Pinto [MVP - DS]" <SubstituteThisWithMyFullNameSeparatedByDots@xxxxxxxxx>
- Date: Wed, 27 Sep 2006 21:14:54 +0200
check DNS settings on that DC and also check AD replication
--
Cheers,
(HOPEFULLY THIS INFORMATION HELPS YOU!)
# Jorge de Almeida Pinto # MVP Windows Server - Directory Services
BLOG (WEB-BASED)--> http://blogs.dirteam.com/blogs/jorge/default.aspx
BLOG (RSS-FEEDS)--> http://blogs.dirteam.com/blogs/jorge/rss.aspx
------------------------------------------------------------------------------------------
* This posting is provided "AS IS" with no warranties and confers no rights!
* Always test before implementing!
------------------------------------------------------------------------------------------
#################################################
#################################################
------------------------------------------------------------------------------------------
"Hayden" <Hayden@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:6CCD6707-9416-4FCF-8A25-D9E7421397FC@xxxxxxxxxxxxxxxx
I have 3 Windows 2003 R2 servers in my test environment. (A, B and C)
When a DFS replication group is created on A or B, it replicates to all
other servers (A,B and C) quickly showing up in DFS management (and file
replication starts quickly).
When a DFS replication group is created on C, it takes approximately 2
hours
for it to appear on A and B, and in the mean time displays this event ID.
----------------------------------------------------------------------------
The DFS Replication service failed to communicate with partner TestC for
replication group Test. The partner did not recognize the connection or
the
replication group configuration.
Partner DNS Address: TestC.domain.local
Optional data if available:
Partner WINS Address: TestC
Partner IP Address: 192.168.100.2
The service will retry the connection periodically.
Additional Information:
Error: 9026 (The connection is invalid)
Connection ID: 920C3D6C-489C-49FB-A590-9638011B3407
Replication Group ID: CAE30C5F-A2F0-42E3-B2FF-7688E72AE563
----------------------------------------------------------------------------
Once this error disapears, and the normal 5004 event ID's start appearing
the system replication takes place and works fine.
I'm really wondering why this would occur on just this server - and am
hesitant to roll out R2 DFS until I get this sorted out.
thankyou.
.
- Follow-Ups:
- Re: DFSR - 2003 R2. EventID 5012
- From: Hayden
- Re: DFSR - 2003 R2. EventID 5012
- Prev by Date: Re: ADMT
- Next by Date: Re: Primary Domain Controller (PDC) emulator cannot be contacted?
- Previous by thread: Remote Desktop Connection - Group Policy
- Next by thread: Re: DFSR - 2003 R2. EventID 5012
- Index(es):
Relevant Pages
|
