If possible, we recommend specifying the full administrative paths to the remote machines. Under certain circumstances, it may be more convenient to use DFS namespaces. PeerSync supports the use of DFS namespaces, provided that they are accessible by the host and user account running PeerSync.
If using DFS namespace paths with the ByteReplicator, the PSListener will need to be installed on the Domain Controller. If you have more than one Domain Controller in your domain it may be necessary to install the PSListener on all of them. The PSListener would need to be installed on all the Domain Controllers that could potentially be selected by the host computer when it tries to look up the DFS namespace.
Related articles
Page: Best Practices: Revit Worksharing Page: Can I use DFS Namespaces when specifying folder paths in PeerSync? Page: Configure PeerSync Listener's advanced settings Page: Configure the PeerSync Listener installer to run unattended Page: Does PeerSync Listener have to be installed on both servers when using the ByteReplicator? Page: How does the ByteReplicator work? Page: Set up synchronization/replication over TCP Page: Upgrade PeerSync and PeerSync Listener Page: Why does ByteReplicator use .BRTMP temporary files?