Solve Network Error 0x800704b3: Step-by-Step Fixes

Network error 0x800704b3 typically appears on Windows when the system cannot reach a network resource due to a misconfigured firewall, corrupted network settings, or a blocked SMB port. The fix involves resetting network components, adjusting firewall rules, and ensuring required services are running—most users resolve it in under 15 minutes by following the steps below.

What Is Error 0x800704b3?

Error 0x800704b3 is a Windows networking error that usually shows up when you try to access a shared folder, map a network drive, or connect to a network-attached storage (NAS) device. The full message often reads: “Windows cannot access \\computer\share. Error 0x800704b3: The operating system cannot run this application.� This occurs when the client cannot establish a session with the server, often due to a firewall blocking the Server Message Block (SMB) protocol or a disabled network service.

While the error is not new, it became more common after Windows 10 and 11 tightened default firewall rules and disabled older SMB versions. Understanding the cause is the first step: the error is almost never a hardware failure—it’s a software configuration issue that you can fix without special tools.

Common Causes of Error 0x800704b3

Several underlying issues can trigger this error. The most frequent ones include:

Firewall blocking SMB ports: Windows Defender Firewall or third-party security software may block ports 445 (SMB) or 139 (NetBIOS).
Disabled network services: Services like “Function Discovery Provider Host� or “TCP/IP NetBIOS Helper� may be stopped.
Corrupted network stack: Winsock or TCP/IP settings can become misconfigured after a system update or malware.
Incorrect SMB protocol settings: If SMB 1.0 is required by an older device but is disabled, the connection fails.
Group Policy or registry restrictions: Sometimes a policy blocks guest access or insecure logins.

Diagnosing which cause applies to you is straightforward: if the error appears only for one specific share, it’s likely a protocol or permission issue; if it appears for all network shares, it’s likely a firewall or service problem.

Before You Start: Quick Checks

Before diving into advanced fixes, verify these basics to rule out simple issues:

Ensure both computers are on the same network and can ping each other (use ping in Command Prompt).
Check that the target computer is turned on and not in sleep mode.
Confirm you have the correct credentials for the shared folder.
Test if the issue occurs with a different share or computer—this isolates the problem.

If these checks pass, proceed with the fixes below. They are ordered from least disruptive to most thorough.

Fix 1: Reset Network Stack and Winsock

Corrupted network settings are a leading cause of error 0x800704b3. Resetting them is safe and often resolves the issue immediately.

Open Command Prompt as administrator (search “cmd�, right-click, and select “Run as administrator�).
Type netsh winsock reset and press Enter. This resets the Winsock catalog.
Type netsh int ip reset and press Enter. This resets the TCP/IP stack.
Restart your computer.

After the restart, try accessing the network share again. If the error persists, move to the next fix.

Fix 2: Ensure Required Services Are Running

Windows relies on several services for network browsing and file sharing. If any are disabled, you’ll see error 0x800704b3. Check these services:

Function Discovery Provider Host (fdPHost)
Function Discovery Resource Publication (FDResPub)
TCP/IP NetBIOS Helper (lmhosts)
Server (LanmanServer)
Workstation (LanmanWorkstation)

To enable them:

Press Win + R, type services.msc, and press Enter.
Find each service, right-click, and select “Properties�.
Set “Startup type� to “Automatic� and click “Start� if it’s not running.
Repeat for all services listed above, then restart your PC.

If a service fails to start, note the error message—it may point to a deeper system issue.

Fix 3: Adjust Firewall Settings for SMB

Firewalls often block the ports that file sharing uses. While you can temporarily disable the firewall to test, the proper fix is to allow the specific rules.

Open Windows Defender Firewall by searching “Windows Defender Firewall� in the Start menu.
Click “Allow an app or feature through Windows Defender Firewall�.
Click “Change settings� (requires admin).
Find “File and Printer Sharing� and ensure both “Private� and “Public� checkboxes are checked.
If it’s not listed, click “Allow another app� and browse to C:\Windows\System32\svchost.exe (though this is rarely needed).

Alternatively, you can create an inbound rule for ports 445 and 139:

In Windows Defender Firewall, click “Advanced settings�.
Click “Inbound Rules� → “New Rule�.
Select “Port� and click Next.
Enter 445, 139 in the “Specific local ports� field.
Select “Allow the connection� and complete the wizard.

If you use third-party antivirus with its own firewall, check its settings as well—it may override Windows Firewall.

Fix 4: Enable SMB 1.0 (If Needed) and Check SMB Signing

Some older NAS devices or Windows 7 machines require SMB 1.0, which modern Windows disables by default. Enabling it can resolve the error, but be aware of the security risks (SMB 1.0 is vulnerable to malware like WannaCry). Only enable it temporarily for legacy devices.

Open “Control Panel� → “Programs� → “Turn Windows features on or off�.
Check “SMB 1.0/CIFS File Sharing Support�.
Click OK and restart.

If SMB 1.0 is already enabled, the problem might be SMB signing. Some devices require signed SMB connections; you can disable signing on your Windows client to test:

Open “Local Security Policy� (search “secpol.msc�).
Go to “Security Settings� → “Local Policies� → “Security Options�.
Find “Microsoft network client: Digitally sign communications (always)� and set it to “Disabled�.
Restart.

Fix 5: Use IP Address Instead of Computer Name

If the error is due to name resolution issues, accessing the share via IP address can bypass the problem. First, find the target computer’s IP address (run ipconfig on that machine). Then, in File Explorer’s address bar, type \\192.168.x.x\share instead of \\computername\share.

If this works, the issue is with NetBIOS or DNS. You can add an entry to the hosts file (located at C:\Windows\System32\drivers\etc\hosts) mapping the computer name to its IP address. Open the file as administrator and add a line like 192.168.1.10 mycomputer.

Frequently Asked Questions

Does error 0x800704b3 mean my network is down?
No. It specifically indicates that Windows cannot access a shared resource, not that your internet or LAN is broken. You can still browse the web normally.

Can I fix this by restarting my router?
Rarely. The error is almost always a Windows configuration issue. Restarting your router only helps if the network itself is unstable, which would produce different errors.

Is it safe to disable firewall for file sharing?
Only temporarily for testing. The correct approach is to add an allow rule for SMB ports, as described above. Disabling the firewall entirely exposes your system to network threats.

Why does this error happen after a Windows update?
Updates can reset network settings or change firewall defaults. Re-applying the fixes in this guide usually resolves it. If not, check for a newer update that may address the regression.

What if none of these fixes work?
Try running the Windows Network Troubleshooter (Settings → Network & Internet → Status → Network troubleshooter). If that fails, consider resetting Windows network settings entirely (Settings → Network & Internet → Advanced network settings → Network reset). This reinstalls network adapters and resets all settings to default.

Does this error affect Mac or Linux users?
No, it’s Windows-specific. However, if you’re trying to connect to a Windows share from a Mac, you might see a different error like “Connection failed� or “The operation can’t be completed.�

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →