Fix System Error 67 on Windows 10: Network Name Not Found

System Error 67 on Windows 10 means “The network name cannot be found.” It usually appears when you try to map a network drive, connect to a shared folder, or run a net use command. The fix is to check the network path, enable SMB 1.0/CIFS if needed, or restart the Workstation service — and this article walks through each step in order.

What Causes Error 67

Error 67 is a Windows networking error that occurs when the client cannot resolve or reach the network share name you specified. Common triggers include:

• Typing the wrong computer name, IP address, or share name in the path (e.g., \\server\share).
• The target computer is turned off, asleep, or not on the same network.
• Firewall or network discovery settings are blocking SMB (port 445) traffic.
• The target computer has SMB 1.0 disabled, while the client is trying to connect using that older protocol.
• The Workstation service (LanmanWorkstation) is stopped or not running.
• DNS or NetBIOS name resolution fails, so the computer name cannot be translated to an IP address.

Unlike error 53 (path not found) or error 5 (access denied), error 67 specifically means the name itself could not be found on the network. That distinction matters because the fix usually involves name resolution or protocol support rather than permissions.

Step 1: Verify the Network Path

The most common cause of error 67 is a simple typo or incorrect path. Before changing any settings, double-check the path you are using:

• Use the computer’s IP address instead of its name: \\192.168.1.10\sharedfolder
• Use the fully qualified domain name (FQDN) if on a domain: \\server.example.com\share
• Confirm the share name is spelled correctly — right-click the folder on the host, select Properties > Sharing to see the exact share name.
• Test basic connectivity with ping and ping to see if the host responds.

If the IP address works but the name does not, the problem is name resolution, which is covered in Step 4.

Step 2: Restart the Workstation Service

The Workstation service (LanmanWorkstation) is responsible for making SMB connections from your Windows 10 PC. If it is stopped or hung, you will get error 67. To restart it:

1. Press Win + R, type services.msc, and press Enter.
2. Scroll down to Workstation.
3. Right-click it and select Restart. If it is not running, right-click and select Start.
4. Set its Startup type to Automatic if it isn’t already.

You can also do this from an elevated Command Prompt:

net stop lanmanworkstation
net start lanmanworkstation

After restarting, try mapping the drive again. This fixes the error when the service was disabled by a previous session or a third-party tweaking tool.

Step 3: Enable SMB 1.0/CIFS (Only If Necessary)

Windows 10 disables SMB 1.0 by default because it is outdated and insecure. However, some older devices (like legacy NAS drives or Windows XP/7 machines) still require it. If you are connecting to such a device, error 67 can appear because the client only offers SMB 2/3 while the server only speaks SMB 1.

To enable SMB 1.0:

1. Open Control Panel > Programs > Turn Windows features on or off.
2. Expand SMB 1.0/CIFS File Sharing Support.
3. Check SMB 1.0/CIFS Client (and Server if you also need to share out).
4. Click OK and restart your PC.

Only enable SMB 1.0 if you are sure the target device needs it. Leaving it enabled increases your exposure to ransomware like WannaCry. After the connection works, you can disable it again.

Step 4: Fix Name Resolution (NetBIOS and DNS)

If the path is correct but error 67 persists, Windows may not be able to resolve the computer name to an IP. Try these fixes in order:

• Flush DNS and NetBIOS cache: open Command Prompt as admin and run ipconfig /flushdns and nbtstat -R.
• Make sure NetBIOS over TCP/IP is enabled on your network adapter: Settings > Network & Internet > Status > Change adapter options, right-click your adapter, select Properties, select Internet Protocol Version 4 (TCP/IPv4), click Properties, then Advanced > WINS tab, and select Enable NetBIOS over TCP/IP.
• Add an entry to the hosts file if the server’s IP is static. Open C:\Windows\System32\drivers\etc\hosts as admin and add a line like 192.168.1.10 server.
• If on a domain, ensure the DNS server is reachable and the computer account is not stale.

If you are using a workgroup, NetBIOS is often the quickest fix. Many home routers disable NetBIOS by default, so enabling it on the adapter can resolve the name instantly.

Step 5: Check Firewall and SMB Ports

Windows Firewall or a third-party firewall can block the SMB connection, causing error 67. The target computer must allow inbound SMB traffic on port 445. To check:

1. On the target computer, open Control Panel > Windows Defender Firewall > Allow an app or feature through Windows Defender Firewall.
2. Ensure File and Printer Sharing is checked for the appropriate network profile (Private).
3. If you have a third-party firewall, temporarily disable it to test — if the connection works, re-enable it and add an exception for port 445.

You can test port 445 from the client with Test-NetConnection -Port 445 in PowerShell. If it returns False, the port is blocked.

Frequently Asked Questions

What does error 67 mean in net use?

When you run net use and get error 67, it means the network name you specified could not be found. This is different from “access denied” (error 5) or “path not found” (error 53). It usually points to a name resolution problem or the share not existing.

Is error 67 the same as error 53?

No. Error 53 means the network path was not found, which often indicates the host is unreachable. Error 67 means the name itself cannot be found — the host may be reachable, but the share name or computer name is wrong or cannot be resolved.

Do I need to enable SMB 1.0 to fix error 67?

Only if you are connecting to an older device that requires it. Most modern devices use SMB 2/3, so enabling SMB 1.0 is unnecessary and a security risk. Try other fixes first.

Why does error 67 appear when mapping a drive but not when using IP?

If the IP address works but the computer name does not, the issue is name resolution. NetBIOS or DNS is not resolving the name. Enable NetBIOS over TCP/IP or add a hosts file entry.

Can a VPN cause error 67?

Yes. If you are connected to a VPN, the network path may be routed through the VPN tunnel, and the target server may not be reachable over that interface. Disconnect the VPN and try again, or check that the VPN allows LAN access.

Will restarting my PC fix error 67?

Sometimes. A reboot clears temporary network state and restarts services. It is worth trying, but if the underlying cause is a wrong path or disabled service, you will need to fix that specifically.

Related

• How to Wipe Your Hard Drive and Reinstall Windows
• Fix System Data Too Large on Mac
• How to Block Unwanted Calls and Texts on iPhone