How to Troubleshoot Slow Transfer Speeds Over SMB on Your NAS

Slow file transfers can make a capable NAS feel faulty. A modern Synology or QNAP system may have fast processors, SSDs and multi-gigabit networking, yet copying a folder over SMB can still crawl. The cause is often outside the NAS itself: a weak Wi-Fi link, a negotiating problem on Ethernet, disk activity, or a small-file workload.

SMB, or Server Message Block, is the file-sharing protocol used by Windows, macOS and many Linux systems. Its practical speed depends on every part of the path between the computer and the NAS. A gigabit connection usually tops out near 110 MB/s in real-world transfers, while 2.5GbE can reach roughly 280 MB/s under suitable conditions.

Australian homes have a few specific variables to consider. NBN service type affects internet access, but it does not directly determine the speed of file copies inside your home network. FTTP, FTTC and HFC connections all still rely on your local router, switches and cabling for NAS performance. ISP-supplied routers can also have limited Ethernet features or crowded wireless channels.

The following checks apply to common Synology DSM and QNAP QTS systems, as well as Windows 11 and macOS clients. Work through them in order, changing one variable at a time so you can identify the actual bottleneck rather than applying random settings.

Establish The Real Transfer Rate

Start by measuring a single large file, such as a video archive or disk image. A folder containing thousands of photos will transfer much more slowly because SMB must open, close and record metadata for every item. Small files create extra latency even when the network is otherwise operating perfectly.

Compare the displayed rate with the negotiated link speed. A 1Gbps Ethernet connection reports bits, while file managers usually show megabytes per second, so 1Gbps does not mean 1,000 MB/s. Around 80–115 MB/s is normal after protocol overhead. If the copy sits at 10–12 MB/s, the connection may have fallen back to 100Mbps.

Test in both directions if possible. Copy from the computer to the NAS, then from the NAS to the computer. A USB hard drive, antivirus scanner or nearly full client SSD can limit only one direction. Run the test with a large file first, then use a mixed folder to understand how your ordinary workload behaves.

Check Cables Switches And Link Negotiation

Use Cat5e or better cabling for gigabit Ethernet, and Cat6 for a straightforward 2.5GbE installation. Inspect the cable ends and replace any lead that is kinked, unusually thin or several years old. A damaged pair can trigger a lower negotiated speed or produce errors that cause retransmissions.

Check the network adapter status on the client and the port statistics on your switch or router. The NAS interface should show 1Gbps, 2.5Gbps or 10Gbps full duplex, depending on the hardware. A direct connection between a desktop and NAS can be a useful test, although the devices may require static addresses if there is no DHCP server.

If you are using Wi-Fi, test with a wired computer before changing NAS settings. Wi-Fi 6 can be quick in a Melbourne apartment with a clear signal, yet concrete walls, neighbouring networks and distance can reduce performance sharply. Mesh nodes may also use wireless backhaul, meaning traffic crosses the air twice.

Separate Local SMB From Internet Performance

SMB transfers inside the house should not depend on your NBN download speed. If a local copy is slow, check whether both devices are connected to the same LAN and whether the computer is accidentally reaching the NAS through a remote-access address. Split DNS, VPN software and security products can send traffic along an unexpected route.

Remote SMB access over the public internet is generally a poor performance test and a security risk. For travel access, use a properly configured VPN, Synology Drive, QNAP’s supported synchronisation tools or another encrypted file service. If you are reviewing documents while travelling through Almaty or planning a trip using Kazakhstan travel information, do not expose TCP port 445 directly to the internet just to make a share reachable.

On the NAS, review the active connections and IP address. A second interface, VLAN or Docker bridge can cause confusion when several names resolve to different addresses. Test with the NAS’s local IP address and a simple mapped share. Disconnect the VPN temporarily on the client, then restore it after the comparison.

Review SMB And NAS Settings

Keep SMB enabled at version 2 or 3 and avoid SMB1 unless an old device genuinely requires it. SMB1 is obsolete and has serious security weaknesses. On Synology, the relevant controls are found in File Services and SMB settings; QNAP places comparable options under Network & File Services.

Encryption and signing can reduce throughput, especially on an older NAS processor or a system handling several tasks. Do not disable these protections casually. Instead, check whether they are being forced by a domain policy, client security setting or share configuration. On a trusted home LAN, using modern SMB defaults is usually a better balance than pursuing a benchmark figure.

