When everyone works in one building, a file server with shared folders is enough. Once you add a branch, the problems begin: an Excel file on the central server is slow to open, working with large design files becomes practically impossible, and people start keeping files on their own computers just to get some speed. There are several ways to share files between branches, and each one fits a specific situation.
Why is a shared folder slow over a branch link?
The Windows file sharing protocol (SMB) was designed for local networks. To open and save each file, it makes many round trips between the computer and the server. Over a branch link, the latency of those round trips adds up, so even with good bandwidth, working with files feels slow. Newer versions of SMB have improved on this, but the core limitation, link latency, remains.
Method 1: A central file server over VPN
The simplest approach is to keep all files on one central server and give branches access to it over VPN.
- Best for: Small branches, lightweight office files and low-latency links.
- Advantage: A single copy of every file, simple permission management and centralized backup.
- Limitation: With large files or a weak link, the user experience is poor, and a link outage means losing access to all files.
Method 2: Local servers with DFS replication
In Windows networks, you can place a file server in each branch and use DFS Replication to keep folder contents in sync between servers. DFS Namespaces adds a single path such as \\company.local\files that directs users to the nearest server.
- Advantage: Users in each branch work at local network speed, and a link outage does not stop their work.
- Key limitation: DFS Replication has no file locking across servers. If two people in two branches edit the same file at the same time, only one version survives and the other is moved to a conflicts folder.
This method therefore suits folders where each branch edits its own files and the others mostly read them, such as reference documents, forms and archives.
For a large initial replication, do not push all the files over the branch link. Copy the data to the destination server in advance (pre-seeding), and set a replication schedule and bandwidth cap so the link is not saturated during business hours.
Method 3: A web-based sync platform
Solutions such as Nextcloud, installed on a company server or a cloud server, provide file access through a browser and through sync apps on computers and phones. Files travel over HTTPS, usually perform better than SMB on weak links, and also work well for mobile users. On the other hand, the platform must be kept secure and up to date like any other internet-facing service, and its permissions must be managed separately unless it is connected to Active Directory.
Method 4: Working on the server with Remote Desktop
For files that must have a single copy and be edited at the same time from several branches, you can move the work to the central server: users connect to the server with Remote Desktop and open the file there. This eliminates version conflicts, but it requires a suitable server and the right licenses.
Security tips and common mistakes
- Never expose the SMB port (
445) to the internet; file sharing should only run over VPN or another secure platform. - Replication is not a backup. A file that is deleted or encrypted by ransomware in one branch is replicated to the other branches in that same state.
- Define permissions on all servers and platforms based on the same unified groups.
- Stop moving work files between branches on USB drives, messaging apps or personal cloud storage.
Checklist
- File sizes, user counts and link latency for each branch are known.
- For each folder, it is clear whether it is edited simultaneously across branches.
- The sharing method has been chosen based on that need.
- Replication does not saturate the link during business hours.
- SMB is blocked from the internet.
- Files have an independent, versioned backup.
ITPlus724 engineers can review your company’s file structure and design and implement the right file sharing approach for your branches.