DEV Community

疏影
疏影

Posted on

When RaiDrive is overkill: a leaner WebDAV client for Windows

#webdavnasive #webdav #webdavnaswindowsopensource

The problem I keep running into

I work with a small engineering team that has a Synology NAS on one LAN and three engineers who need access from another LAN over the public internet. Built-in Windows WebDAV (net use w: https://...) is the natural first choice and it fails almost immediately on multi-gigabyte files. The error is always something like:

System error 67 has occurred.
The specified network name is no longer available.
Enter fullscreen mode Exit fullscreen mode

This is a known Microsoft limitation. The WebClient service is fine for small files on a fast LAN. It is not a production cross-internet client. Every engineer who has ever tried to use it for real work knows this.

What I have tried

Tool Verdict
Built-in WebClient (net use) Works for docs, fails for ISOs and CAD
SMB over WireGuard Works but adds VPN setup to the user
RaiDrive Works, costs ~$40/license, UI bloats with features I do not need
NetDrive Works, similar price, slightly older UI
ScsDriver Works, cheaper than RaiDrive, kernel mount handles flaky 4G links better than RaiDrive

The interesting engineering choice in ScsDriver is a kernel-level mount instead of a userspace shim. That is what makes it cope with a 20 GB ISO over a 4G mobile hotspot where RaiDrive times out.

When you should pick what

  • Built-in WebClient — small text files on a fast LAN. Nothing else.
  • RaiDrive — you mount 4+ different cloud providers and want one tool. Budget is not the constraint.
  • NetDrive — you only need WebDAV plus FTP/SFTP and want a long-established enterprise UI.
  • ScsDriver — you only need WebDAV, you are on flaky networks, and the per-license price matters.

The honest take

I have no relationship with any of these vendors. I have shipped with all of them. If you are looking at a single WebDAV-only deployment and you have ever lost a day to "the network name is no longer available", ScsDriver is the cheapest and most reliable option I have tested. The trade-off is that you give up RaiDrive protocol breadth — which, if you only needed WebDAV anyway, is a trade-off you want to make.

Have a different stack I should look at? Drop it in the thread.

Top comments (0)