SMB Login
failure
3x weight
measured
SMB Login refused (Errno 111). Samba not accepting connections
SMB operation failed: [Errno 111] Connection refused
Events
3,184
Pts per check
4.2
Pts missed
13,266.7
Teams hit
13/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 111 is POSIX for 'Connection refused'. The scoring engine reached port 445 on your server but nothing is listening (or the listener closed the connection immediately). Either **smbd is not running**, or **port 445 isn't forwarded through the MikroTik router**. SMB Login is the **single highest-value service at 3× weight** (4.17 pts/check). Fix this before anything else.
Why the service is down
- `smbd` service stopped or crashed.
- Samba listening only on 127.0.0.1 (smb.conf `bind interfaces only = yes` misconfigured).
- MikroTik router missing dstnat for TCP 445.
- Host firewall dropping inbound 445.
- `smb.conf` has a syntax error and Samba refused to start. check `testparm -s`.
Commands in order
-
1. 1. Is smbd running?
systemctl status smbdExpectactive (running)Interpret and nextIf inactive: `systemctl start smbd`. If it fails: `journalctl -u smbd -n 50`. -
2. 2. Listening on 445?
ss -tlnp | grep :445Expectsmbd on 0.0.0.0:445 or :::445Interpret and nextIf only 127.0.0.1: fix smb.conf `interfaces` and `bind interfaces only`, then restart smbd. -
3. 3. Validate smb.conf
testparm -s 2>&1 | head -30ExpectParses cleanly; `[files]` share present; `security = user`Interpret and nextError lines indicate the bad directive. Diff against backup: `diff /etc/samba/smb.conf /root/smb.conf.backup`. -
4. 4. Verify Samba users exist
pdbedit -LExpectAt least the expected users: keons, henri_cartan, listo, nills, reisdro, lisdnInterpret and nextMissing: `smbpasswd -a <user>` and re-enter password. -
5. 5. Try a local connection as the scoring user
smbclient -L //localhost -U keonsExpectLists shares (incl. `files`) without errorInterpret and nextACCESS DENIED = password wrong. NT_STATUS_CONNECTION_REFUSED = service still down. -
6. 6. Router NAT
/ip firewall nat print where dst-port=445Expectdstnat TCP 445 -> <server-IP>:445Interpret and nextMissing? Add it with `/ip firewall nat add chain=dstnat protocol=tcp dst-port=445 action=dst-nat to-addresses=<ip> to-ports=445` -
7. 7. Nuclear restore
cp /root/competition-backups/smb.conf /etc/samba/smb.conf ; systemctl restart smbdExpectBack to known-good configInterpret and nextUse when the student has edited smb.conf beyond repair.
Decision tree
Answer each question to route to the right fix.
Q: Is smbd active per systemctl?
Yes:
Q: Listening on 445 on 0.0.0.0?
Yes:
Q: smbclient -L //localhost -U keons works?
Yes:
Router NAT is the problem. Add /ip firewall nat for 445.
No:
Samba users missing or wrong password. smbpasswd -a.
No:
Fix interfaces binding in smb.conf.
No:
Start it. Read journalctl if it won't start (usually smb.conf syntax).
External references
- NCAE Cyber Games. official rules and scoring
- Samba 3 HOWTO (Samba project)
- Samba smb.conf(5) man page
-
NCAE Cyber Games. official tutorials channel
44 tutorials. Numbers 23–32 are the Defense Checklist.
Other patterns on this service
- 3,637.5 failure SMB operation failed: [Errno 113] Host is unreachable
- 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