Quantcast
Channel: File Services and Storage forum
Viewing all articles
Browse latest Browse all 10672

DFSR Setup Problem

$
0
0

I have 3 domains, each one at a different location.  Each domain has a two way trust relationship between them, but share the same Schema.  Each domain has a DC (Server 2003 native function level) and a file server (Server 2008 and 2 x Server 2012s).  I wanted to test out DFSR to see if it can help me eliminate some duplicate data entry and help with some backup limitations we have.

I installed DFS on the 2 file servers.  I wanted to just sync a test folder between both of the 2012 servers but I am unable to do so.  The 2 servers I am trying to sync are both domain member servers of different domains separated by a WAN VPN.  I am focusing on the Replication part.  I'm not interested in the Namespace part.  So I attempt to create a new Replication Group for Data Collection.  I put in the name of my Replication Group (Test) and the name of my domain (Domain A).  I enter the server name (Server A) and then add the path to the folder I want to replicate.  When I enter in the Hub server (Server B) I get an error that says "The server's operating system version cannot be retrieved.  The network path was not found".  I use the FQDN (I always have to in order to communicate between servers over the WAN) and I get the same error.  I can ping the server, I can access network shares on it.  But cannot set this up. 

I started thinking that the reason I cannot connect to it has to do with user permissions.  I am logged in as the domain administrator for Domain A.  I want to sync to Server B on Domain B.  However Server B is not a domain controller, but instead also a member server.  If I try to setup a replication with a domain controller on Domain B, I do not get the error and am able to proceed to the next step.  I tried adding the Domain A domain admins group to the Domain B user account list administrators group but problem remains.  I think that if Server B was a domain controller, I probably wouldn't have this issue because it would be authenticating directly to Active Directory.  The problem must be Server A not being able to authenticate to the domain controller for domain B. 

I hope this makes sense.  If anyone can help I would appreciate it.  I'll be on for another hour or so, then I'll check back in tomorrow. 

Thanks


Viewing all articles
Browse latest Browse all 10672

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>