I’m trying to access a USB device (like a dongle and external drive) over a VPN so it works as if it’s plugged directly into a remote computer. I’ve tried a couple of tools but they’re either unstable, slow, or don’t handle reconnects well. I’m looking for reliable USB over VPN methods or software recommendations that are secure, support Windows and possibly Linux, and can handle multiple devices without constant manual tweaking. What solutions or setups are you using that actually work in real-world use?
Short version. You want USB over VPN to feel like the device sits right in the remote box. You need something that shares the USB device at the driver level, not a flaky file share or weird RD hack.
Here are the options that usually work and do not suck too much:
-
USB Network Gate
For dongles and external drives this is one of the more stable tools.
Server side, install it on the PC where the USB is plugged in. Share the dongle or drive from the app.
Client side, install on the remote PC, connect to the shared device.
Windows, macOS, Linux, even some server setups.
Licensing is per host, so plan your budget if you have many endpoints.
Performance over VPN is close to LAN if your VPN is not choked. For software license dongles it is solid. For big file transfers it works but needs a decent connection.
This is the one you should test first. -
Hardware USB over IP hubs
Vendors like Silex or Digi sell USB device servers.
You plug the USB key or disk into the hardware box.
Box connects to your network. Client uses a driver to map that USB device.
Over VPN this works if you route the VPN to the subnet where the box lives.
Good for a small office with one “dongle corner”. Less great if your device needs special drivers on the host side. -
RDP USB redirection
If both sides run Windows Pro or Server and you only need it inside an RDP session.
Plug the USB into your local machine. Enable local resources USB in the RDP client.
RDP sends the USB into the remote session.
Good for license dongles and smartcards. File storage works but is slower.
Drawback, the USB is visible only inside that remote session, not to other users or services on the remote host. -
VPN and protocol tuning
For any USB over IP software you need:
• Stable latency under 80–100 ms for dongles.
• For external drives, at least 10–20 Mbps up and down for okay speeds.
• Avoid double encryption if the USB tool already encrypts traffic. Use one secure layer, not two.
If you want a guide that focuses on USB over VPN setups, this page helps:
reliable USB sharing over VPN
For your exact use case, dongle plus external drive over VPN, I would:
• Start with USB Network Gate on both ends.
• Put both hosts on a routed VPN, not split tunneling for that traffic.
• Test the dongle first. If that is stable over a week, then push the external drive and see the throughput.
If file access feels too slow over VPN, keep the dongle over USB Network Gate, but sync the drive using SMB plus something like Robocopy, Resilio, or rsync instead of full USB passthrough.
1 Like
If you want it to behave like “physically plugged into the remote box,” you really have to treat it like a transport problem at the USB layer, not another file share gimmick. I’m mostly on the same page as @codecrafter, but I’d tweak the approach a bit.
1. Don’t mix the dongle and the external drive requirements
Dongles and disks behave very differently over VPN:
-
Dongle / license key
- Latency sensitive, but barely any bandwidth
- Needs rock‑solid, low jitter
- Works fine over 5–10 Mbps as long as latency is under ~80 ms
-
External drive
- Bandwidth hungry
- Not that sensitive to latency, but hates packet loss and jitter
- Over slow or lossy VPNs, it feels like you’re dragging files through wet cement
Trying to get both to “feel local” over the same weak link is usually what makes people think “this software sucks” when in reality the network sucks.
2. USB Network Gate is fine, but tune your stack or it will feel laggy
USB Network Gate is probably still your best bet for an all‑in‑one USB over IP tool. Where I disagree slightly with @codecrafter is on the “close to LAN” bit for drives. That’s only true if:
- You’re on a routed VPN, not some cobbled PPTP relic
- You avoid double encryption: if your VPN is already using strong crypto, don’t pile on insane extra encryption features in the USB tool unless you actually need them
- You set the VPN to use UDP where possible and enable keep‑alives so idle dongle connections don’t drop
If your use case is mostly license dongle + “occasional” drive use, I’d do:
- Put the dongle on USB Network Gate permanently
- Use the drive in short bursts, not as a constant read/write target
3. For the drive, consider not doing pure USB passthrough
This is where I’d actually go a bit against the full USB‑over‑VPN idea:
- Use USB Network Gate for the dongle only
- For the external drive:
- Format it on the local machine
- Expose the files over SMB, SFTP, or rsync/RoboCopy instead of USB passthrough
- Treat USB passthrough for storage as a last resort
Protocol‑level file copy tools handle crappy WAN links way better than raw USB traffic. USB mass storage over a noisy VPN is honestly asking for stalls and timeouts. If you absolutely must keep it as a block device, plan for:
- At least 20–30 Mbps symmetrical bandwidth
- Low packet loss (<0.5 %)
- Reasonable RTT (<70 ms)
If you’re under those, the drive will “work” but it won’t feel local, period.
4. Alternative approach: attach at the server side, not the client
One trick that often works better:
- Plug the USB drive into a machine near the VPN server
- Run USB Network Gate server there
- Connect to it from the remote client over the VPN
That keeps one side in a clean LAN and only sends USB traffic across the WAN once. Way fewer weird hiccups compared to hopping across multiple NAT layers and Wi‑Fi.
5. If you’re still shopping tools and want to test more
Since you said some tools were unstable or slow, make sure you test them with:
- A fixed MTU on the VPN (try 1400 or 1420, then work down if you see fragmentation)
- Disabled power saving on USB controllers on Windows
- No “aggressive” firewall inspection on the USB/IP ports
For an easy way to grab a build and try things, see
download reliable USB over IP tools for secure remote access
and start with USB Network Gate on both ends, then layer the file‑level stuff for the disk if performance annoys you.
TL;DR version:
- Use USB Network Gate for the dongle, it’s one of the few pieces of software that behaves decently over VPN for that.
- Test the external drive over it, but don’t be shocked if it’s meh unless your VPN is solid.
- For serious file work, let the dongle ride over USB, and let the drive ride over SMB/rsync instead of pretending the WAN is a USB cable.
Splitting use cases like @codecrafter did is smart, but I’d flip the priority a bit.
If your primary pain is the dongle, then full USB tunneling is justified; if the drive is the real workhorse, I’d almost avoid USB passthrough entirely and design around file protocols first.
1. Alternatives to full USB passthrough for the drive
Instead of trying to make the external disk “look” local over VPN, try:
-
iSCSI target on the side where the drive is plugged in, mounting it as a block device on the remote side.
- Pros: behaves closer to a disk than SMB, good for certain apps.
- Cons: very sensitive to packet loss and latency; needs careful MTU and QoS tuning.
-
A proper file protocol:
- SMB with offline files or DFS-R if you are in a Windows domain.
- Syncthing or Resilio‑style sync if you mostly shuttle working sets back and forth instead of live-editing huge files.
This often beats any USB-over-IP scheme when the WAN is mediocre.
2. Where USB Network Gate actually shines
For the dongle, USB Network Gate is still a solid choice:
Pros:
- Handles weird vendor dongle drivers better than most open USB/IP stacks.
- Works acceptably with moderate latency as long as jitter is controlled.
- Encryption / access control options that are actually usable in a business environment.
Cons:
- For storage, performance can drop sharply on noisy VPN links.
- Extra moving part in your stack, so more places to debug.
- Licensing cost vs free USB/IP implementations if you only need basic lab-style connectivity.
If you go with USB Network Gate, I’d dedicate it to:
- Dongles.
- Niche USB gear that has no sane network-aware alternative (some measurement devices, card readers, etc).
I actually disagree slightly with the idea that “test your drive and see” is enough. With spinning disks or large SSD workloads, USB-over-VPN tends to hide problems until the worst moment: big sequential copies or many small I/O operations. For serious workloads I would design assuming USB passthrough for disks is a last-ditch option, not something to rely on long term.
3. Architecture tweak that often helps
Instead of “laptop ↔ flaky Wi‑Fi ↔ internet ↔ VPN server ↔ target PC with USB,” try:
- Plug the USB devices into a stable host near the VPN endpoint.
- Run USB Network Gate or similar there.
- Access that host from the remote system as the only USB/IP hop.
Then, for the drive, share from that host via SMB/SFTP to other internal machines rather than tunneling the block device twice.
4. If you want an alternative path to test
While @codecrafter focused on USB over IP tooling broadly, another angle is:
- VPN over WireGuard or modern IKEv2 for lower overhead.
- QoS rules prioritizing your USB/IP or iSCSI traffic.
- Fixed MTU and disabled “clever” packet inspection on your router.
Only once the transport is clean should you judge whether USB Network Gate or any rival is “unstable” or “slow.” Often the tool is just revealing how sketchy the VPN path really is.
In short:
- Dongle: USB Network Gate is a good fit, worth tuning around it.
- External drive: strongly consider iSCSI or file protocols first, keep USB passthrough as a fallback when you absolutely must pretend the cable is 2000 km long.