Event ID 5002 Source DFSR, Error Code 5 connecting to a 2003 R2 server from a Server 2012


  • We recently performed an in-place upgrade of a 2008 R2 file server to 2012. For the most part things went well, but we have been unable to replicate with our only 2003 R2 file server with DFSR (other replica partners are 2008, 2008 R2 and 2012). The 2003 server logs successful 5004 events indicating a successful inbound connection from the 2012 server, but the 2012 server logs a 5002 with an error code 5 (access is denied).

    I have checked the firewalls on both servers and the firewall in between and confirmed the two servers are communicating successfully. I completely reset the DFSR volume on the 2003 server (the 2012 server is our hub and is successfully replicating with four other servers), but the problem persists. I installed all the DFSR hotfixes for 2003 R2. Both servers are on the same AD domain and connected via a 10Mbps MPLS. 

    My best guess is that there is a permissions or rights setting causing the connection to be denied, but nothing has changed on the 2003 server recently, so perhaps there is a new security setting on 2012? 

    Wednesday, April 24, 2013 3:52 PM

All replies

  • Hi,

    Please check the folders/files in System Volume Information folder (a hidden folder) in the same volume of the DFS folder, and see if permissions are correct --- At least SYSTEM should have full control permission on all folders and files. In order to check permissions, you will need to take ownership and give your admin account Full Control first.

    Though Windows Server 2012 is the changed server, you could also check the permissions on Windows Server 2003.

    TechNet Subscriber Support in forum |If you have any feedback on our support, please contact

    Friday, April 26, 2013 7:40 AM
  • Thanks for the suggestion, but in my troubleshooting I deleted my Rep group, disabled the dfsr service on both servers and completely deleted DFSR folder on the 2003 server and deleted the contents of DFSRPrivate in the root of the replicated folder on the 2012 server. Both were successfully recreated after I re-enabled the service and created a new replication group. Either way, I checked the permissions just now and system has full control on both servers.
    Friday, April 26, 2013 12:26 PM