Error map
The specified network name is no longer available (64) Networking: Windows error 64: The specified network name is no longer available — SMB session dropped
Networking · layer 2, Network
Centre: this error. First ring: errors it is linked with (7). Outer ring: what those are linked with. Colours show the layer of a request each error belongs to. Click any dot to re-centre the map on it; hover to follow its connections. The centre dot opens the error page.
Directly related (7)
0x80070035: The network path was not found (System error 53)
Windows can’t reach the shared folder — name resolution, SMB settings, firewall or network discovery is preventing it.
Networking: PING: transmit failed. General failure. / ping: sendmsg: Operation not permitted
The operating system could not even send the packet, so the problem is local (adapter, route or firewall), not the remote host.
Networking: kernel: nfs: server nas01 not responding, still trying / nfs: server nas01 OK
An NFS client can't get replies from the server, so processes using the mount hang in uninterruptible sleep.
Networking: IPv4 address 169.254.x.x (Autoconfiguration / APIPA) — the PC couldn't get an address from DHCP
With no DHCP answer, the computer gave itself a link-local 169.254.x.x address, which only works on the local segment.
Networking: Windows: Default gateway is not available / Diagnose Connection Problems: DHCP not enabled
The PC can't reach its router, so it has no path out of the local network.
Networking: SSH/HTTPS connects but hangs on large data — path MTU discovery black hole
Small packets pass but full-size ones vanish, so logins work and then transfers or page loads stall.
Networking: Your Remote Desktop Services session has ended. Possibly the network connection was lost / Remote Desktop disconnected, error code 0x904
An established Remote Desktop session dropped because the network under it stalled or the session was reset.
Two steps away (21)
Error: connect ECONNREFUSED 127.0.0.1:5432
Nothing is listening at that host:port — the target service is down or you’re connecting to the wrong address.
HTTP 407 Proxy Authentication Required
A proxy between you and the server requires credentials before it will forward your request.
HTTP 408 Request Timeout
The server closed the connection because the client took too long to send the complete request.
Docker Desktop: WSL 2 installation is incomplete / WSL update required
Docker Desktop on Windows needs WSL 2 and its Linux kernel; they’re missing, outdated or disabled.
Networking: Network cable unplugged / `ip link` shows NO-CARRIER state DOWN / Ethernet: Network cable unplugged
The network card sees no electrical link, so nothing above it (IP, DNS, browser) can work.
Networking: No Wi-Fi networks found — the Wi-Fi adapter is missing, disabled or its driver failed
The operating system doesn't see a working wireless adapter, so no networks can be listed.
connect: No route to host (EHOSTUNREACH)
The destination host isn’t reachable — it’s down, on another subnet without routing, or a firewall rejects with “host unreachable…
Networking: `arp -n` shows (incomplete) / Destination Host Unreachable — no ARP reply from the next hop
The machine asked "who has this IP?" and nobody on the local network answered.
Networking: netstat -s: segments retransmitted / Wireshark: TCP Retransmission, TCP Dup ACK — packet loss on the path
Packets are being lost, so TCP resends them and throughput collapses.
Networking: Windows has detected an IP address conflict / Duplicate address detected by 00:aa:bb:cc:dd:ee
Two devices on the same network are using the same IP address, so traffic reaches the wrong one or neither.
Networking: Two hosts on one LAN can't talk — subnet mask or network address mismatch
The hosts disagree about which addresses are local, so one tries to route traffic that should go straight across the LAN.
Networking: dhclient: DHCPDISCOVER on eth0 ... No DHCPOFFERS received. No working leases in persistent database - sleeping.
The client broadcast a DHCP request and no server answered.
HTTP 502 Bad Gateway
A proxy or gateway (Nginx, load balancer, CDN) got an invalid response — or no response — from the upstream server behind it.
HTTP 504 Gateway Timeout
A proxy or gateway waited too long for the upstream server to respond and gave up.
Cloudflare-branded 502 Bad Gateway / 504 Gateway Timeout ("cloudflare" footer)
A plain-looking 502/504 page with “cloudflare” at the bottom comes from Cloudflare’s network itself (or an origin response it cou…
Networking: ping: local error: message too long, mtu=1500 / Packet needs to be fragmented but DF set
A packet is larger than the path MTU and is marked "don't fragment", so a router discards it.
Networking: VPN is connected but I can't reach the internal network — missing routes, split tunnel or overlapping subnets
The tunnel is up, but traffic for the office/VPC subnets isn't sent through it or comes back the wrong way.
Networking: %OSPF-5-ADJCHG: Nbr 10.0.0.2 from EXSTART to DOWN — OSPF neighbor stuck in EXSTART/EXCHANGE (MTU mismatch)
Two OSPF routers see each other but never finish exchanging databases, cycling between EXSTART and DOWN.
Networking: Connection works, then fails after being idle — firewall/NAT idle timeout dropped the TCP session (use keepalive)
A connection that sat idle was forgotten by a firewall or NAT device, so the next packet gets reset or vanishes.
Networking: Handshake for peer did not complete after 5 seconds, retrying (try 2) — WireGuard tunnel never establishes
The WireGuard peers can't complete the cryptographic handshake, so no traffic flows.
Networking: IKE: received NO_PROPOSAL_CHOSEN — IPsec peers can't agree on encryption, hash or DH group
The two VPN gateways offered encryption settings that have nothing in common, so the tunnel never comes up.
Map another error
Popular: 500403400ORA-009331064Critical errorFileNotFoundException assemblyTypeError