SMB Multichannel can improve performance when both the client and NAS support it and there are multiple suitable network paths. It can also complicate diagnosis. Test with a single active interface first, then enable advanced features after basic transfers are stable. Jumbo frames should be treated similarly: every device on the path must support the same MTU, or transfers may become unreliable rather than faster.

Inspect Disks RAID And Background Tasks

A NAS cannot sustain fast SMB writes if its storage pool is busy rebuilding, checking parity or running a large backup. Look at Resource Monitor in DSM or QTS and check CPU, RAM, disk utilisation and network throughput during a copy. A scheduled Hyper Backup, HBS job, media index or cloud synchronisation task may explain an otherwise unexplained slowdown.

RAID type affects writing behaviour. RAID 5, RAID 6 and their Synology SHR equivalents calculate parity, which can reduce write performance, particularly with random or small-file workloads. A degraded array can be dramatically slower and should be repaired promptly after confirming that the replacement disk is healthy.

Use the NAS health tools to check SMART warnings, bad sectors and temperatures. A failing disk may retry operations for seconds at a time, making SMB appear intermittent. SSD caching is not a universal cure: it helps repeated random access more than a single large sequential copy, and it cannot compensate for a weak network link or an overloaded CPU.

Match The Test To Your Files

Large sequential files are the best way to assess network throughput. Video production files, virtual machine images and disk backups reveal whether the Ethernet path is working near its expected limit. If those files are fast but office folders remain slow, the issue is likely metadata overhead, application behaviour or the number of files.

File-system features can affect results. Windows Defender, third-party antivirus and macOS indexing may inspect every item as it arrives. Encrypted shares, compression, snapshots and deduplication can also consume processor resources. Test a temporary share with normal settings, then compare it with the production share without permanently removing useful protection.

Useful comparisons can narrow the fault quickly:

• Copy one 10 GB file to measure sequential performance.
• Copy a folder of small documents and photos to expose metadata overhead.
• Test a second computer on the same switch and share.
• Compare wired Ethernet with the usual wireless connection.
• Monitor NAS CPU, disk activity and network graphs during every test.

For a repeatable result, use the same file, destination and client each time. Record the average transfer rate rather than focusing on a brief peak shown at the start of a copy. Caches can make the first few seconds look impressive before the actual disk or network limit becomes visible.

Improve The Client And Network Path

Update the NAS firmware, network adapter drivers, operating system and switch firmware before deeper changes. Rebooting can clear a stalled service, but it should not be considered a permanent fix. If performance degrades after hours or days, inspect logs for link resets, storage errors and authentication failures.

On a desktop, connect directly to the main switch rather than through a powerline adapter, extender or old 100Mbps switch. A Sydney home office may have the NAS beside the router while the workstation sits in another room, so a properly installed Ethernet run can deliver a larger improvement than buying faster disks. In a rental, a short Cat6 lead and a compact switch may be the most practical upgrade.

Avoid forcing speed or duplex settings unless the manufacturer specifically recommends it. Auto-negotiation is normally the correct choice, and mismatched manual settings can create packet loss. Replace suspect switches with a known-good gigabit or 2.5GbE model and test again before changing MTU, DNS or firewall rules.

A sensible upgrade path depends on the current limit:

• Use wired Ethernet for fixed computers and editing workstations.
• Choose a 2.5GbE switch only when the NAS, client and cabling support it.
• Add RAM when monitoring shows memory pressure during file services.
• Use SSD storage for active projects with many random reads and writes.
• Keep backups separate from the NAS performance experiment.

When a NAS is used by a small business, schedule intensive backup and indexing tasks outside trading hours. For a home in Brisbane, Perth or regional New South Wales, local network design matters just as much as the advertised NAS specification. Internet outages may stop cloud synchronisation, but they should not stop a correctly configured local SMB share.

Apply one change at a time and retain the results. If a large wired transfer reaches the expected rate but ordinary folders remain slow, the NAS is probably healthy and the workload is the limiting factor. If every test is slow, focus on link negotiation, storage health and background services before buying new hardware.

Work through these checks on your own system and document the before-and-after figures. A careful diagnosis can restore reliable SMB performance without unnecessary upgrades, while also revealing whether your next investment should be cabling, a switch, faster disks or a more suitable NAS.