DFS Replication only occuring one direction

I have a two servers setup for DFS replication. Both systems are running Windows 2003 R2 SP2. I'm using a AD DFS scheme.

If I copy files directly to the share on server 1, then these files are replicated to server 2. Like wise if I delete files from server 1 then they are deleted from server 2. However the reverse is not true. If I copy or delete files on server 1 then these changes are not being reflected on server 1.

Can someone help me get things setup where they work the same in either direction? I've confirmed in the Replication settings that both systems have replication enabled, and each system is setup to replicate to each other (full mesh).
LVL 1
richard_westAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

stronglineCommented:
any FRS event errors on both sides?
double check your DNS settings for both servers. Is the AD replication ok both directions?
0
richard_westAuthor Commented:
I get the following errors on Server 1 periodically, even though Server 2 is up and remains available (but servers on on the same LAN only a few feet apart also so long distance connection issues are not applicable):

The DFS Replication service failed to communicate with partner SERVER2 for replication group mydomian.net\public\dp\programs. This error can occur if the host is unreachable, or if the DFS Replication service is not running on the server.
 
Partner DNS Address: server2.mydomain.net
 
Optional data if available:
Partner WINS Address: SERVER2
Partner IP Address: 10.0.1.20
 
The service will retry the connection periodically.
 
Additional Information:
Error: 1722 (The RPC server is unavailable.)
Connection ID: 305381FF-33F0-4D9C-A6CF-DEA40B21782D
Replication Group ID: 55F1BF27-A5F5-45AC-8CBD-FDBADCCD2D91

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
0
richard_westAuthor Commented:
I see the following message in the event viewer on Server 2:

The DFS Replication service is stopping communication with partner SERVER1 for replication group mydomian.net\public\dp\programs due to an error. The service will retry the connection periodically.
 
Additional Information:
Error: 9033 (The request was cancelled by a shutdown)
Connection ID: 2B7C214B-575D-4385-A1DD-BE170C8C516C
Replication Group ID: 55F1BF27-A5F5-45AC-8CBD-FDBADCCD2D91

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.


-----

No system shutdown is scheduled, or is occurring on either system.
0
Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

richard_westAuthor Commented:
Can you eloaborate on what you mean by checking the AD replication in both directions?

If I look in the Windows Storage Server Management MMC, under DFS Management > Replication I see both servers listed under the Connections tab in the details panel. Both Servers have replication enabled.

I'm sure if this is what your asking about or not since this not not seem to be related to AD.
0
stronglineCommented:
repadmin /showreps on both DCs.
If ad replication both ways that should pretty much mean the underlying dns/network is ok.
Nevertheless, i will double check the DNS settings, SRV records, and port requirements.
http://support.microsoft.com/kb/832017

temporary disable AV, firewall, or such if you have any.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
richard_westAuthor Commented:
Turns out that the Windows Firewall was enable on one of the two systems (SERVER2)

This was preventing the replication from going out to SERVER1. I have made the proper changes to the firewall and everything looks good now.

I'm going to go ahead and award you the points since you were helpful.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2003

From novice to tech pro — start learning today.