DFS Replication issue Event ID 5002
I have a 2008 R2 Domain, two productions sites, and 4 domain controllers (all GC's).
I have migrated recently from 2003 R2 domain and forest levels. The problem only started today and DFS has been working fine.
Important info is the DFS was setup originally in Windows 2003 and hosted on two W2K3 name servers - Properties of the namespace - Domain (Windows 2000 Server mode).
Prior to domain/forest functional levels being raised I slowly introduced new 2008 R2 files servers running DFS and decommisioned the old 2003 root servers. I have not migrated the namespace and still reads Domain (windows 2000 Server mode). This is a separate project!
Today I have been experiencing issues with replication and getting the event ID 5002
--------------------------
The DFS Replication service encountered an error communicating with partner <servername> for replication group <DFS namespace\folder>
Partner DNS address: Servername.domain.local
Optional data if available:
Partner WINS Address: Server Name
Partner IP Address: *.*.*.*
The service will retry the connection periodically.
--------------------------
I have worked through this link below and all looks ok - http://blogs.technet.com/b/josebda/archive/2009/07/15/five-ways-to-check-your-dfs-namespaces-dfs-n-configuration-with-the-dfsdiag-exe-tool.aspx
DCDIAG /v looks ok on all DC's no errors.
DCDIAG /TEST:DNS looks fine.
IPV6 is diabled on LAN - adding the regedit for 'DisabledComponents'
I have created a TEST folder and setup a new replication but this again reports the same event errors.
I had a feeling this would be WINS so confirmed the new DC's WINS working ok and checked DNS records had been updated with the new WINS servers.
IPconfig /displaydns looks fine on both file servers but replication is just not happening. Worked fine yesterday and there have been no changes.
Can anyone suggest anything here?
Tempted to migrate - http://technet.microsoft.com/en-us/library/cc753875.aspx but this should work and I don't want to carry the problem across! Plus it's a fair amount of work/downtime!
Thanks for looking.
I have migrated recently from 2003 R2 domain and forest levels. The problem only started today and DFS has been working fine.
Important info is the DFS was setup originally in Windows 2003 and hosted on two W2K3 name servers - Properties of the namespace - Domain (Windows 2000 Server mode).
Prior to domain/forest functional levels being raised I slowly introduced new 2008 R2 files servers running DFS and decommisioned the old 2003 root servers. I have not migrated the namespace and still reads Domain (windows 2000 Server mode). This is a separate project!
Today I have been experiencing issues with replication and getting the event ID 5002
--------------------------
The DFS Replication service encountered an error communicating with partner <servername> for replication group <DFS namespace\folder>
Partner DNS address: Servername.domain.local
Optional data if available:
Partner WINS Address: Server Name
Partner IP Address: *.*.*.*
The service will retry the connection periodically.
--------------------------
I have worked through this link below and all looks ok - http://blogs.technet.com/b/josebda/archive/2009/07/15/five-ways-to-check-your-dfs-namespaces-dfs-n-configuration-with-the-dfsdiag-exe-tool.aspx
DCDIAG /v looks ok on all DC's no errors.
DCDIAG /TEST:DNS looks fine.
IPV6 is diabled on LAN - adding the regedit for 'DisabledComponents'
I have created a TEST folder and setup a new replication but this again reports the same event errors.
I had a feeling this would be WINS so confirmed the new DC's WINS working ok and checked DNS records had been updated with the new WINS servers.
IPconfig /displaydns looks fine on both file servers but replication is just not happening. Worked fine yesterday and there have been no changes.
Can anyone suggest anything here?
Tempted to migrate - http://technet.microsoft.com/en-us/library/cc753875.aspx but this should work and I don't want to carry the problem across! Plus it's a fair amount of work/downtime!
Thanks for looking.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.