The specified network name is no longer available (64) Networking Origin: Network OSI layer 5 · Session Last updated 5 Nov 2026

Networking: Windows error 64: The specified network name is no longer available — SMB session dropped

A connection to a Windows file share was cut while in use.

Exact message you may see The specified network name is no longer availableWindows error 64 network nameSystem error 64 has occurred\\server\share The specified network name is no longer available
Explore the map of this error Full error map →
Seen on: Windows Networking

Meaning

The SMB session broke, from a network drop, a server restart, a firewall or antivirus resetting the connection, or an SMB signing/version mismatch. Check connectivity and event logs, update NIC drivers, test with Get-SmbConnection, and make sure SMB ports (445) aren't being interrupted by VPN/MTU settings or security tools.

Common causes

  • Network interruption between client and file server
  • File server restarted or overloaded
  • Firewall/antivirus resetting SMB
  • NIC offload/driver problem
  • SMB version or signing mismatch

⚡ Quick fix

  1. Test: Test-NetConnection server -Port 445
  2. Update NIC drivers; try disabling large send offload
  3. Review the server's SMBServer event log

Detailed fix by platform

Windows

  1. powershell
    Test-NetConnection fileserver -Port 445
Get-SmbConnection
Get-WinEvent -LogName Microsoft-Windows-SMBServer/Operational -MaxEvents 20

How to diagnose

  1. Port 445 — Reachable?
  2. Server — Stable?
  3. Security software — Resetting?

🔧 Still not fixed?

Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:

Where this error sits

Origin: Network. Errors that are often confused with or caused by this one (click to open):

0x80070035 — 0x80070035: The network path was not found (System error 53) (Windows)0x80070035169.254.x.x self-assigned IP (DHCP failed) — Networking: IPv4 address 169.254.x.x (Autoconfiguration / APIPA) — the PC couldn't get an address from DHCP (Networking)169.254.x.x self-assi…Connections hang on large transfers (PMTU black hole) — Networking: SSH/HTTPS connects but hangs on large data — path MTU discovery black hole (Networking)Connections hang on l…nfs: server not responding, still trying — Networking: kernel: nfs: server nas01 not responding, still trying / nfs: server nas01 OK (Networking)nfs: server not respo…PING: transmit failed. General failure. — Networking: PING: transmit failed. General failure. / ping: sendmsg: Operation not permitted (Networking)PING: transmit failed…Windows: Default gateway is not available — Networking: Windows: Default gateway is not available / Diagnose Connection Problems: DHCP not enabled (Networking)Windows: Default gate…Your Remote Desktop Services session has ended (network problem) — Networking: Your Remote Desktop Services session has ended. Possibly the network connection was lost / Remote Desktop disconnected, error code 0x904 (Networking)Your Remote Desktop S…The speci…

Explore the map of this error Full error map →

🧠 Still stuck? Analyze your error

Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.

💬 What worked for others

No tips yet — did something else fix this for you?

Share what worked for you

Tips are checked by an editor before they appear. Links are removed.