Fix 0X000008FC NERR_MultipleNets multi-network error

Windows throws 0X000008FC when a mapped drive or net use targets a PC with multiple active networks. Quick fix: specify the right NIC or adjust binding order.

Quick answer

For the impatient: the fix is to make sure your network binding order puts your primary (work) network first, or use the specific IP of the target machine instead of its name.

Why this happens

I've seen this one pop up in small offices where someone decides to plug a desktop into both the company LAN and a second router—maybe for a guest network or a separate internet line. Suddenly, mapping a drive to a file server gives you the dreaded 0X000008FC with the message "This operation is not supported." Windows is basically saying: "I see multiple networks, and I can't figure out which one to use for this SMB call."

The error maps to NERR_MultipleNets in the Windows networking stack. It happens when the SMB redirector tries to resolve a server name and gets confused because the machine has more than one active network interface with a default route. It's not a permissions problem, not a firewall block—it's a routing ambiguity issue.

I had a client last month whose print queue died because of this. The receptionist's PC had a wired connection to the office switch and a USB Wi-Fi dongle for the guest network. Every time she tried to map the shared drive on the file server, boom—0X000008FC. Took me ten minutes to sort it.

Fix steps (in order)

Disable the extra NIC temporarily. Go to Control Panel > Network and Sharing Center > Change adapter settings, right-click the network you don't need for the drive mapping, and choose Disable. If the map works now, you've confirmed the issue. Re-enable it.
Adjust the interface metric. In the same adapter settings, right-click your primary (office) adapter, go to Properties, select Internet Protocol Version 4 (TCP/IPv4), click Properties, then Advanced. Uncheck Automatic metric and set a value like 10. Do the same for the secondary adapter but set a higher value like 20. This forces Windows to prefer the primary NIC.
Change the binding order. Open Network Connections (run ncpa.cpl), then press Alt to show the menu bar. Click Advanced > Advanced Settings. Under Connections, use the arrows to move your primary network adapter to the top of the list. Click OK.
Map the drive using the server's IP address. If the server is at 192.168.1.10, try net use Z: \\192.168.1.10\share. This bypasses name resolution entirely and often works even when the other fixes don't. But note: if DHCP gives you a different IP later, the map breaks.
Check your routes. Run route print in an admin command prompt. Look for two default routes (0.0.0.0) with different gateways. If you see that, you can delete the unwanted one with route delete 0.0.0.0 mask 0.0.0.0 <gateway> but be careful—that might kill your internet on that adapter. Better to fix the metric as in step 2.

If the main fixes fail

Sometimes the issue isn't the binding order but the SMB client itself. Try these:

Disable SMB over QUIC or SMB signing (if you're on Windows 11 and the server is older). I'm not a fan of disabling signing, but in a pinch it's worth testing. Go to Windows Features and uncheck SMB over QUIC if it's enabled.
Use a hosts file entry. Add the server name and its IP to C:\Windows\System32\drivers\etc\hosts. That forces the name to resolve to the correct IP, bypassing the multi-net confusion.
Check if the target machine also has multiple NICs. The error can originate from the server side. If the server has two NICs, make sure its binding order is correct too.

One time, the problem wasn't the client at all—it was the server having a dual-homed setup with both NICs on the same subnet. That's a classic misconfiguration. If you're the admin, fix that on the server.

Prevention for the future

The real fix is to not have multiple active networks unless you absolutely need them. For most small businesses, that means:

Use a single NIC per machine. Disable Wi-Fi if you're plugged into the LAN.
If you need a second network (like a dedicated IoT or guest network), use VLANs on your switch instead of physically plugging a second cable. That keeps everything on one NIC.
Set your DHCP reservations so your file server always gets the same IP, and map drives by IP rather than name where possible.

I know it's tempting to just live with it, but this error will keep biting you—especially after reboots when Windows decides to re-enable that Wi-Fi adapter. Set the adapter metric and binding order once, and you're done.