SMB Login
failure
3x weight
measured
SMB Login. host unreachable (network routing broken)
SMB operation failed: [Errno 113] Host is unreachable
Events
873
Pts per check
4.2
Pts missed
3,637.5
Teams hit
8/13
Authority mappings
Which work roles, knowledge units, and EWU courses this error pattern touches. Hover for context, click to drill in.
DCWF roles:
CE-463 Host Analyst
CS-462 Control Systems Security Specialist
CS-521 Cyber Defense Infrastructure Support Specialist
CS-531 Cyber Defense Incident Responder
IT-411 Technical Support Specialist
IT-451 System Administrator
What the message means
Errno 113 is 'No route to host'. Unlike 'connection refused' (the host is there but nothing is listening), 'unreachable' means the packet can't even reach the host. This is typically **routing or NAT broken**, not a Samba problem.
Why the service is down
- Server VM is powered off.
- Router's NAT rule points to an IP that doesn't exist on your network.
- Switch/bridge problem. VM network interface disconnected.
- IP conflict. another host claimed the Samba server's IP.
Commands in order
-
1. 1. From the router, ping the server
/ping <server-IP> count=3Expect3 repliesInterpret and nextTimeout = server is off, wrong IP, or L2 problem. Investigate the VM next. -
2. 2. From the server, check your own IP
ip addrExpectThe IP you expect matches the IP in the router's NAT ruleInterpret and nextIf server IP differs: either fix the NAT rule, or fix the server's netplan/interfaces. -
3. 3. Any IP conflicts?
arping -c 3 -I <iface> <your-IP> # from a second host in the same L2Expect1 distinct MAC address responds (yours)Interpret and nextMultiple MACs = IP conflict. Either shut down the other host or change your IP + NAT rule. -
4. 4. VM interface up?
ip link showExpect<iface> state UPInterpret and nextDOWN = `ip link set <iface> up`; check netplan.
Decision tree
Answer each question to route to the right fix.
Q: Can router ping the server?
Yes:
Server is reachable. recheck SMB service status (see SMB Errno 111 playbook).
No:
Q: Is the VM powered on?
Yes:
Wrong IP in NAT rule OR L2 broken. Reconcile IPs.
No:
Boot the VM.
External references
Other patterns on this service
- 13,266.7 failure SMB operation failed: [Errno 111] Connection refused
- 829.2 failure SMB connection failed: protocol error
- 183.3 failure Failed to connect to host: IP
- 120.8 failure SMB operation failed: timed out
- 116.7 partial SMB operation failed: Failed to list shares: Unable to locate Server Service RPC endpoint
- 100 failure SMB operation timed out in 5 seconds
- 91.7 partial SMB operation failed: Failed to list shares: Unable to connect to IPC$
- 16.7 partial SMB operation failed: Failed to list shares: Unable to bind to Server Service RPC endpoint
- 8.3 failure SMB operation failed: [Errno 104] Connection reset by peer