| Event Id | 13539 |
| Source | NtFrs |
| Description | The File Replication Service cannot replicate<Location>because the pathname of the replicated directory is not the fully qualified pathname of an existing, accessible local directory. |
| Event Information | According to Microsoft: DFS topology starts with the root of the DFS tree. The DFS root at the top of the logical hierarchy is mapped to a physical share. A DFS link maps a Domain Name System (DNS) name to the UNC name of the target shared folder or target DFS root. When a DFS client accesses a DFS shared folder, the DFS server uses the DNS name to UNC mapping to return a referral to the client so that it can locate the shared folder. Mapping the DNS name to the UNC name makes the physical location of data transparent to users, who no longer have to remember the server where a folder is stored. When a DFS client requests a referral to a DFS share, the DFS server uses the Partition Knowledge Table (PKT) to direct the DFS client to the physical share. The PKT is stored in Active Directory for domain-based DFS and is stored in the registry for stand-alone DFS. In a network environment, the PKT maintains all information about DFS topology, including its mappings to the underlying physical shares. After the DFS server refers the DFS client to a list of replica shares that correspond to the requested DFS link, the DFS client uses Active Directory site topology to connect to a replica in the same site or, if one is not available, a replica that is outside the site. |
| Reference Links | Overview of DFS in Windows 2000 |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.