Learn / Answers

What does "connection refused" look like in a packet capture?

A refused connection is a connection request (SYN) answered immediately by a reset (RST) instead of a SYN/ACK. The network delivered the request and the server's machine answered, so the path works: nothing was listening on that port, or a firewall rejected it on the server's behalf.

What it looks like in the packets

  • The client sends a SYN to the server's port.
  • The reply comes back quickly with the RST and ACK flags set.
  • No SYN/ACK, so no connection ever opens. Apps often retry, so the pattern repeats.

Common causes

  • The service isn't running or crashed.
  • It listens on a different port, or only on localhost (127.0.0.1).
  • A host firewall rejects the port with a reset.
  • A load balancer has no healthy backend.

What to check

  1. Confirm the port number the client used matches the service.
  2. On the server, list listening ports: ss -ltn (Linux) or netstat -an (Windows).
  3. Check the service's logs and status, then any firewall rules on the server.

Wireshark display filters

  • tcp.flags.reset == 1every reset
  • tcp.flags.syn == 1 && tcp.flags.ack == 0every connection request

How Blame Finder flags it

Warning when the same address and port refuse two or more attempts; Low for one. Upload a capture and the finding links straight to the packets behind it, with the most likely culprit at the top.