Network error 0x800704b3 in Windows 11 typically appears when you try to access shared folders, map a network drive, or connect to a network printer. It means Windows cannot reach the network resource, often due to incorrect network discovery settings, a blocked port, or a misconfigured network adapter. This guide walks you through the most effective fixes, from enabling network discovery to resetting the network stack.
What You’ll Need
- Administrator access to your Windows 11 PC (you’ll need to confirm UAC prompts).
- The exact name or IP address of the computer or device you’re trying to reach.
- Optional: a USB drive to back up your network settings if you plan to reset the network stack.
Step-by-Step
- Enable Network Discovery and File Sharing
Open Settings (Win + I) → Network & internet → Advanced network settings → Advanced sharing settings. Under Private networks, turn on Network discovery and File and printer sharing. If you’re on a public network, switch to a private one (or temporarily enable these for public, then switch back). - Check the Network Profile
Go to Settings → Network & internet → Wi-Fi or Ethernet. Click your connected network and ensure the Network profile type is set to Private. If it’s Public, network discovery is often blocked. - Run the Network Troubleshooter
Go to Settings → System → Troubleshoot → Other troubleshooters. Click Run next to Network Adapter and Shared Folders. Follow the prompts and restart if suggested. - Verify the Target Device is Reachable
Open Command Prompt (as admin) and run:ping target-ip. If ping fails, the device may be off, on a different network, or firewall-blocked. Also trynet viewto list available shares. - Enable SMB 1.0/CIFS (if needed)
Some older devices use SMB 1.0, which is disabled by default in Windows 11. Go to Control Panel → Programs → Turn Windows features on or off. Check SMB 1.0/CIFS File Sharing Support and restart. Only enable if you must connect to legacy hardware. - Check Windows Firewall Rules
Open Windows Security → Firewall & network protection → Allow an app through firewall. Ensure File and Printer Sharing is checked for both Private and Public (if needed). If you use a third-party firewall, add exceptions for ports 139, 445, and 5353. - Reset the Network Stack
Open Command Prompt as administrator and run these commands one by one, pressing Enter after each:
netsh winsock reset
netsh int ip reset
ipconfig /release
ipconfig /renew
ipconfig /flushdns
Restart your PC. - Re-add the Network Location
If mapping a drive, remove the existing mapping (right-click the drive in File Explorer → Disconnect). Then re-map using the full path:\\computer-name\shareor\\ip-address\share. Check the Connect using different credentials box if needed. - Update or Reinstall the Network Adapter Driver
Open Device Manager (right-click Start). Expand Network adapters, right-click your adapter, choose Update driver → Search automatically. If that fails, uninstall the device (check Delete the driver software) and restart – Windows will reinstall it.
Common Mistakes
- Forgetting to set the network profile to Private – public networks block discovery by design.
- Typing the share path with a single slash instead of double backslashes (e.g.,
\serverolderis correct, not/server/folder). - Enabling SMB 1.0 unnecessarily, which can be a security risk – only do it for legacy devices.
- Not restarting after making changes – many settings require a reboot to take effect.
- Assuming the target device is on the same network – check that both are on the same subnet or VPN.
Tips
- Use the computer’s IP address instead of its name if name resolution is failing. You can find the IP with
ipconfigon the target machine. - If you’re using a VPN, try disconnecting temporarily – VPNs can interfere with local network discovery.
- Keep Windows updated. Many network bugs are fixed in cumulative updates.
- For persistent issues, create a new local user account and test – this can rule out profile corruption.
Troubleshooting
If the error persists after following all steps:
- Check the target device’s firewall. Windows Defender Firewall on the remote PC may block incoming connections. Temporarily disable it (with caution) to test.
- Verify the share exists. On the remote computer, right-click a folder → Properties → Sharing → Share. Ensure the user account you’re using has read/write permissions.
- Use the IP address directly. Try
\\192.168.1.10\shareinstead of the computer name. If this works, the issue is DNS or NetBIOS name resolution. - Check the SMB protocol version. Run
Get-SmbConnectionin PowerShell to see what dialect is being used. If it’s SMB 1.0, consider upgrading the remote device. - Reset the network adapter. In Settings → Network & internet → Advanced network settings → Network reset. This reinstalls all network adapters and resets settings to defaults. You’ll need to reconnect to Wi-Fi and reconfigure VPNs.
- Check for third-party security software. Antivirus or firewall suites can block SMB ports. Temporarily disable them to test, then add exceptions.
Frequently Asked Questions
What does error 0x800704b3 mean?
It means Windows cannot access a network resource, usually because network discovery is off, the target device is unreachable, or a firewall is blocking the connection.
Is this error related to the internet?
No, it’s about local network sharing. Your internet may work fine, but Windows cannot see other computers on your LAN.
Do I need to enable SMB 1.0?
Only if you’re connecting to very old devices (like Windows XP or some NAS drives). For modern systems, keep SMB 1.0 disabled for security.
Why does the error appear when mapping a network drive?
It usually means the share path is incorrect, the remote computer is off, or your user account lacks permissions. Double-check the path and credentials.
Will resetting the network stack delete my Wi-Fi passwords?
No, netsh winsock reset and netsh int ip reset do not clear Wi-Fi profiles. However, the Network reset option in Settings will remove all network adapters and require you to reconnect.
Can I fix this without admin rights?
Most fixes require administrator privileges. If you don’t have them, contact your IT department or the account administrator.
Related
General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.
More in this bed
- Fix Device Manager Not Opening in Windows 11
- How to Pause Snapchat Location
- System Restore Points Missing in Windows? Fixes
- Install League of Legends on Linux: Full Guide
- Fix Error 0x80070001: Causes & Solutions
- Facebook.com: What It Is and Is It Safe?9.26 yd³