How to fix ERROR_BAD_NET_NAME (67)
Description
The network name cannot be found. This error occurs during a file transfer when Windows is unable to resolve or reach a UNC network path (e.g. \\server\share\folder). TeraCopy encounters this when the source or destination is a network share that is unreachable, misconfigured, or no longer exists.
Causes
- Invalid or mistyped UNC path — the server name or share name in the path does not exist or has been renamed.
- Network share has been removed — the shared folder on the remote machine is no longer shared or has been deleted.
- Domain controller is unresponsive — if the machine hosting the share is a domain controller with misconfigured network components, it may stop responding, making its shares unreachable.
- Outdated or incompatible network adapter drivers — faulty drivers on the server can prevent it from properly advertising or serving network shares.
- Misconfigured IP Network Address Translator (NAT) — an incorrectly configured NAT driver can interfere with network name resolution and UNC path access.
- Distributed File System (DFS) service not running — if the path routes through DFS, a stopped DFS service will cause the network name to be unresolvable.
Solutions
-
Verify the UNC path — Open File Explorer and try navigating to the path manually to confirm it is accessible.
-
Check that the share exists — on the remote machine, confirm the folder is still shared and that sharing has not been disabled or the folder renamed.
-
Update network adapter drivers — on the machine hosting the share (particularly domain controllers running Windows Server), install the latest network adapter drivers compatible with the operating system.
-
Disable a misconfigured IP NAT driver — if Network Address Translation is installed but not configured correctly, disable it:
- Open Device Manager (right-click My Computer → Properties → Hardware → Device Manager).
- From the View menu, select Show hidden devices.
- Expand Non-Plug and Play Drivers.
- Right-click IP Network Address Translator and select Disable.
- Restart the computer when prompted.
-
Restart the Distributed File System service — if the share is accessed via DFS, restart the service on the domain controller:
- Open Services (
services.msc). - Locate Distributed File System, right-click it, and select Restart.
- Retry the file transfer.
- Open Services (