Oxolan vs Windows File Sharing (SMB) — why offices replace the built-in
Windows File Sharing costs nothing and is already installed — and it is the single biggest source of office networking pain: network discovery dies after updates, mapped drives drop mid-copy, and errors like 0x80070035/0x80070043 come back no matter how many times you fix them. Oxolan replaces that entire stack with its own discovery and encrypted transfer, so the failure class disappears. A well-run dedicated file server is still fine — it’s peer-to-peer SMB between workstations that deserves replacing.
Feature by feature
| Oxolan | Windows File Sharing (SMB) | |
|---|---|---|
| Price | Paid — flat per office, 14-day free trial | Free, built into Windows |
| Setup | Install once — no shares, no permissions | Shares, NTFS permissions, profiles, firewall rules |
| PCs visible on the network | Automatic, ~300 ms — PCs stay visible | Depends on 4 fragile services — breaks after updates |
| 0x-errors (0x80070035, 0x80070043…) | Cannot occur — no SMB in the path | Chronic, returns after updates |
| Large transfers | Resumes 60 GB+ transfers after a drop | Interrupted copy restarts from zero |
| Encryption | TLS 1.3 + certificate pinning, always on | Varies by SMB version and negotiation |
| File locking | Built-in file locking | Partial (application-dependent) |
| Works when discovery breaks | Yes — own discovery protocol | No — you fix services first |
| macOS in the mix | First-class (macOS 12+) | SMB from Mac to PC is its own adventure |
Speed, with real numbers
On a healthy gigabit network both can move data fast — SMB’s problem has never been top speed, it is reliability. Oxolan sustains 60–115 MB/s with parallel connections, checks every chunk with BLAKE3, and resumes 60 GB+ transfers after a drop — the scenario where Explorer shows "the specified network name is no longer available" and starts over.
Pricing
SMB is free forever, plus the hours spent re-fixing it. Oxolan’s flat per-office license exists to make that time cost go away; the 14-day trial is the test. Oxolan plans run $149–$999/yr by office size (5 to 50 PCs) — see current pricing.
The honest test: run it on two PCs
Install Oxolan next to whatever you use today and let the transfers decide. Free 14 days, no card.
Try Oxolan side by side — freeFrequently asked questions
Why does Windows file sharing keep breaking?
Discovery depends on four background services (Function Discovery Resource Publication, SSDP Discovery, UPnP Device Host, DNS Client) plus a Private network profile and firewall rules — and Windows updates routinely reset them. Each layer failing produces a different error, which is why fixes never stick.
Does Oxolan use SMB underneath?
No. Peer transfers run over Oxolan’s own encrypted protocol (TLS 1.3 with certificate pinning) with its own discovery — the components that produce SMB’s 0x-errors are simply not involved. (Accessing a traditional NAS still uses SMB — that’s a different job.)
Should I remove my file server?
No — a stable, well-configured server or NAS is worth keeping for central storage. What Oxolan replaces is workstation-to-workstation sharing: mapped drives between peers, "\\PCNAME" paths, and the discovery dance.
Is Oxolan safe to use instead of Windows sharing?
Transfers are TLS 1.3-encrypted with certificate-pinned peers and BLAKE3 integrity checks per chunk, and files never leave your network. There is no cloud account and no credentials to phish.